Great Docs started with a premise: you should be able to point a tool at
your Python package and get a documentation site that looks good without
any design work. Run great-docs init, run great-docs build, open the
result in a browser, and you are done. That three-command workflow has
not changed since v0.1, and the simplicity of the entry point is
important. But behind that simple surface, ten releases have added a
world of capability for when you are ready to go further.
This is a companion discussion topic for the original entry at https://opensource.posit.co/blog/2026-05-13_great-docs-ten-things/