sphinx VS furo

Sphinx is primarily known as a documentation generator, but it can also be used to create static websites. It excels in generating technical documentation, and its support for multiple output formats, including HTML and PDF, makes it a versatile tool. Sphinx uses reStructuredText for content creation and is highly extensible through plugins.

Sphinx a documentation generator or a tool that translates a set of plain text source files into various output formats, automatically producing cross-references, indices, etc. That is, if you have a directory containing a bunch of reStructuredText or Markdown documents, Sphinx can generate a series of HTML files, a PDF file (via LaTeX), man pages and much more.

Notable mentions to [Sphinx](https://www.sphinx-doc.org/). It's workflow is more tuned to the "book" format rather than the blog, forum or thread format.

Currently trying out Sphinx (https://www.sphinx-doc.org) and the trying to get the autodocgen feature to see what that can do.

So, I've documented my code and now I need a .PDF with this documentation. Is there any easy way to do it? Once I used Sphinx but it generated a not so easy .TeX.

AutoPyTabs allows you to write code examples in your documentation targeting a single version of Python and then generates examples targeting higher Python versions on the fly, presenting them in tabs, using popular tabs extensions. This all comes packaged as a markdown extension, MkDocs plugin and a Sphinx, so it can easily be integrated with your documentation workflow.

Honestly, I think it's just an issue of documentation. For example, if there was an easier way to document @overload functions, that would help (cf. https://github.com/sphinx-doc/sphinx/issues/7787)

We use sphynx for our pipeline documentation for all technical details Classes , packages and functions docstrings using reStructuredText (reST) format

I like Sphinx [0] with the MyST Markdown syntax [1]. There is a related project, Myst NB [2], which enables including Jupyter notebooks in your site. There is also a plugin for blogging [3].

[0]: https://www.sphinx-doc.org

Sphinx is the go-to tool for documentation. It took me a while to understand how to use Sphinx, but I now have a decent workflow with MyST which allows me to write all the docs in markdown. My sphinx-markdown-docs repo shows an example of what I do.

Sphinx has more and in my opinion better themes (especially the popular Furo them). I also think it's better for handling large and complex sites. It's way more extensible. That there are far more Sphinx users means that you're more likely to have community support if/when you run into issues.

My company uses sphinx, in particular the furo theme: https://github.com/pradyunsg/furo. I'd like to use something like this to start documenting our Rust repositories. Is this possible on stable?

On another note, what did you dislike in Sphinx ? I found it pretty easy to work with until now and there are quite nice themes, like Furo (https://github.com/pradyunsg/furo), which is actually pretty similar to your current docs theme. I used it recently for one of my projects (see https://francois-rozet.github.io/piqa/piqa.psnr.html).

reminds me a lot of Furo which is used by big names such as urllib3, pip, attrs, psycopg3, black

This theme was created by one of the maintainers of pip, which is where I first saw it (https://pip.pypa.io/en/stable/). Here are some of the things I like about it:

- Well-chosen, proportionate font sizes and spacing.

- Table of contents sidebars for both the current page and the whole documentation site.

- Fully responsive: sidebars disappear in narrow windows or small screens, but can still be popped out.

- Clean color scheme with good contrast, and full support for dark mode (see screenshot at https://github.com/pradyunsg/furo/blob/main/README.md).