Building Themes in 2016
The Undiscovered Country
No Guidebook
Thought Exercise
Throw out all our old code
JavaScript Based
JSON API
Build Process
NOT ABSTRACT ENOUGH
What should a theme do?
Why do we even want a theme?
What if all our sites looked the same?
Visitors finding Content
Visitors Ingesting Content
It's About Visitors
Visitors are Users
User First
User First Everywhere
Less Functionality, More Presentation
Less Options, More Decisions
Design Matters
Design Really Matters
Developers QA Designers
Take Feedback Liberally, Accept Feedback Critically
Tools
Browser First Design
Browsers Browsers Everywhere
Design is an iterative process
More Libraries
RequireJS?
Browserify?
Less Bootstrap
Typeplate
Atomic Design
Smallest Component
Reusable Components
Wrong Today
Theme Tags are Outdated
Sticky Posts?
Fluid Layout?
Success of 2010
Does Core do Enough for Themes?
Menus Are Awesome
Menus Aren't Perfect
Custom Walkers
Taxonomies Are Awesome
Post Relations meh
Three Solutions to one problem
Post Collections
Collections Evolve.
Collections Are Fluid
Collections Matter
Rule Based
Zone Based
Semi-Fluid Zones
Today !== Tomorrow
Visuals are cyclical
Big Blue Headers will be back
All of this is guessing
Some may happen
Much Won't
Weezer (Blue Album)