When comparing Postagon vs Pelican, the Slant community recommends Pelican for most people. In the question“What are the best solutions for a personal blog?” Pelican is ranked 3rd while Postagon is ranked 27th. The most important reason people chose Pelican is:
All code is available on GitHub.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro WYSIWYG & Markdown editors
You can opt to use the What You See Is What You Get editor or write using Markdown syntax.
Pro Clean interface
Postagon is very minimalist and clean in its design.
Pro Google Analytics support
Postagon has built-in statistics using Google Analytics to help get a better understanding of your visitiors.
Pro RSS support
You can have people subscribe to your blog using RSS.
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.
Cons
Con No postagon link
redirected link to https://upstract.com/
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.