Thank you to Vivek W (github @AryanVBW) for making some changes possible on the landing page ==> https://fineract.apache.org.
I pushed those live yesterday and then made some editorial changes, to better reflect what is in the project. I highlight a few here so it is transparent and to be on the same page as to what is in the Project boundary. Instead of "Comprehensive customer verification system", I write "Flexible customer system of record". The difference is that we do NOT have any processes that can query outside IDentity systems, address verification systems, or other third party systems. That is the job of a system integrator or vendor that takes the project and productizes it. On the other hand, we can consume a lot of different data about a Customer, so that's a valid feature set. Instead of "Secure and efficient payment processing", I write "System of record for repayments". To be clear, the fineract system does not enable payment processing. Payment processing treats fineract as a System of Record (SOR) or Account-Management-System (AMS). Again, more of a deployment concept and definitely not in our code at Fineract. Instead of "Support for both online and offline mobile interfaces", I write "Headless designs allow for third party mobile solutions", as Fineract does not have online and offline mobile interfaces. Indeed we have some active improvements needed in this area in particular to secure such external end-user connections. (see threads on FSIP for removing Self Service APIs). I also added a link to https://fineract.apache.org/docs/current/, because this is where the Platform or System documentation should now live as discussed previously. There may be some additional documentation that hasn't fully come over from the wiki, but primarily the Wiki is for Development processes and Project Management. I'm going to look at the other links as I think some of them are dead or lead to inaccurate information about the project. Anyone willing to help out, give me a shout here. Thanks, If you happened to be looking at the page yesterday, you may have noticed a graphical mess. Thank you to @Adam Monsen for fixing this. On Jan 25th, the ASF started to restrict some cross-site scripting, so all of the Google material assets such as icons had to be brought into our CSS and so that broke the site. James