Download to read offline
![The WordPress Codex:
“a flexible foundation
for quicker [theme]
development”](https://image.slidesharecdn.com/taketwo-slideshare-111012193810-phpapp02/85/Using-an-in-house-WordPress-framework-2-320.jpg)
More Related Content
Similar to Using an in-house WordPress framework
Using an in-house WordPress framework
- 1.
- 2. The WordPress Codex: “aflexible foundation for quicker [theme] development”
- 3. Dee on Genesis: “Fasterthan coding from scratch and security tested”
- 4. I’d reply: “...but theyuse #wrap where I use #pagewrap. Boo.”
- 9.
- 11.
- 13. What we wanted: “Fasterthan coding from scratch without the disadvantages”
- 14. Requirements • Preregister CSS& JS file structure • Hard code options to set during initial client consultation • Functionality common between sites • Filter HTML for common form plugins so it’s right
- 16. Options • meta tagsto appear in html <head> • theme options • content & attachment width • post formats • Widgets & menus to enable
- 17. Theme Repository • Wantedto put it back into community • Handy way of getting bug fixes/updates to previous customers • Free code review • Forces keeping up to date with the WordPress release cycle
Editor's Notes
- #2 \n
- #3 often operate as parent themes\nparent theme can be updated seemlessly\n\n
- #4 \n
- #5 Used to doing things my way\nRelearning will slow me down\nFrustrated & throw it away\n
- #6 needed to cover multiple scenarios\nblog to brochure sites\n
- #7 \n
- #8 \n
- #9 \n
- #10 Most frameworks incl options screens.\nadds to confusion in WP Dashboard\nadds weight to database (next)\n
- #11 adds weight to database\neach option is a database call (99)\n\n
- #12 adds weight to database\neach option is a database call (99)\n\n
- #13 design decisions aren&#x2019;t fixed\nmore combinations to consider during dev\nwhat we wanted (next)\n
- #14 disadvantages:\nworking someone else&#x2019;s way\ncode base may not be easy to understand\nadvanced features not needed most sites (library)\n
- #15 options - convert core functionality to a true/false (next slide)\ncss - include the basics, js - our base & a file ready for custom js\nfunctionality - editor headings, meta tags, sidebar registrations\n
- #16 not a css reset. WordPress was the motivation behind this\nwidget layouts add weight to css already\n\n
- #17 quick demo\ncopy files over, name theme, setup options, queue CSS\nset to theme in WP admin, make obvious CSS change.\n\n
- #18 * sounds like crap, was genuine motivation\n* if they&#x2019;re security minded will have disabled my FTP login\n* reviewers run check against theme data\n* themes which aren&#x2019;t updated in a while may get kicked out of repo.\n\n