Bayprogrammer Progress Update
24 Jan 2015
Decided it was time to take the next step on my new bayprogrammer.com website and work in CSS to bring style to the structure. I gravitate toward visual simplicity and minimalism with my websites, especially my personal sites– yet I do have an appreciation for balance and asthetics. (Side note: I do need to study typography!). So this past week I began crafting some simple styling for my site, and making small adjustments to the underlying semantic HTML structure as needed.
I am happy with the results. If you look at my previous post (Bayprogrammer Reboot) you will see that I started with (nearly) no CSS, just trying to get the basic semantic HTML generation set up using Jekyll. Now, with some minimal CSS, layered on top of normalize.css, I have a simple asthetic that works well on both the mobile web and on desktop.
While I feel I am making good progress on my personal website, there is yet more work to be done. The next thing for me to work on is my professional web development portfolio. After that I want to leverage a front-end framework to enhance the overall design and structure of my site.
Choosing a front-end framework
I plan to use either Twitter Bootstrap or Zurb Foundation. (Which I am unsure as yet, perhaps I’ll experiment with both before making a final decision.) I am interested in these for two main reasons:
First is expedience in having a better mobile experience. Why re-invent the wheel here; people with far more expertise and experience than myself have already worked out good baseline frameworks on which to build. Just as I use Jekyll to generate my personal website and I use Django for larger web application back-ends, I can leverage (and hopefully even contribute to) the good work of others for my own front-end development.
The second reason is to learn mobile and responsive best practices. I don’t like the idea of merely sprinkling “magic pixie dust” on my projects and getting results with no understanding of why or how the results are obtained. But it does make sense to choose a good front end framework to learn from by reading (ane even hacking on) its source code as I use it. That way I develop an understanding of how it’s built by people who know what they’re doing while reaping the rewards of their good work immediately.