ML-airport-configuration VS Zato

https://github.com/nasa/ML-airport-configuration

Donation is the normal term for proejcts joining the foundation - in doing so you establish a steering committee where members are entitled to voting rights. To graduate as an incubation project, 5 organisations need to join your board and the project is thus the priorities of the project will no longer be driven by just one organisation.

In the short term there is still a full time internal team staffed and maintaining the project, but excitingly we now have a mechanism for new collaborators to properly come onboard.

Yes, the article is correct, there is a market for Markdown sites and related products.

Our Zato website is in Markdown: https://zato.io

We have a purpose-built static site generator, which makes sense in our case because:

* The resulting site is very fast, seeing as there is no need for runtime generation of any assets / HTML / any kind of resources

* It is easier for developers to work on documentation because they already know Markdown

* It is easy to statically apply filters such as spell checkers for multiple languages during the build

* Various optimizations can be applied, e.g. incremental builds or on-demand builds

The drawbacks are:

* Non-technical translators may have a difficult time working with anything but either their own specialized tools or MS Word and they consider Markdown to be "advanced"

* Sometimes you work with writers who are not technical at all and who will not understand what a build system is even if they are open to the idea of learning Markdown itself

Thus, there is a market for a lightweight CMS that would enable non-technical people to author Markdown in their browsers, without a need for any command line usage.