This Blog Framework Ain't Perfect

I have been writing with this blog framework that I built for a few days now. It's not perfect, but it's mine.

I will continue to improve it, and will hopefully track it in here by crossing items off the not-perfect list.

Why is it not perfect?

• There is not a good way of getting a created/updated date for blog posts because of the way git handles the files on push to the server.
  • This causes ordering of blog posts to be random. I cannot easily control the order of the blog posts.
  • Every time I push a change to the server, the created and updated dates are the date of the push on the server. This is not the date of the last change to the file, it's the date of the push.
• There is no built-in commenting system.
• Titles cannot be whatever I want. They must be the name of the file.
  • I cannot easily control the capitalization of the title, since I am using .title()
• My local DB is the same as the production DB.

Why is it almost perfect?

• I get to write in just basic HTML. No complicated templating engine.
• There is built in traceability. Every change to a blog post is tracked on github.
• It is incredibly fast.
• No subscription fees.
• No bullshit analytics.
• No paywall

Despite these imperfections, it aligns perfectly with my philosophy about cutting out the bloat in web development. Simple, fast, and gets the job done without unnecessary complexity.