Hello James, I'd like to volunteer to take ownership of this initiative and help build a sustainable blogging and content-sharing process for the Fineract community. On the platform side, I've looked through the Fineract website, which is now Hugo-based, and explored how other Apache projects manage their websites and blogs. I see two possible approaches. We could continue with Hugo and integrate a blog section into the existing website. This would be the simplest option to start with, as it keeps the stack consistent and relatively easy to maintain. Several Apache projects use similar static-site approaches.
Alternatively, if we're thinking about building a more structured, long-term content platform, we could consider Docusaurus. I've seen Sujan's, Aira's, and Edward's GSoC project documentation using Docusaurus, and I think we could take inspiration from their work. It offers a good foundation for organizing technical content, with features such as author profiles, tags, categories, and a clear navigation structure. It would also give us a straightforward contribution workflow: contributors could write posts in Markdown, submit pull requests, and receive inline feedback and reviews before publication. Once approved and merged, the posts could be published through an automated build and deployment pipeline. We wouldn't need a separate CMS or database for this. However, we'd need to evaluate the migration effort and ongoing maintenance costs before deciding whether the additional capabilities justify introducing a new stack. Regarding content and long-term maintenance, my initial thought is to gradually bring relevant documentation and articles from the wiki into a more structured, discoverable section of the website. The goal would be to make it easier for users and contributors to find information through a consistent UI/UX, while preserving the wiki where it still serves a purpose. We'd also need to ensure that existing links, ownership, and the source of truth remain clear during any migration. For new content, we could start with one post per month, as suggested, and gradually expand based on community participation. Some potential topics include: * GSoC experiences, project summaries, and lessons learned. * Release announcements and important project updates. * Technical deep dives, tutorials, and contributor guides. * Talks, session summaries, and highlights from events such as Community Over Code. * Community members sharing their experiences, use cases, and contributions. I'd also be happy to help contributors turn their technical work and experiences into publishable articles, so that content generation doesn't depend on a single person. On the maintenance side, I can take responsibility for coordinating the editorial process, maintaining consistent style and quality, checking technical accuracy and links, and ensuring that content follows applicable ASF policies and licensing requirements. I'd also help establish a lightweight review and publishing checklist, coordinate reviews with the relevant maintainers, and encourage community members to contribute. Beyond publishing on the website, I'd be happy to help share approved project updates and articles through appropriate public channels to improve the visibility of Fineract and its community. I've been writing on LinkedIn for a while, so I can bring some experience in presenting technical content to a wider audience while keeping the focus on the project's work and contributors. I completely agree with the incremental approach. Rather than building too much upfront, we can start with a manageable scope, establish a consistent publishing cadence, and learn from the process. We can review progress after the first three months and decide what to improve or expand based on the community's response and our capacity to maintain it. I'm happy to take the lead on getting this started, work with everyone on the platform decision, and help make sure this becomes a sustainable community effort rather than something that's difficult to maintain after the initial launch. Thanks! ________________________________ From: James Dailey <[email protected]> Sent: 23 October 2026 06:15 To: [email protected] <[email protected]> Subject: Re: Fineract - calling all story tellers Hi I’m +1 on the starting something, blog on our site w Publish (on your) Own Site, Syndicate Elsewhere, but let’s please stay incremental. We have blogging capabilities in the wiki so it’s more about bringing that content into a blog section on our website. And generating content! Will someone step up to manage and edit for style and content one entry per month or more? Ie run a small marketing effort over several quarters or years?? It’s easy to start and harder to maintain. Always. On Thu, Oct 22, 2026 at 11:45 AM Priyam Priyanshu <[email protected]<mailto:[email protected]>> wrote: How about adding a blog feature to our Fineract Site itself, many oss maintain their own blog driven by the community. Currently we don't have one, if the community agrees I can add the functionality and maintain On Thu, 22 Oct 2026 at 9:05 PM, Adam Monsen <[email protected]<mailto:[email protected]>> wrote: I recommend both, following POSSE<https://indieweb.org/POSSE> - Publish (on your) Own Site, Syndicate Elsewhere. So in this case we'd publish first on, for example, our blog<https://cwiki.apache.org/confluence/pages/viewrecentblogposts.action?key=FINERACT> (looks like we've used that a bunch in the past). Then we copy/paste the link to the blog post on socials and/or syndicate (copy/paste and refer back, summarize and refer back, etc). We should probably add a link to the blog at https://fineract.apache.org/#resources or https://fineract.apache.org/#reference , too. On Thu, Oct 22, 2026 at 6:39 AM Aira Jena <[email protected]<mailto:[email protected]>> wrote: The blog will be posted on LinkedIn or Fineract Site ?
