This is really neat. I would love if something like this got included in the actual Sphinx documentation itself. It's hard to find extensions in the wild, and especially hard to judge the quality if multiple extensions do similar things.
I would also love to see an opinionated guide that suggests the best extensions for a task as well. For Read the Docs, we've been looking at trying to document and "bless" certain of the autodoc tools for specific languages. I really want Sphinx to grow outside of the Python world, and making sure good autodoc solutions exist for other popular languages would be a huge step. Cheers, Eric On Friday, October 31, 2014 6:43:56 AM UTC-7, Komiya Takeshi wrote: > > Hello, > > I made a list of sphinx extensions (for presentation at SphinxCon JP 2014). > Currently, it includes 230 extensions. > http://sphinxext-survey.readthedocs.org/en/latest/ > > It is based on searchs from PyPI and Googles (mainly github, gist and > bitbucket). > The extensions are classified into 18 categories. > > - autodoc > - builders > - changelog/version-control > - data-sources > - domains > - enhancement > - execute/result > - images > - integrations > - metadata > - multimedia/web-services > - roles > - search > - thesis/latex > - utilities > - website/blogs > > Please use it to search extension if you like. > > > BTW, for now, it is too hard to find and add new extensions to the list, > because the list is made manually. > If you have good idea to follow new extensions, please let me know. > > Thanks, > -- > Takeshi KOMIYA > -- You received this message because you are subscribed to the Google Groups "sphinx-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sphinx-users. For more options, visit https://groups.google.com/d/optout.
