3 ms·

Thanks for the feddback No drawbacks to share compared to your previous stack?

• tony 5y ago
  I inherited 11ty from a boilerplate, but to be fair to them, people do amazing stuff with it: Example https://web.dev/how-we-build-webdev-and-use-web-components/ https://web.dev/how-we-build-webdev-and-use-web-components/. Back to docusaurus, one weakness is the lack of API documentation tools. Check to see if the programming language for your project has a docusaurus (or a markdown) API generator. For Python, if you use docusaurus, there's no API documentation generation is nowhere near Sphinx. Sphinx uses sphinx.ext.autodoc (https://www.sphinx-doc.org/en/master/usage/extensions/autodoc.html https://www.sphinx-doc.org/en/master/usage/extensions/autodo...). The dream would be getting a python API like this ported to docusaurus: https://libtmux.git-pull.com/api.html https://libtmux.git-pull.com/api.html This can supposedly do it via exporting the API to markdown: https://github.com/NiklasRosenstein/pydoc-markdown https://github.com/NiklasRosenstein/pydoc-markdown