Blog Dev Update: Making Progress

Previously, I wrote about releasing an MVP (Minimum Viable Product) as soon as possible. In that post, I outlined a number of features that I had skipped over when building this blog, in an effort to get it out the door. What has changed since?

There were a number of features that I skipped, or rushed through:

  1. There was only one public-facing page, which contained all blog posts.
  2. Private back-end for creating posts lacked proper CSS styling after switching to using Tailwind CSS, so it looked very plain.
  3. A number of bugs had snuck in that I was not aware of.

While this is not a comprehensive list, it's actually a list of features that I've now added since the blog was launched on 8th of July! So everything mentioned above no longer applies.

An extremely MVP back-end that only I will ever see, unless I happen to post it in a blog post that is open to the public. Oops...

An extremely MVP back-end that only I will ever see, unless I happen to post it in a blog post that is open to the public. Oops...

Let's go through those again, this time with an update:

  1. Each blog post has a dedicated page, which means I can now link to the page from Twitter and other locations. Otherwise, I could only link to the home page ... and when someone wanted to click on the link, there was no guarantee that the same article would be at the top. While it's generally accepted that blogs must have a dedicated page for each article, I temporarily threw that out the door because there was no need for it with only a few articles. I could hold off on that for a week or two until I had time to implement it.
  2. The private back-end dashboard has had a significant refresh, and looks much nicer now. The image you see above is the 'before' shot, and below is the 'after' shot after re-styling to take proper advantage of Tailwind. I decided to make the editor look as close to the finished product as possible, so the title input field is styled to look like there is no input field!
  3. Bugs were squashed. More surfaced. Bugs were squashed again.

One addition that I'd like to add in the near future is testing. While I didn't mention it in the MVP post, I skipped testing and opted not to go for a TDD approach in this case. However, now that the blog is getting slightly more complicated (more than two pages), it's starting to become more critical.

How have your projects developed over time? Does this behind-the-scenes info interest you, and would you like me to post more of it? Get in touch and let me know. I enjoy writing this style of article.

Looking better, but it still has plenty of room for improvement!

Looking better, but it still has plenty of room for improvement!

UPDATE (31 OCT 2018): I've since updated the blog even further, and the hidden admin screen looks far nicer than that screenshot up above. I don't know what I was thinking! Plus, I've plugged in Laravel Nova for some added functionality, and enjoying it so far.

Meta