Let's Build a Custom Theme
1 like1,315 views
The document outlines the process of building a custom WordPress theme for WordCamp Orange County 2012, emphasizing the importance of organization, planning, and user experience. It encourages breaking down design into manageable components and utilizing WordPress functions to enhance efficiency and security. The document also advises on best practices, such as avoiding hard-coding and utilizing core WordPress APIs.
![Thanks ;]](https://image.slidesharecdn.com/2012-orangecounty-customtheme-120605002931-phpapp01/85/Let-s-Build-a-Custom-Theme-43-320.jpg)
Let's Build a Custom Theme
- 1. Let’s Build A Custom Theme WordCamp Orange County 2012 #wcoc @theandystratton
- 2. Plan Your Work. Work Your Plan.
- 3. Stay Organized. What needs to be dynamic? Organize assets: HTML/CSS/JS/images.
- 4. Static HTML/CSS. Highly recommended. Great reference point for possible browser bugs you may find later. Keep in a separate folder, use as starting point.
- 11. Our Blog Page...
- 16. Link to home page
- 17. Link to home page WP Nav Menu
- 18. Link to home page WP Nav Menu Custom Post Type (slide) Includes title and featured image.
- 21. Home Page Title/Content Custom field for anchor text and URL
- 23. Widgetized Sidebar for Footer
- 25. the_title()
- 27. the_title() Custom call to wp_list_pages() (followed by widgetized sidebar) the_content()
- 29. the_date() and comments_number()
- 30. the_date() and comments_number() Featured Image, the_title() and the_excerpt()
- 31. the_date() and comments_number() WP Nav Menu & Widgetized Sidebar Featured Image, the_title() and the_excerpt()
- 32. BREAK DOWN your design into MANAGEABLE WordPress components.
- 33. Let’s dive into some <code/>
- 34. Let’s Review.
- 35. Stay Organized. Plan your work, work your plan. Organization & planning are key to effective & efficient coding.
- 36. Isolate HTML/CSS. Fastest starting point. Focus on user experience, not dev experience. Best way to troubleshoot browser bugs later.
- 37. Chunk Things. Dissect markup into manageable pieces. Header, Footer, Sidebar(s), etc. Most can be done with copy/paste and replacing static functions with WP functions.
- 38. Doing It Right. Are you doing it wrong? Enqueue scripts/styles. Use hooks. Avoid hard-coding anything that can be dynamic, hooked or a widget when possible.
- 39. Optimized & Secure. Escape your output. Scrub your input. Use core WordPress API’s/functions
- 40. Steal Borrow. Refer to TwentyTen/TwentyEleven View other themes. Re-use your code & refine when appropriate.
- 41. Context Is Queen. What functionality do they need? Some pieces may not need to be implemented (e.g. some sites do not have blogs)
- 42. Maintain Experience. Design for the user, code for the admin. Maintain the WordPress admin UI when adding options/settings screens, etc.
- 43. Thanks ;]
Editor's Notes
- #2: \n
- #3: \n
- #4: \n
- #5: \n
- #6: \n
- #7: \n
- #8: \n
- #9: \n
- #10: \n
- #11: \n
- #12: \n
- #13: \n
- #14: \n
- #15: \n
- #16: \n
- #17: \n
- #18: \n
- #19: \n
- #20: \n
- #21: \n
- #22: \n
- #23: \n
- #24: \n
- #25: \n
- #26: \n
- #27: \n
- #28: \n
- #29: \n
- #30: \n
- #31: box icon with stuff in it?\n
- #32: HTML/CSS icons arrow to WP\n
- #33: Chunk from Goonies\n
- #34: HTML/CSS icons arrow to WP\n
- #35: HTML/CSS icons arrow to WP\n
- #36: HTML/CSS icons arrow to WP\n
- #37: HTML/CSS icons arrow to WP\n
- #38: HTML/CSS icons arrow to WP\n
- #39: \n