Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: port accessibility app from stackblitz to aio #32377

Closed

Conversation

kapunahelewong
Copy link
Contributor

@kapunahelewong kapunahelewong commented Aug 28, 2019

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • angular.io application / infrastructure changes
  • Other... Please describe:

What is the current behavior?

Currently, the example is solely on stackblitz and is not in aio, so the example code is inline rather than from a compiled app.

Issue Number: Fixes #32320

Inspired by PR #32261 in which a discrepancy between the code in the actual app and the inline code snippets was fixed.

What is the new behavior?

Now there's an aio example app for the accessibility guide. This way it can be maintained along with the other aio examples and we can use live code snippets in the doc.

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

Adds:

  1. docregions
  2. the same example as is in current use, except in aio in aio/content/examples/accessibility
  3. e2e tests

@mary-poppins
Copy link

@mary-poppins mary-poppins commented Aug 28, 2019

@mary-poppins
Copy link

@mary-poppins mary-poppins commented Aug 28, 2019

@mary-poppins
Copy link

@mary-poppins mary-poppins commented Aug 28, 2019

@mary-poppins
Copy link

@mary-poppins mary-poppins commented Aug 28, 2019

@mary-poppins
Copy link

@mary-poppins mary-poppins commented Aug 28, 2019

Copy link
Member

@jelbourn jelbourn left a comment

LGTM

@kapunahelewong
Copy link
Contributor Author

@kapunahelewong kapunahelewong commented Aug 29, 2019

FYI, here's the preview: https://pr32377-5b560ce.ngbuilds.io/guide/accessibility#case-study-building-a-custom-progress-bar (see the two code examples in that section)

Copy link
Member

@gkalpak gkalpak left a comment

I left a couple of minor comments, but otherwise LGTM 💯
Also, not directly related to this PR, but it would be nice to have a code-woner for the accessibility docs.

@kapunahelewong kapunahelewong force-pushed the accessibility-example branch 2 times, most recently from 401bd4d to 6c22727 Compare Sep 3, 2019
@mary-poppins
Copy link

@mary-poppins mary-poppins commented Sep 3, 2019

@mary-poppins
Copy link

@mary-poppins mary-poppins commented Sep 6, 2019

@kapunahelewong
Copy link
Contributor Author

@kapunahelewong kapunahelewong commented Sep 6, 2019

Caretaker, this is a docs only change. Thank you!

@angular-automatic-lock-bot
Copy link

@angular-automatic-lock-bot angular-automatic-lock-bot bot commented Oct 11, 2019

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Oct 11, 2019
@kapunahelewong kapunahelewong deleted the accessibility-example branch Jun 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
docs
Done
Linked issues

Successfully merging this pull request may close these issues.

6 participants