# I couldn't sleep so got up for a drink and did a little more work on the non-WordPress version of the blog.

It's still intrinsically linked to WordPress because it currently just retrieves the post sections from the database that are created within the main site but, ultimately, I'd like to make it a fully self-contained system.

I'll need to sort out some kind of functionality for logging in and will need to rethink posting and how sections are stored. What will be a little more problematic is working out commenting should I decide to include it.

I would also lose webmentions because my coding skills really don't extend as far as rolling my own solution for that. This, in turn, means that I would lose the current "related posts" feature.

I'm not entirely sure where I'm going with all of this, or what compromises I'm willing to make, but it would be nice to be able to say I use my own blogging engine.

# A rudimentary login system has been built and appears to work okay. I've also forked the database being used so that I can start working on the posting functionality.

# Liked: Just One Thing, 34 of 101 - Nicholas Bate...

Fresh starts don’t need a specific date, nor necessarily a SMART goal.

They do need a decision followed immediately by a first action.

  1. devilgate says: #
    It feels to me as if what you’re really after is a static site. Get away from all that database trouble. Write in Markdown, run a script to generate the HTML, and all is well. I can recommend it. It does have the question of how best to handle comments. There are various possible solutions, though.
    1. Colin Walker says: #
      Because I'm going to be writing and editing inline I'm still going the database route as everything will be instant.

Leave a Reply

Your email address will not be published.