We have been waiting for years to have that typical Yaml feature.
This lets you create variables in your Yaml actions workflows that you can reuse later, including more complex data structures like objects and lists that you can spread into jobs.
TLDR: less duplication, although the syntax is a bit awkward.
I agree the md editing story for non-dev contributor is not great.
You can try a git based CMS like Tina, they have a Docusaurus starter/example.
StackBlitz web publisher is also a good solution, allowing you to run Docusaurus directly in the browser in a very simple interface allowing you to commit or send PRs easily. No need to install nodejs locally, and you get a real preview.
I work for Meta Open Source, maintaining Docusaurus. It's a SSG that let's you focus on writing content (Markdown/MDX) and will help you ship flexible and beautiful docs and blog static sites.
We just released a new major version of Docusaurus, after 1 year of work once v2.
Thanks!
I'm not the original author but maintain it since mid 2020.
Meta has always been involved, the project was created internally at Meta around 2016 to replace a Jekyll docs boilerplate that was difficult to manage when deploying hundreds of docs.
After reading this article, I'm still not sure to understand what Livebook is.
Can someone show me a real production url of what is possible to achieve in Livebook and impossible/difficult to achieve with other tools?
I'm the Docusaurus maintainer, and making your docs interactive, and giving the ability to run the documented project inside its doc does not feel like something new.
This lets you create variables in your Yaml actions workflows that you can reuse later, including more complex data structures like objects and lists that you can spread into jobs.
TLDR: less duplication, although the syntax is a bit awkward.