Google Docs

hello, check out astro.docs and firebase hosting https://firebase.google.com/pricing. I really like their island inftastructure and its easy to deploy too. about the hosting you have a very cheap plan now with firebase you will pay as much as you use. You can also use your current hosting provider and move to firebase or somthing else if you run into the limits of your current hosting.

Consider leveraging Next.js for your NGO's knowledge-sharing platform, ensuring a seamless user experience. Combine it with Payload CMS for flexibility, moving away from WordPress. Optimize costs by exploring serverless architecture on platforms like Vercel or Netlify, allowing scalability without a substantial increase in hosting expenses.

You should take a look at Notion.so. I'm using it personally to manage my code/snippets, how-tos, and pretty much all of my knowledgebase management. It's become my second brain. With my team, we collaborate on Notion Kanban boards for project management, document collaboration, and since our company uses G-Suites, I'm using an unofficial integration (via Zappier and notion-automations.com) to import our google docs into customized notion databases to improve discovery/access (less searching, more doing) - Notion's databases support multiple views for databases: Table, List, Gallery, Calendar, Kanban, and Timeline views. Documents we collaborate on live on a notion "page" where we can @comment inline or on the overall document using a comments tool a the top of every document. We also have a Slack integration that notifies users in slack channels when there's a comment on a document or database they're following or something is assigned to them. Block creation, text/code/snippet formatting are done using markdown. Notion has integrations with Trello, Miro, Gdocs, MS Excel, Word, and others. They are working on an API to enable more customization and integrations. Most important, you are not locked into their ecosystem. If you ever decide to leave Notion, you can export all of your content in markdown, pdf, and html.

Me and a lot of colleagues have done documentation collaboratively with https://hackmd.io/ which also comes as an open source fork as https://hedgedoc.org/. The first has commenting function, the latter hasn't. Both make it easy to do doc sprints synchronously which means everybody is on the phone at the same time and write down documentation. As you do this with Markdown you can use your writing with https://squidfunk.github.io/mkdocs-material/ e.g. which is a static site generator running on Python and build beautiful documentation from Markdown files. If you want to build with https://gohugo.io/ I recommend https://www.docsy.dev/ theme.

We do scholarly writing and documentation with GitLab which we host on-premise. GitHub and GitLab come with sophisticated workflows for commenting and quality assurance if you learn to branch and merge which is for a lot of folks a steep learning curve. To onboard colleagues I recommend starting with HedgeDoc first and then migrate to more advanced workflows with Git(Lab|Hub).

Of all the content management systems out there, contentful seems to be the most flexible. It consist of an user interface with an API a front end app can retrieve data from.

It makes no assumptions about how your data is presented or structured, and you can form any kind of content in the interface. Architectural portfolio with square footage attributes? Check. Carousel section on a page? Check. A blog? No problem. Entire landing pages consisting of sections that have child items in them and attributes for each child? Not an issue. Image hosting / cdn and resizing? No problem. Character limits? Widely supported. Multilingual? Easy peasy

There are two parts of the interface. Content types and content items. Content types is just a definition of how a content item is structured, you can add fields such as title, unique id, image, rich text, lists of child content items, etc. And then the API will just return a list of content items in JSON array or object format.

There is service integration with common apps, or data sources.

Because it’s just an API call, you can use literally any tech stack with it. It won’t stop you from using MySQL or any other technology alongside it. No messing about compilation, Java, maven, like with AEM. No being constrained to the CMS’s programming language or hosting environment like with Wordpress (to an extent, wp has an API too). You can integrate it with any app, whether it be serverless, on a vm, or inside a docker container.

Downside is the front end is really up to you. It’s just a cms for structuring your data. No preview though. How you present it is not handled by contentful. It is it’s greatest strength and not a weakness though

Hi Kamil, Have you considered Adobe Experience Manager (AEM)? It is not completely open-source but is built on top of many open source modules - like Apache Sling, Apache Felix, has a great deal of open-sourced core components, supports SPA - React and Angular Recently and can be deployed as a cloud service. Good luck in your search!