[ ] Complete a bit file:///home/hp/Documents/james-site-asf/doc-sites/build/site/james-project/3.8.2/servers/basic/index.html assuming james-server-jpa
[x] Migrate file:///home/hp/Documents/james-site-asf/doc-sites/build/site/james-project/3.9.0/servers/distributed/extending/index.html into file:///home/hp/Documents/james-site-asf/doc-sites/build/site/james-project/3.8.2/development/index.html
[x] Simple placeholder within file:///home/hp/Documents/james-site-asf/doc-sites/build/site/james-project/3.9.0/development/index.html
[ ] Link legacy doc! And mention legacy spring app.
[ ] Review and polish file:///home/hp/Documents/james-site-asf/doc-sites/build/site/james-project/3.9.0/concepts/index.html
Why?
Being in a state we can publish with minimal efforts.
We would replace the legacy documentation.... (move it into /legacy path into james.apache.org). Needs a vote?
And we would drop the distributed doc as a replacement.
How?
Documentation materials needs to be adapted for this move to be doable.
We would need to also polish the current site like ...