potiuk commented on PR #761: URL: https://github.com/apache/airflow-site/pull/761#issuecomment-1496593374
That's an interesting idea @mik-laj :) . It's not exactly why canonical was created for, but it might do it in our case. However this is significantly more complex to implement because not only we would have to post-process historical pages and add "canonical" link, but we would have to continuously update old pages as they get older - note that "stable" is a symbolic link to the last version, so in effect the stable links would refer to themselves, This on it's own is not a bad practice - it seems to be even recommended https://www.searchenginejournal.com/google-self-referencing-canonicals-are-not-critical/312619/ but then we either post-process the docs when some new version is released or we are limiting ourselves strictly to only indexing the very last patchleve version for airflow or providers. IMHO - If we choose to only index the last patchlevel - then using canonical makes sense. If we choose another scheme, this is a lot of hassle. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
