Re: Tutorials Review: Carousels (and minor Images)

Hi all,

addendum to the email below:

I wanted to incorporate some changes from Shadi (to continue work on them) into  pull request [PR 317], but made an error that made it hard to review. I was able to restore the content of PR 317 (thanks to versioning!), but it now has another Pull Request number: [PR 365]. I added pointers to the new PR number in 317 and closed it.

I am sorry for the inconvenience and confusion this might have created. I am looking forward to your reviews.

— Eric




On 25 Oct 2016, at 15:10, Eric Eggert wrote:

> Hi Adina, Denis, Howard, Shadi, Susan, and anyone else who wants to help!
>
> Thanks for coming forward to help with the Tutorials. I need your input to the following issues __by next Tuesday (November 1, 2016)__, so we can progress with publishing out-of-draft versions of the tutorials as soon as possible.
>
> Please indicate to me if you are able to do so.
>
> ## The issues:
>
> * Carousels – [#317 Simplify carousel tutorial, mostly structure page][PR317]
>
>   The carousels structure page has gotten an overhaul, you can find rendered versions the current and the suggested version linked from [a comment in the pull request][PR317c].
>
> * Carousels – [#318 Restructuring/Slimming down carousel functionality page][PR318]
>
>   The carousels functionality page has gotten a similar overhaul, you can find rendered versions the current and the suggested version linked from [a comment in the pull request][PR318c].
>
> * Images – [#359 Add “(redundant)” to misleading functional image link][PR359]
>
>   A minor change to the “Alt Decision Tree” that clarifies a link.
>
> ## How to help:
>
> * Read through the changed pages as they are linked from the pull requests above.
>
> * Use the [GitHub Pull Request Reviews][PRReviews] to comment, request changes or approve the changes.
>
>   * **How does that work?** When you hover or tab trough individual lines on the Files tab of the pull requests, there is a blue [+] button that appears for every line. That way you can comment on lines individually and be very specific.
>
>   * Mark clearly which comments are for Editor’s discretion.
>
>   * When adding the first comment select the (green) „Start a review“ button. Your comments are then collected into one review.
>
>   * Once you have put in all the feedback, select the (green) „Review changes” button and select if you have only submitted comments (for Editor’s discretion), request changes or approve the changes.
>
>   * See [GitHub Help Pages][PRReviews] for further information and step-by-step
>
> * Of course you can also just comment on the GitHub Pull Request or send emails to the (publicly archived) w3c-wai-eo@w3.org list if you find the process above overwhelming.
>
> * (Yes, you’re the guinea pigs for this workflow. Sorry. 😀 Report what works for you and what does not, please!)
>
> * If you have any questions, [drop me an email][ERIC]. If you want me to give you a brief run-down of the commenting process, I might be able to do so at the end/after our weekly meeting on Friday (October 28, 2016).
>
> Best,
> — Eric
>
> [PR317]: https://github.com/w3c/wai-tutorials/pull/317
> [PR317c]: https://github.com/w3c/wai-tutorials/pull/317#issuecomment-254837052
> [PR318]: https://github.com/w3c/wai-tutorials/pull/318
> [PR318c]: https://github.com/w3c/wai-tutorials/pull/318#issuecomment-254837479
> [PR359]: https://github.com/w3c/wai-tutorials/pull/359
> [PRReviews]: https://help.github.com/articles/reviewing-proposed-changes-in-a-pull-request/
> [ERIC]:mailto:ee@w3.org
>
> -- 
> Eric Eggert
> Web Accessibility Specialist
> Web Accessibility Initiative (WAI) at World Wide Web Consortium (W3C)
>


[PR 317]: https://github.com/w3c/wai-tutorials/pull/317
[PR 365]: https://github.com/w3c/wai-tutorials/pull/365

--

Eric Eggert
Web Accessibility Specialist
Web Accessibility Initiative (WAI) at World Wide Web Consortium (W3C)