I took the redesign of Passion for Coding as an opportunity to learn Twitter Bootstrap and also to learn som PHP by writing a WordPress theme.
Bootstrap is Awesome
Working with Bootstrap is totally awesome. For the first time when doing web page layout I didn’t have divs jumping around all over the place with a minor change in one place wreaking havoc to the entire layout.
I had no intentions to create any graphically exciting design. Actually I was quite happy with the clean simple layout I had before – until I opened it on a tablet or even worse on smartphone. So what I wanted was a simple, clean layout that set focus on the content and works fine for reading on all kinds of devices.
Welcome to the redesigned Passion for Coding!
While the design probably looks familiar, there are some changes. The old theme was a child theme to the WordPress standard twenty eleven theme. This new theme however is a brand new theme I’ve written specifically for Passion for Coding. It uses Bootstrap 3 and is fully responsive. I do quite a bit of my own reading of blogs when riding the train to the office, having only a small phone screen to read on so I know how important it can be to provide a good mobile experience and now I (finally) do that myself.
I’ve also decided to go back to Google Adsense for advertising trying their responsive ads. I know that ads are never popular, but if I create the content and pay for the hosting, then I think it’s fair that there are some ads.
I decided to write the theme myself starting with nothing, in order to learn Bootstrap, PHP and WordPress. It has sometimes been challenging, but it’s always very valuable to dig into a new language or platform to learn and I’ve definitely learnt a lot. I will share some details in a separate post later.
For now, I hope that the new design offers a better reading experience. If you experience any problems with the site, please leave a comment or drop me a mail/tweet to let me know.
It’s now two years since I started the Passion for Coding blog. I’d like to share a few thoughts about blogging and also say a big THANK YOU to everyone reading and commenting and sharing my posts. It is strange to know that my writing now reaches to almost every country in the world – to far more places than I have ever been or will ever be able to visit myself.
I would also like to thank DZone for accepting me as one of their Most Valuable Bloggers – without you I would never had got the same number of visits.
Code or Methodology Posts or Both?
Since the start of the blog I’ve published 140 posts about a variety of topics involving software development. There have been a number of posts with code samples (all code is now available in a GitHub repo). There have both been a number of instructional posts about how something specific works, but also a number of utility classes that are ready to use. I do put pride in having test run all the code I publish on the site. I do know that it works (at least until I forget to HTML escape something containing generics and all
> go missing, spoiling the code).
I’ve also written a number of posts on software development methodology, with a clear focus on scrum. Personally I do like to mix the different kinds of writing. I hope that you enjoy reading the mix too – but I’m very interested on what you think about the mix. Would you prefer more code? Or more scrum thoughts?
All the code samples on this blog have been tested and run before publishing. The sample code is now available on GitHub.
Most of the time when I write code for the blog I do that in a number of test projects that I do have. So far I’ve kept them in an svn repo, but the time has come to move on so I’ve now pushed all the test code to a public GitHub Repo. I do try to keep the code samples in the posts complete, but sometimes it is simply not possible to add all the supporting code needed to the post itself. Now everything is available to use in the repo.
The code that is intended for reuse is mostly located in the
CodingAbelNu.Utilities library. I started it out with the intention that it should be a nice-to-have utility library that could get released separately. I don’t think that I’m there yet, but feel free to use it as it is.
In just a few days, Google will kill Google Reader. Moving to Feedly is extremely simple – do it now, before it’s too late and your precious feed setup is lost! Just go there and hit “login” and the migration is done.
This post is not about coding or software development, it’s about feed readers. From my statistics I know that 80% of my subscribed readers are using Google Reader. It used to be 90% before Google announced that they would kill Reader. That means 80% of you have to make a decision in just a few days or you’ll loose your feed setup. I was a Google Reader user too and decided to make the switch about a month ago and picked Feedly.
Migrating to Feedly
Migrating to Feedly from Google Reader is really simple since Feedly used to run on the Google Reader backend. Just go to http://feedly.com and sign in with your Google account and you’re done. All subscriptions are automatically imported into Feedly and available once Google Reader is killed.
I like the site, but it’s in the Android App I’m doing most of my reading.