Collaboration space to discuss and document re-architecture of the project website.
Goals
- Currently, any change to the website requires a commit to the project source code repository and a series of manual steps to get the change published.
- It would be preferable if small content changes did not require a commit to project source code and could be reflected immediately.
- Currently, the entirety of site content is served out of release and snapshot sub-folders such as /site/0.5-incubating with a manually manipulated /site/latest redirect
- Really only a subset of artifacts need to be maintained for earlier versions - much of the content could be hosted directly from streams.incubator.apache.org not in a subfolder
- Currently, the site is 100% built by maven site plugin. This does an ok job at producing a navigable integrated hierarchical experience, but the actual HTML, CSS, JS produced is flawed and only so flexible.
- Really only the site report artifacts (javadocs, checkstyle reports, etc...) need to be product by maven site.
- It would be nice if the site scaffold (headers, menus), hierarchy, and content (example code, prose, diagrams, etc...) were
- decoupled from the project source code
- able to be customized fully (at least more) to use arbitrary HTML, CSS, and JS libraries