When comparing Pelican vs Sphinx, the Slant community recommends Pelican for most people. In the question“What are the best static site generators?” Pelican is ranked 1st while Sphinx is ranked 16th. The most important reason people chose Pelican is:
All code is available on GitHub.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Open source
All code is available on GitHub.
Pro Active community
Pro Uses a versatile, powerful and easy to use templating engine
Uses Jinja.
Pro Code syntax highlighting
Uses Pygments for code highlighting.
Pro Support for unique templates per page
Adds flexibility to create variety of websites.
Pro Content can be written in multiple formats
Supports reStructuredText, Markdown, or AsciiDoc formats.
Pro Import your existing blog from many sources
Pro Customisable Themes and support for Plugins
Makes it flexible to cater to creation of variety of websites in addition to blogs.
Pro Multilingual
Easily handles multiple languages, like EN, FR, etc.
Pro Quite fast even for sites with thousands of posts
Can spin up an build sites with thousands of articles in a matter of seconds even on very old computers.
Pro Good search performance
Pro Fast indexing
Since Sphinx talks directly to the database, indexing speed is very fast.
Pro Rich database-like querying features
Pro Batch and real-time full-text indexes
Pro SQL database indexing
Pro Advanced full-text searching syntax
Pro Easy application integration
Pro Non-text attributes support
Pro Non-SQL storage indexing
Pro Good relevance ranking
By default results are ranked by relevance. If you wish, you can adjust the ranking by giving more weight to certain fields.
Pro Excellent scalability
Pro Distributed searching
Pro Flexible text processing
Cons
Con Theme inheritance doesn't seem to be a priority
There have been endless discussions for years but theme inheritance still doesn't seem to be a thing. You can "inherit" from the simple theme so you don't have to have all the required files in your theme, but that's as far as it goes.