Open ailsaleen opened 3 years ago
fyi @annhelen and @UsmanAfzal made a new ticket here for Sprint 6 for URLs
Here's the table for URLs which I've shared with @yemijaiyeola and @kingdomlevel URLs table
Hi Yemi and Niall - please note I've updated 'documentation-and-tools' to 'documentation-tools' after feedback from Usman. Many thanks
Also 'contact-us' to 'contact'
Thanks
Hi Usman - (left you a note on slack) after double checking, 'contact-us' is fine and widely used on GOV.UK.
I also think it would be preferable to use 'documentation-and-tools', as not having the 'and' slightly changes the meaning. GDS says to avoid articles (a, an, etc) but 'and' is not an article and I've seen it used. I'm not overly attached to this though.
Many examples of 'and' removed in the primary navigation of the website, let's keep this one out.
In response to tree testing results we've decided to amend 'documentation-and-tools' to 'developers' (so the top menu heading will be 'For developers'). So that resolves the debate anyway :-) I've updated the url table @yemijaiyeola @kingdomlevel
Updated spreadsheet for URLS
Thanks for updating those URLs so quickly @kingdomlevel! Much appreciated. A couple of other changes (if you could take a look when you have the opportunity):
Open Referral URLs are designed to be naturally user (and SEO) friendly, and to follow a consistent, predictable, format. These guidelines set out how URLs should be constructed, and our approach to setting up additional URLs for marketing purposes.
These standards apply to openreferraluk.org and its sub-domains.
openreferraluk.org URL style
The style for openreferraluk.org URLs is that: a) URLs always need to be clear, unambiguous, easy to read, easy to type and easy to share
b) all URLs must be in lower case
c) URLs must use words and should not contain acronyms, wherever possible
d) dashes should be used to separate words within URLs so they are easy to read - for example, https://openreferraluk.org/about-open-referral
e) articles (a, an, the) and other superfluous words should not be used. For example, use /documentation-tools rather than /docs-and-guides
f) URLs should use the verb stem, where possible. For example, /register instead of /registering
g) each page must have a URL which is as short, memorable and unambiguous as possible, especially if a URL is going to be referred to offline
h) URLs should be based on user need rather than the (current) name of a policy, scheme or service, which might change.