View Source

Date

2023-05-11

On Zoom. Send email to dev list, responding to the thread "Website and Wiki for Fineract Updates" if you wish to attend.

- Unknown User (jdailey), PMC
- @abhinav Sinha , new to Fineract, GSOC 2023
- @John Gathogo , at Fiter , implementing system
  @Juste Comore , new to Fineract
- @Inzemam Ul Haq, pursing a Tech CS degree

Establish the plan for improving the front end of Fineract landing page and the wiki structure ,
Communication concepts and branding
Review designs by a contributor

Time	Item	Who	Notes
10 min	Introductions	James	John - interested in documentation
10 min	Communication - why are we here?	Inzemam	How does the world perceive us? Landing page redesign Wiki
	Details on Documentations	John G	made some recommendations on documentation analysis of what is there
40 min	Discussion		see below

The landing page is for the outside audiences
Wiki pages is how the org stays organized, public but almost an "internal to the project"
The Technical documentation - Post dev, what is the platform as it exists today (including tech documentation)
What is our initial focus? Let's work on the Landing page and key messages
- See https://spark.apache.org/. No mention of open source, aimed at technical people , one of the best projects
- See https://hadoop.apache.org/. Mention of open source up front, simple landing page
- See https://cwiki.apache.org/confluence/display/HIVE. for example of a much simpler wiki structure
Inzemam:
- Landing page should have some graphical information / communication to the audience
- News section / blog
messages feedback / imagery
- John - key messages , core banking , simple iconography
- Juste - make it simple to understand. Core banking, simplicity, when people see it, we want them to understand it.
- Abhinav - anything related to finance: secure (number one thing)
- James - look at Hadoop, nothing graphically intense, can be very simple, just a landing page for people following links from other providers

(as of May 15, 2026, all are stale and manually closed to clean up the aggregated TODO list on Meeting notes)

Inzemam to share new landing page and then to fork the current GitHub repo and propose a PR
due date is June 15th for launch of new landing page
John to work on the alignment of Technical Platform documentation vs Wiki pages
James to update listserv with these notes.