Duplicate Chapter about narrows HOT 8 CLOSED

On Jul 22, 2017 10:46 AM, "Esteban Manchado Velázquez" < ***@***.***> wrote: Saving a chapter (to fix typos) shouldn't change the publishing date, so that shouldn't become a problem. Unless you press "Publish" instead of "Save" (and thanks to this conversation I realise that having a "Publish" button when it's already published is probably stupid/confusing). Chapter numbers are probably going to be very tricky, at least if we show them to the players (because not all characters participant in all chapters). But we can talk about it via e-mail or whatever. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#5 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGLNG8AwgAWaBlTvBAc83U3LG5174vP2ks5sQjVpgaJpZM4OZejU> .

On Sat, Jul 22, 2017 at 1:29 PM, Esteban Manchado Velázquez < ***@***.***> wrote: The main issue (duplicate chapters) should be fixed now. Let's talk about the ordering issue separately. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#5 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGLNGwdEOnoyCi_bbksPw3GG_WP8cz3Tks5sQlvCgaJpZM4OZejU> .

On Jul 22, 2017 1:40 PM, "Tess Gadwa" ***@***.***> wrote: Good plan. I wanted to run something by you that is simply a matter of process, and see what you thought about it. In the past, it has been difficult to submit UX input to open source projects because Github does not have a good process to incorporate usability and design feedback such as wireframes, mockups, usability testing, motion captures, and of course issues and suggestions for existing functionality. The problem is that UX input typically is not a spec and is not a bug report, but can be either -- it also relies heavily on visuals as well as plain text. Also, ideally it is part of the overall collaborative conversation and not just "for eyes only" of one participant. Anyway, I've experiment with a good format to include this type of a project in the discussion -- slide deck, issue list in Github, Gist -- and I think I have an idea for something that might work a little better for ongoing usability contributions to open source projects. May I share it with you? Best, Tess On Sat, Jul 22, 2017 at 1:29 PM, Esteban Manchado Velázquez < ***@***.***> wrote: > The main issue (duplicate chapters) should be fixed now. Let's talk about > the ordering issue separately. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#5 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AGLNGwdEOnoyCi_bbksPw3GG_WP8cz3Tks5sQlvCgaJpZM4OZejU> > . > -- Tess Gadwa Chief Executive Officer _______________________________ Yes Exactly, Inc. | yesexactly.com | 413.325.8251 <(413)%20325-8251>