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!):
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!):
0(example:AEP-0164), should probably have any leading zero(s) stripped.