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

Move to a single, canonical URL pattern for AEPs #35

Open
3 of 6 tasks
earth2marsh opened this issue Oct 10, 2024 · 0 comments
Open
3 of 6 tasks

Move to a single, canonical URL pattern for AEPs #35

earth2marsh opened this issue Oct 10, 2024 · 0 comments

Comments

@earth2marsh
Copy link
Contributor

earth2marsh commented Oct 10, 2024

Today the site generator supports both the numbered resource (example: https://aep.dev/135 ) and the slug resource (example: https://aep.dev/delete/ ).

As discussed in last week's call, continuing down this path this will split traffic and complicate both search results and web metrics. Going forward, each AEP should have one canonical URL based on the (immutable) AEP number.

This has a few implications (happy to split out as sub-tasks if necessary!):

  • Every AEP page should have only one canonical URL
  • Links in AEP document content should prefer the numbered pattern
  • An AEP may be aliased to one (or possibly more) slugs, which will each re-direct to the canonical numbered URL pattern
  • The rule numbers should be included in the sidenav list of AEPs
  • Consider whether slugs should appear in the keywords meta field (not sure how useful those are any more)
  • Any AEP number reference that begins with 0 (example: AEP-0164), should probably have any leading zero(s) stripped.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant