Photo Phinish Painting Website
A learning project focused on leveling-up with:
- Building practical websites for business clients.
- Mobile-first responsive design with HTML and CSS.
- Foundation for Sites front-end framework.
- Principles of clean, DRY, self-documenting code.
Table of Contents
This is a basic website for a local painting business, which uncoincidentally is run by my brother. This is the first website I've built that isn't a clone of a popular homepage like Apple or Mint. This is the first time I've used a front-end framework to build a website. I chose to work with Foundation for Sites.
How is Foundation used in this website?
- For the basic organization of the content into a grid format.
- To make the site more flexible and responsive.
- All the cool behavior, like the testimonials slider and the responsive top bar.
Highlights and Discussion
On choosing a front-end framework.
I am writing this README a few months after building the website (SAD!), but I recall a lot of hemming and hawing about whether I should use Bootstrap or Foundation. I also recall there were some other options, and I also recall receiving some sage advice that I should not be hemming and hawing so much. The basic arguments I heard were: "Bootstrap has more features and a larger community, but it's a bit bloated. Foundation is lighter weight and offers more flexibility, but lacks support." Or something like that. In the end, I decided to go with Foundation for two reasons. First, I am a contrarian and typically choose to side with things that are less popular. But second--and more seriously and more importantly and very much worth noting if you are a professional web developer--I chose Foundation because I liked their docs better. As a newbie, I found Foundation's documentation accessible, easy to use and easy to understand. The content is overall really well organized, and they have lots of great videos and explanations of how the different parts of the framework function and fit together. Really, from my perspective it was a no-brainer (after all that hemming and hawing, of course).
On not understanding how your website works.
Author, Credits and Links
- Jeff Bothe, @jmbothe