5. FRAMEWORK
• “...a drop-in code library
used to facilitate
development of a theme”
“A front-end web development
framework is simply a
collection of production
ready HTML/CSS/JavaScript
components that we can use
in our designs.”
6. CHI LD THEME
• Requires a parent theme
Hint - many WordPress
“frameworks” are parent
themes
10. FRAMEWORKS
PROS
• Base CSS
• Grid system
• Responsive
• Classes defined
• Typography
• Defines stuff you’d forget
about
• Broader than WordPress
11. FRAMEWORKS
CONS
• Not a stand-alone theme
• Usually included in a
theme’s functions.php file
• http://www.punkchip.com/w
hy-dont-you-use-bootstrap/
16. CHILD THEME
PROS
• Quickest and easiest choice
• DO THIS rather than hack the
theme
• Parent theme can carry the
weight
• Bork the child and the parent
is OK
• Works immediately
• 80% of the work is done for
you
17. CHILD THEME
CONS
• At the mercy of the parent
theme’s code
• Quality
• Security
• Upgrades
• Compatibility
• Not the leanest strategy
34. QUESTIONS TO ASK
• How will it (the site /
framework / parent theme)
change?
• Upgrades?
• Redesigns?
• Improvements?
• Budget? Timeframe?
• What will you be asking
the site to do?
• Heavy traffic?
• Heavy database use?
• Who’s going to support
it?
• What are you comfortable
with?
35. “So what do you recommend?”
– A N Y O N E W H O ’ S S T I L L W I T H M E
36. MY ADVICE
• Research the differences
between frameworks
• Choose one parent theme
and build several child
themes on it
• When you’re ready, find a
starter theme that you like
and use it for everything