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.
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.
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.
> we click a play button to start an elixir runtime based on that metadata code block
Can you show a concrete example? IE a real production url running this?
What is "metadata"?
In Docusaurus you can have a live playground evaluating on your browser, or you can embed any embeddable playground if it requires a server integration.
> with this component, we then issue commands to inspect state, manage elixir "processes" in the runtime, etc
Another example would be useful.
So this is just an embedded widget to interact with something remote? Why can't this be built as a React component that you can add to any Docusaurus page?
---
It looks to me that you don't need maintainer knowledge to build that, and React knowledge is enough.
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.
I'm not sure to understand what you mean by "Docusaurus is static".
Docusaurus builds static pages and allows you to plug JS/React code anywhere in your docs, so it's quite interactive and can run anything that can run in a browser, including REPLs.
I read the Fly article but still don't really understand what Livebook is about.
They say they use Livebook themselves, but the examples linked to only display a regular non-interactive doc to me.
Do you have any production url showing me an experience that is possible in Livebook, and impossible in Docusaurus?
As the Docusaurus maintainer, I stand by behind these ideas. Markdown is a portable format, and I'd like to make Docusaurus/Obsidian work well together in the future.
It's taking a long time because there are edge cases to figure out if we don't want the upgrade to be painful for certain sites, notably the ones using anchor links or i18n. It's not far from the end so hopefully mdx2 will be merged soon.
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.