slorber

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.

Honestly, can we even trust a technology that is not 1.0 ?

Impossible yet it often happens the same old link gets featured everywhere at the same time :)

Docusaurus maintainer here. Can you expand that feeling? What makes you feel Docusaurus as complex?

Wonder if it's not possible to use this dark matter product (normally for Astro) with Docusaurus worth giving it a try https://getdarkmatter.dev/

Docusaurus maintainer here

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.

Hey there

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.

Let me know if you have any questions

React vs Vue is a quite significant difference if you plan to customize it: you'd better be familiar with the underlying tech

FYI Software Mansion ran a React-Native survey last year with almost 2000 answers.

Here are the results: https://results.stateofreactnative.com/

My personal biased opinion: React-Native is awesome and keeps improving.

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.

Hey, Docusaurus maintainer here.

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?

That's because React developers are not on hacker news anymore, they are all reading my newsletter thisweekinreact.com (wink wink)

React dev?

Try https://ThisWeekInReact.com (disclaimer, I'm the author)

I also enjoy Bytes, JavaScriptWeekly, NextJS Weekly, ESNext News, Web Weekly and many others

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.

Docusaurus maintainer here, happy to read your feedback ;)

Docusaurus maintainer here. Wrote a Twitter thread explaining why Docusaurus is not a good fit in this case. https://twitter.com/sebastienlorber/status/14527225683902218...

Old but still relevant.

Sorry from the Docusaurus team.

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.

Docusaurus is a great way to start a static blog. Give it a try!

Lots of features included: RSS, sitemaps, multi author, regular/guests, tags, unlisted/draft, i18n, accessibility, very customizable...

My newsletter is based on it: https://thisweekinreact.com/ I edit content there first in Markdown and then copy paste to ConvertKit

https://thisweekinreact.com for React devs :)

We could apply lazy loading only after the 2nd image maybe

Yes, great choice :)

Docusaurus maintainer here. I don't really understand what you mean, considering we don't have official support for API documentation, but have a plugin system allowing you to build your own support.

And we have a few OpenAPI plugins, and redocusaurus.

A Docusaurus plugin MDX makes it possible to implement this with client-side React in case you want to create an interactive client alongside editorial text content.

See what Courier did just using React in MDX, and without any Docusaurus plugin: https://www.courier.com/blog/how-we-built-our-documentation/ https://www.courier.com/docs/reference/send/message/ (their site is opensource)

Thanks, I wasn't alone in this project started internally at Meta a few years ago ;)

Hey, I'm the maintainer of Docusaurus

For what it's worth, I'd really like to build a Second Brain, Obsidian, Digital Garden, Zettelkasten plugin, at least for myself. We have the infra to make it possible as a plugin, and you can probably hack the docs plugin to add [[keyword]] as a link to a doc tag page in the meantime (using a custom remark plugin)

Images can be co-localized with the content, although it increases the size of your Git repo over time

You mean Openapi?

Docusaurus has at least 2 community openapi plugins

+ 1 Redoc community plugin

+ it's possible to build something custom with MDX,see Courier doc: https://www.courier.com/blog/how-we-built-our-documentation/

What is missing exactly?

Not sure to understand what you mean here, can you explain?

Docusaurus is a static site generator, a bit similar to Gatsby. It's opinionated toward docs/blog/pages but you can also use it in a more generic way.

Great! Let me know if you have any question

Thanks from the Docusaurus team ;)