Sorry, I was a bit too hasty in sending that. I'd like to add: re: potentially blocking issues -- Honestly, I don't know. It may be dependency conflicts on our end, and/or those issues I linked to might be involved. Those were just breadcrumbs that may help us when we decide to devote the time to upgrading our deps for building our official docs. If someone with intimate knowledge of Gradle (or even one of their devs) can help us that would be great, but we surely have the expertise on this list as well. I know I could do it, I'll just be slow at it until I'm able to refresh my Java dep mgmt tooling and skills. Pairing would help.
re: nice to have -- no, I'd say it's much more severe than that, but not necessarily urgent (until it is -- e.g. our docs break or we want a new asciidoctor feature). Dependencies must be kept up to date. Out of date deps are a code smell / tech debt and they creep up on us when we're lazy or just haven't properly planned / allocated resources. They waste everyone's time and turn away new contributors. re: step 14 -- good call, yes, it should be added there. Patches welcome, or I'll get to it eventually, or just wait a bit: Aru Sharma is working on automating deployment of generated versioned asciidoc (official docs) <https://mifos.slack.com/archives/C028634A61L/p1756085259295949?thread_ts=1755877617.970599&cid=C028634A61L> .
