2. Two guiding rules
• Observe best practices for applicable
disciplines and technologies.
• Create modular components based on
common design patterns that are easy
for developers and clients to use.
11. Technology: Semantic HTML
Nicolas Gallagher’s “Anatomy of an HTML5 WordPress
Theme”
http://nicolasgallagher.com/anatomy-of-an-html5-wordpress-
theme/
Bruce Lawson’s “Designing a Blog with HTML5”
http://html5doctor.com/designing-a-blog-with-html5/
12. Technology: Accessibility
• IE6 should die, but it’s users may not
know better.
• “The power of the web is it’s
universality” – Tim Berners-Lee
http://www.w3.org/TR/WCAG20-TECHS/
Over the past 6 months I’ve played around with responsive designs in WordPress, and gotten one such project under my belt. With another on the go, and I suspect more to come in the future, I have decided to use my directed study to build a jumping-off point for these kinds of projects. This will allow me to distill my experience-so-far in to a platform that I can use for my own new projects, and provide as a useful tool to other developers.\n
It really is simple when you think about it. Awesome people have made projects available that distill tonnes of experience in to boilerplates and snippets that you can draw on.\n\nBeyond this “jumping-off point” though, I would like my framework to include modules that a developer or a client can use to save even more work. These modules would be things like carousels, navigations, features or promotions, forms, media elements and other design patterns common within a CMS.\n
We’re looking at the usual suspects as far as technology goes.\n\nThe whole thing is powered by WordPress, which is built on PHP and MySQL and so the project will be heavy on those two languages. There will likely be MySQL and DB development for some of the modules that I would like to build in.\n\nOne resource that I will be drawing from heavily is the HTML5BP.\n
We’re looking at the usual suspects as far as technology goes.\n\nThe whole thing is powered by WordPress, which is built on PHP and MySQL and so the project will be heavy on those two languages. There will likely be MySQL and DB development for some of the modules that I would like to build in.\n\nOne resource that I will be drawing from heavily is the HTML5BP.\n
We’re looking at the usual suspects as far as technology goes.\n\nThe whole thing is powered by WordPress, which is built on PHP and MySQL and so the project will be heavy on those two languages. There will likely be MySQL and DB development for some of the modules that I would like to build in.\n\nOne resource that I will be drawing from heavily is the HTML5BP.\n
We’re looking at the usual suspects as far as technology goes.\n\nThe whole thing is powered by WordPress, which is built on PHP and MySQL and so the project will be heavy on those two languages. There will likely be MySQL and DB development for some of the modules that I would like to build in.\n\nOne resource that I will be drawing from heavily is the HTML5BP.\n
We’re looking at the usual suspects as far as technology goes.\n\nThe whole thing is powered by WordPress, which is built on PHP and MySQL and so the project will be heavy on those two languages. There will likely be MySQL and DB development for some of the modules that I would like to build in.\n\nOne resource that I will be drawing from heavily is the HTML5BP.\n
We’re looking at the usual suspects as far as technology goes.\n\nThe whole thing is powered by WordPress, which is built on PHP and MySQL and so the project will be heavy on those two languages. There will likely be MySQL and DB development for some of the modules that I would like to build in.\n\nOne resource that I will be drawing from heavily is the HTML5BP.\n
HTML5BP takes care of baseline HTML5, CSS and JavaScript best practices. It includes things like “respond.js” and “modernizr.js” which shiv support for necessary technology in the bad browser, a build script to minimize load times, and CSS “normalization”— I read that it’s better than CSS resets. See “normalize.css.”\n\nHTML5BP is in a state of constant iteration as the state of the industry changes, I would like to make it so that future versions of the BP can easily be integrated in to the theme.\n
Semantics and accessibility are chief concerns when designing the HTML structure.\n