Download as PDF, PPTX
Uploaded byKonstantin Kovshenin
Things I Wish I Had Known Before Developing a WordPress Theme
This document provides tips and best practices for developing WordPress themes. It recommends using WordPress coding standards, enqueueing scripts and styles properly, avoiding bundled scripts, using subdirectories and template parts, and better alternatives to query_posts(). It also suggests implementing core features, localizing themes, optimizing images and caching queries for speed. Overall it stresses the importance of building themes with a simple structure, backwards compatibility, security and following WordPress standards and best practices.
More Related Content
Similar to Things I Wish I Had Known Before Developing a WordPress Theme
Things I Wish I Had Known Before Developing a WordPress Theme
- 1. Things I WishI Had Known Before Developing a WordPress Theme Konstantin Kovshenin Automattic
- 3.
- 4.
- 5.
- 7.
- 8.
- 9.
- 10. Don’t Bundle Scripts Whichare Available in WordPress
- 11.
- 12.
- 13.
- 14.
- 15.
- 16. query_posts() is badand you should never use it “ ” — Andrew Nacin, WordPress Lead Developer
- 17.
- 18.
- 19.
- 20.
- 21.
- 22. Feature Bloat and PluginTerritory
- 28.
- 29.
- 30.
- 31.
- 32.
- 33.
- 34.
- 35.
- 36. Be a GoodParent (Theme)
- 37.
- 38.
- 39.
- 40.
- 41. if ( !function_exists( 'foo' ) ): function foo() { ... } endif;
- 42.
- 43.
- 44. Be a GoodChild (Theme)
- 45.
- 46.
- 47.
- 48.
- 49. function _s_categorized_blog() { $c= get_transient( 'cool_cats' ); if ( false === $c ) { $c = count( get_categories( … ) ); set_transient( 'cool_cats', $c ); } return $c > 1; }
- 50.
- 51.
- 52.
- 53.
- 54.
- 55.
- 56.
- 57.
- 58.
- 59. What Makes aGood WordPress Theme?
- 60. Great Design Ease ofUse Simple Structure Flexibility Speed Reliability Security
- 61.