Sections, Navigation

[shawna-slh]

Background is in other issues.

Ideas:

1. All (h1:All ARIA Authoring Guidance) [see https://github.com/Differences in APG navigation and information architecture when compared to WAI minimal template #34]
2. Patterns and Widgets (h1: Design Patterns and Widgets)
3. Examples Index [it is lists of Examples. include “Index” for those familiar with previous /TR/ doc]
4. General [or something other than fundamentals]
5. Current Work [or maybe “Updates and Contributing” or “Get Involved” ?]

Question: Is everything users might want from the /TR/ doc included in this redesign? What about 10. Roles That Automatically Hide Semantics by Making Their Descendants Presentational and 11. Structural Roles ?

[shawna-slh]

I am missing the rationale for calling the lists of examples "Index"?

The word "Index" is used for a list of everything. This is not a list of everything.

If a developer is looking for examples, seems they would look for "Examples" and not "Index".

[mcking65]

@shawna-slh asks:

I am missing the rationale for calling the lists of examples "Index"?

The word "Index" is used for a list of everything. This is not a list of everything.

If a developer is looking for examples, seems they would look for "Examples" and not "Index".

It will be a list of everything. It just is not that yet. We have a lot of work to do on the index page. It didn't make sense to do it in the TR doc because of the complications of linking and maintenance.