Select redirect / route component Go capabilities
This issue is required in order to create the architecture issue for the redirect / router component.
The potential scope and features of the redirect / route component has been through several expansion and contraction cycles as we've gotten our hands on some real, complex and legacy docs systems. Now we need to evaluate what we've learned and select the capabilities we'll implement for v1.0 of Antora.
Below are two summaries (each in there own comment) of previous iterations. The first iteration was heavily focused on tracking and mapping. The second iteration was focused on automatically delivering rules to nginx.
Goals for this issue:
- Identify the proposed capabilities and requirements, from either previous iteration, that are a Go for Antora (though not necessarily for v1.0).
- Sort through the Go capabilities / requirements and select which ones we'll implement for v1.0 of the redirect / route component.
- Those v1.0 Go capabilities / requirements will then become the focus of the redirect / route component architecture and implementation issues.
- Create an architecture issue and an implementation with the v1.0 Go capabilities / requirements
- Capabilities / requirements marked as a Go, but not selected for v1.0, should be logged in the roadmap for future versions.