Yes I’d also like to participate in this Sent from my iPhone
> On Jan 31, 2023, at 02:37, Meta Cyrus <[email protected]> wrote: > > > Hi James, > I am a good UI/UX and web developer who can Design and develop a good user > reliable website. > Where I can start?? > Regards, > Inzemamul Haq > >> On Tue, 31 Jan, 2023, 7:23 am James Dailey, <[email protected]> wrote: >> All - >> >> We have a lot of good content on the wiki but it's been 3+ years since we >> did a clean sweep of it. We also have a front landing page at >> https://fineract.apache.org that could be better at communicating the >> project and community. Who wants to work on this with me? >> >> PROPOSED CHANGES >> --- >> On the front "Landing" page: >> Add blog feed >> Add feed to dev list >> Include FAQ >> Split FineractCN and Fineract >> As we hope to see a FineractCN release soon, I think we should have a top >> level split on the main page as well, or perhaps a separate landing page for >> FineractCN. >> >> --- >> On the wiki - new suggested structure (figure out how to show two levels): >> FAQ >> About Fineract >> New top level functional descriptions >> About FineractCN >> TBD >> Project Management >> Quarterly reports to the Apache Board (this needs to be more prominent) >> Community meetings organized by date (most recent at top) >> Surveys >> Release processes >> How do I get involved? >> Committer guides >> Links to JIRA and GitHUB >> Standards >> Documentation >> Replace with links to the new dynamically generated documentation. >> Move Comms related stuff (talks, opinion pieces, etc) ... all go to blog >> >> >> Are there things we should keep or not keep? >> >> >> >> The current high level structure: >> FAQ (frequently asked questions) >> GETTING INVOLVED (commit, contribute) >> FINERACT >> FINERACT CN >> Fineract Data, Credit Scoring, AI >> Fineract Project Security Report >> COMMS: Blogs, Talks, and Links >> ApacheCon EU 2016 Fineract Speaker's Notes >> How-to articles >> ApacheCON Fineract Track >> Meeting notes >> >> >> >>
