5 ms·

Wordpress is for bloggers, Github is for developers. Why not keep things simple?

• minimaxir 14y ago
  What about developers who are also bloggers?
  • jgh 14y ago
    gitpress
  • greghinch 14y ago
    http://jekyllbootstrap.com http://jekyllbootstrap.com
  • fosk 14y ago
    Gist
  • ecspike 14y ago
    Self-host.
  • spc476 14y ago
    Write your own blogging engine and self hosting? That's what I do.
    • booruguru 14y ago
      Why build your own blogging engine when so many open source solutions already exist?
      • mappu 14y ago
        Blogging engines are a simple enough concept that it might well be faster to write your own than to understand, configure and patch an unfamiliar system.
      • spc476 14y ago
        I originally wrote mine in 1999-2000, when there were very few options (if any). It works, so why not keep using it?
      • jfb 14y ago
        Because it's fun? And all the options suck in one way or another?
  • RegEx 14y ago
    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.
    • samstave 14y ago
      What about bloggers that want to be developers? Can you do a writeup/tutorial for your setup?
      • RegEx 14y ago
        > 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 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.
      • pav3l 14y ago
        >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/ http://flask.pocoo.org/docs/tutorial/introduction/
      • krat0sprakhar 14y ago
        I have a simple blog engine that can be readily deployed on Google App Engine - https://github.com/prakhar1989/CS253-Blag https://github.com/prakhar1989/CS253-Blag It features Stvtle like blog post editing (distraction free), supports markdown and a draft system.
      • 14y ago
  • mavroprovato 14y ago
    To add to the different choices, use octopress [1] with github pages [2]. I was evaluating various choices when I decided to create my own blog, and I found it was the only solution that: 1. Does not cost me anything 2. Lets me use my custom domain name 3. Gives me control over the generated HTML, but also gives me a starting point in the form of some decent looking themes [3]. 4. Actually works (I'm looking at you, bitbucket). 5. Gives me control over my content. Github decides to close its service? No problem, I got all my content and its history in my local git repo, so I can migrate it to anything I think is better. If there is another option that fulfills these criteria I would like to know. [1]: http://octopress.org http://octopress.org [2]: http://pages.github.com http://pages.github.com [3]: http://octopressthemes.com http://octopressthemes.com
    • ardianzzz 14y ago
      Toto & Heroku
• OGC 14y ago
  Yeah, the average blogger doesn't even _know_ half of these words.