At least we probably want the "203" string to be a Django Setting somewhere.
Do we want to try and have the version as a field on the page somewhere so we aren't parsing URLs? (Not that the URL's are likely to change.) Should we try and make guidance dev docs a different model?
Or is not indexing a bad idea in all, what if people want to find old versions? Then I think our only option is to make a giant big banner on the top of old versions saying "Go here for latest version!" (Maybe we should do that anyway?)
https://developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap says
Google ignores <priority> and <changefreq> values.
So don't index old ones?
Let's discuss how further to go here.
At least we probably want the "203" string to be a Django Setting somewhere.
Do we want to try and have the version as a field on the page somewhere so we aren't parsing URLs? (Not that the URL's are likely to change.) Should we try and make guidance dev docs a different model?
Or is not indexing a bad idea in all, what if people want to find old versions? Then I think our only option is to make a giant big banner on the top of old versions saying "Go here for latest version!" (Maybe we should do that anyway?)