John Thank you for your contributions in the proposed PRs. I have not pushed them yet as I think we have two issues to resolve.
1) How do we push changes to the site. 2) Which site should it push to? Can you please respond? on #1. If we look at the Antora project, we see that we need to issue this command on our Apache Infra. $ antora antora-playbook.yml And that implies that Antora is deployed there. I don't see that on the list of support deployment mechanisms. https://infra.apache.org/project-site.html. Can you review that and let me know how this will work in our regular workflow of create content and push content? Currently when we push changes to our git for the site, the changes go live - that is the deployment mechanism. I am unclear what is possible and if you've looked at the actual infra. How is Antora supported? Can you write a specific set of steps? on #2, I believe you have some new thinking about managing documentation on the fineract-site, rather than the Fineract code repo. While I appreciate this sentiment, the code needs to be documented and keeping the code and the documentation together helps enforce the idea that if you update the code and do a release, then the documentation is there, as as snapshot of the documentation at that time. That is Release 1.9.0 has Release_Documentation 1.9.0 even if that is incomplete it gives an accurate version of what things are there at that time. Others may disagree but I think the movement should be toward more "self documenting" code and strongly linked to the current release tag or proper branch. Thanks, James
