Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
Right now, the https://jackrabbit.apache.org website automatically redirects to https://jackrabbit.apache.org/jcr/index.html and this is placed front and centre as the most recent version of jackrabbit.
This page contains a "documentation" subheading, which in turn shows how to get started with what turns out to be legacy version of jackrabbit 2.
Oak is the most recent version of jackrabbit, however links to oak appear nowhere in any of the main site's navigation, neither the top nav, nor the left side nav. A throwaway mention is made of oak in "Welcome to Apache Jackrabbit" and the download page, but the end user is none the wiser as to the significance.
To fix this (please correct if wrong).
- Create a stripped down maven site to be published at https://jackrabbit.apache.org. Apart from the Apache boilerplate, the site needs to link to Jackrabbit Legacy, and Jackrabbit Oak, clearly indicating that Legacy is an older iteration of Oak.
Include some history of the difference between legacy and oak, so that the end user isn't sent down a long rabbithole implementing legacy when it is oak they should have been using all along.
- Rename the https://jackrabbit.apache.org/jcr/ site to https://jackrabbit.apache.org/jr2/.
JCR has a specific meaning, hosting the docs for jr2 under the url jcr is super confusing for end users.
- Link https://jackrabbit.apache.org/oak/ into the https://jackrabbit.apache.org/ site at the same level as https://jackrabbit.apache.org/jc2/
Highlight that oak is the system that should be used, while noting where it is still necessary to use jr2 components.