feature/website support for /latest/ and /absolute-latest/ redirection #965
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary of the changes (Less than 80 chars)
Website /latest/ using .htaccess rewrite rules
Description
I don't think there is an issue for this one but it's a feature we have been wanting for a while.
This pull request introduces a new URL redirection feature for the Lucene.NET website. It sets up two redirects into the API documentation using .htaccess rewrite rules. The implementation adds two useful URL paths:
• /doc/latest/: Redirects users to the API documentation for the most recent officially released version of Lucene.NET.
• /doc/absolute-latest/: Directs users to the absolute latest version of the API documentation, which may include pre-release versions.
These redirects allow the main website to link to the API documentation dynamically, without hardcoding the version number in the URLs, ensuring that users are always directed to the correct version of the documentation even as we provide new version of Lucene.NET and its accompanying API documentation.