Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Roll your own! It's fun. My site is a custom made file-based blogging platform written with Python Flask, and it's a joy to use since I made it exactly how I wanted it to be made. One feature that I really enjoy is being able to call source files into the post. This allows me to create/update code snippets extremely easily. Markdown + calling includes on my source files is exactly what I needed to efficiently produce content, so I made it myself.


What about bloggers that want to be developers?

Can you do a writeup/tutorial for your setup?


> Can you do a writeup/tutorial for your setup?

Sure. I can just open source the site after I remove some private stuff and improve the documentation a bit.

I have a similar site (my old web design partnership vertstudios.com) that already has an open source mirror[0], but it doesn't have source file inclusion or tags like my joequery site.

[0]: https://github.com/joequery/Vert-Flask

The article linked in the repo has information on setting up nginx and uwsgi when it comes time to run the thing live.

Keep in mind that my site's workflow isn't perfect by any stretch, but it's perfect for me. That was my main point.


>Can you do a writeup/tutorial for your setup?

Actually, Flask tutorial uses a blog application as example

http://flask.pocoo.org/docs/tutorial/introduction/


I have a simple blog engine that can be readily deployed on Google App Engine - https://github.com/prakhar1989/CS253-Blag

It features Stvtle like blog post editing (distraction free), supports markdown and a draft system.


I just started playing with Hyde as a blog engine, which is a static site generator for Python. So far the only blog posts are about setting it up! http://esd.io/

Flask is very cool too, though, and if you want your sites dynamic, I'd recommend it. I choose Hyde because my eventual goal is speed: I want to see how fast I can get a "real world" page to load.


Wouldn't security be an issue?


Of course, security is always an issue. I kept everything as simple as possible to reduce the number of ways an attack could exploit my site. I don't believe it to be any less secure than your standard Wordpress site.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: