Hacker News new | ask | show | jobs
by abhv 3770 days ago
Main question: how is this better than Hugo (really simple one-binary application), and how is this better than jekyll?

Just saying that it is not "just for blogs" doesn't really explain how it is better for a use-case. Maybe pinpoint the issue?

1 comments

My main use case are technical-oriented websites.

So I need to support content like a manual, a faq, news, feature requests, essays, and yes, also a blog. I also want good navigation support, and an easy way to refer to other project pages. Furthermore, I want programmatorial flexibility, which because of my background means Python and Jinja2 templates.

I wrote this because I didn't find an existing solution that met those requirements. I am not claiming it is "better" in a general sense than anything else - I think it all depends on your requirements and background.

> I need to support content like ... feature requests

How do you accept feature requests with only a static backend?

The sites are typically in a git repo, so content updates are through commits or pull requests.

For an example of feature requests that are ordered by status and number, see http://dev.myhdl.org/meps/