Misc navigation updates

[tamsinewing555]

No description provided.

[remibetin]

@tamsinewing555 This PR includes a lot of URL changes.

We should avoid changing URLs frequently and only do so if we expect the new ones to stay for long. See Tim Berners Lee's Cool URIs don't change, and Studio24 notes on URL strategy for the W3C website.

If we want to do some changes, I would recommend following the following principles in consistency with the W3C website:

• Prefer shallow URLs. For example, let's use w3.org/WAI/contact/ instead of w3.org/WAI/about/contact/
• Prefer short URLs. In WAI's context, I would recommend not using wai in the URLs when not needed. For example, let's use w3.org/WAI/contact/ instead of w3.org/WAI/contact-wai/
• Use patterns and keywords already used on the W3C website.

[remibetin]

@tamsinewing555 I have merged some changes via #208 (and two subsequent commits to fix a bad search and replace)

[shawna-slh]

open: capitalization of resource titles

[tamsinewing555]

@remibetin - Happy for you to make the changes you suggested and use shallow, short URLs.
Is there anything else this is waiting on?

[remibetin]

@tamsinewing555

Is there anything else this is waiting on?

It seems that one comment from Shawn about capitalization still needs resolution?

use shallow, short URLs

I propose to revert the URL changes. During a recent meeting, we concluded it was best to do this wholesale later rather than gradually.

[tamsinewing555]

@remibetin

It seems that one comment from Shawn about capitalization still needs resolution?

use shallow, short URLs

I propose to revert the URL changes. During a recent meeting, we concluded it was best to do this wholesale later rather than gradually.

Sorry, I don't understand what these URL reversions are exactly?
For example, 'previous' needs to be 'past'.

[remibetin]

I don't understand what these URL reversions are exactly?

By "reverting URL changes", I meant not changing the URLs for now (sorry for the Git terminology). Would it be ok with you if we only change /about/groups/previous-groups/ to /about/groups/past-groups/ in this PR, and postpone the other URL changes?

[tamsinewing555]

Would it be ok with you if we only change /about/groups/previous-groups/ to /about/groups/past-groups/ in this PR, and postpone the other URL changes?

Yes, no problem. That's the important one.

[remibetin]

Yes, no problem. That's the important one.

@tamsinewing555 Thanks, I've updated the PR.

Please let me know when the capitalization issue is addressed.

[tamsinewing555]

Please let me know when the capitalization issue is addressed.

I'm unclear what the issue is. @shawna-slh will need to clarify.

[shawna-slh]

Titles of pages remain title style capitalization for now.

[shawna-slh]

related: Closed groups should be listed in https://www.w3.org/WAI/about/groups/ , not a separate page, per @iadawn and me. Also "Closed" is W3C terminology so seems best to use that instead of "Past".

[tamsinewing555]

@shawna-slh - if we keep the past groups in a separate page, the current page will need to be redesigned.

@iadawn took a look at the issue with the design a couple of months ago and after discussion agreed it should remain as a separate page.
Happy to look at redesigning if you think this is a priority?

[shawna-slh]

Closed groups should be listed in https://www.w3.org/WAI/about/groups/ , not a separate page, per @iadawn and me. Also "Closed" is W3C terminology so seems best to use that instead of "Past".

This meets user needs.

Happy to look at redesigning if you think this is a priority?

I don't see that it needs major redesign work. Simply put the list of closed groups in the Groups page and:

• Change the heading "Past groups" to "Closed groups" or "Closed working groups and task forces" — I don't care which.
• Put the closed WGs and TFs under that one heading. I do not think there should be separate sub-headings for WGs and TFs — that is unnecessary structure. Though I won't object if others feel strongly.
  I'm fine with either option:
  • The WGs and TFs are together in one list. They are all alphabetical, or the WGs are first then TFs.
  • There are two lists with <p> lead-in "Closed working groups:" and "Closed task forces:"

I'm pretty sure that Kevin does not feel strongly about those listing options either.

Not high priority. Though with our re-starting work on ATAG, people will likely be looking for previous ATAG Working Group info and I'd like it to be easy to find.

[remibetin]

@tamsinewing555 @shawna-slh @iadawn I'll archive this repository, since we are not using it anymore.

Here is what I've done:

• I've re-created and merged a PR RE removing the gerund form
• I've not kept the changes hiding the project pages, since this is now redundant with hide individual project pages — Update navigation.yml  wai-website-theme#179
• I've not kept the URL change for ‘Past groups’, since this is still being discussed.

For future changes to the navigation, feel free to open a PR in the wai-website-theme repository (navigation.yml file).

Thanks all!