Google Docs

We are an NGO and we got from a partner a new design for our knowledge-sharing platform https://morethandigital.info/en/. We have now almost finalized the UI/UX Design in Figma with all the flows and functionalities for the future platform.

Next.js came up often as a possible solution for our future "platform" but I am not sure, also I found Payload CMS in the process as WordPress seems to be not the right decision for us. The next generation of our knowledge-sharing platform should also have more functionalities as the current version is only an article publishing platform.

Some of the new functionalities we thought of to make consuming/sharing knowledge easier:

• Better Author / Organization / Publication pages
• Peer-Review Feedback and Translation Feedback
• Translation flows and integration of machine translation suggestion
• Collaboration and live collaboration (like @{Google Docs}|tool:4575|)
• Follow Creators, Subscribe to Authors/Organizations
• Create collections (collections of articles) and share them
• As well as "Save for later" and other functionalities that help better interaction with content

As we are overwhelmed with the choices it is really hard to determine what technology stack/choices we should make in order to keep it as lean and easy as possible without creating too much overhead. Is there any "Best practice" you could recommend to allow for a low-cost development of our Design into a scalable infrastructure that doesn't cost thousands a month for hosting etc. (currently we serve 2.5 million people with 24 USD in Hosting and 20 USD in CDN with a WordPress system)? So please don't suggest options that are 100s of USD per month or thousands per month as we simply don't have the budget.

Any help/info/hints/recommendations are really appreciated!

We are trying to find a good tool for internal technical documentation. E.g. playbooks for site operations, or how-to docs on how to use a particular library. The documentation will contain a lot of code/command snippets.

We currently use Google Docs because of its very good WYSIWYG capabilities, and most importantly, its commenting system that allows us to discuss a particular issue and keep record of that discussion. However, Google docs is not made for code documentation so it's a bit clunky sometimes (e.g. it will capitalize the first letters of sentences etc...).

We briefly tried the GitHub wiki, but it severely lacked on collaboration/commenting and ease of editing.

What tools do people recommend for editing internal documentation?

If you're a developer using Google Docs or Google Sheets... just stop. There are much better alternatives these days that provide a better user and developer experience.

At FeaturePeek, we use Slite for our internal documents and knowledge tracking. Slite's look and feel is similar to Slack's, so if you use Slack, you'll feel right at home. Slite is great for keeping tabs on meeting notes, internal documentation, drafting marketing content, writing pitches... any long-form text writing that we do as a company happens in Slite. I'm able to be up-to-date with everyone on my team by viewing our team activity. I feel more organized using Slite as opposed to GDocs or GDrive.

Airtable is also absolutely killer – you'll never want to use Google Sheets again. Have you noticed that with most spreadsheet apps, if you have a tall or wide cell, your screen jumps all over the place when you scroll? With Airtable, you can scroll by screen pixels instead of by spreadsheet cells – this makes a huge difference! It's one of those things that you don't really notice at first, but once you do, you can't go back. This is just one example of the UX improvements that Airtable has to the previous generation of spreadsheet apps – there are plenty more.

Also, their API is a breeze to use. If you're logged in, the docs fill in values from your tables and account, so it feels personalized to you.