Hi Eugen,

Thank you very much for all your efforts. The community is fortunate that you 
are able to dedicate so much concentrated effort.

> I've given up on building the old site since I failed several times.

I think that’s ok, though. Honestly, I don’t see a viable path forward in terms 
of “migrating” the old docs. Yes, there is some good information still in those 
docs, and some good stuff that could inspire the new docs, however, I think the 
only practical way forward is to start over, from a top-down perspective. IMO, 
we need to make a clean break, and at the same time re-evaluate the James 
mission. (But that’s just my opinion and I’m just a newbie so my voice doesn’t 
hold as much weight.)

I like the inventory. I can use that as a checklist to make sure the new docs 
aren’t leaving anything out. Or maybe the old docs could be assembled for the 
“developer” part of the site, aimed at experienced James developers who already 
know their way around and just need a reference. But I don’t see how the 
current docs could be useful for Operators or Integrators who don’t have 
experience with James.

So with that in mind...

> I've create two issues to track the progress of migrating the old site
> to Antora.
> 
> * Make an inventory of old site
> https://issues.apache.org/jira/browse/JAMES-3301

Cool, thanks! I think this can be useful.

> * Migrate the content https://issues.apache.org/jira/browse/JAMES-3302
> 
> Please help out with the inventory and if you have ideas with the content.
> 
> I'll migrate what I can, we can sort them after.

I don’t think that’s necessary, but if it’s already done, then great.


Thanks again!
=David


Attachment: signature.asc
Description: Message signed with OpenPGP

Reply via email to