Accomplish It With Core: Sliders, Galleries and MoreAndy Stratton
Building custom theme/plugin functionality using powerful built-in core API's / libraries. Thinking about things in terms of core functionality and rolling your own.
Accomplish It With Core: Sliders, Galleries and MoreAndy Stratton
Building custom theme/plugin functionality using powerful built-in core API's / libraries. Thinking about things in terms of core functionality and rolling your own.
This document provides an overview of how to write a WordPress plugin in 3 steps:
1. Plugins add functionality to WordPress through hooks like actions and filters without modifying core code. Actions call functions when events occur, while filters modify values being returned.
2. Plugins include metadata like the name, description, and author to display in the admin interface. Code is hooked into WordPress using actions and filters.
3. More advanced plugins can use objects to organize code, support custom post types and settings, and be submitted to the official WordPress plugin directory. Careful coding and documentation is important to create high quality, well-supported plugins.
This document discusses the importance of the WordPress community. It notes that the success and perception of WordPress relies on contributions from its community. Community members, including designers and developers, are encouraged to contribute code, report bugs, participate in forums and documentation, and ensure the security and quality of plugins, themes and code. The overall message is that the WordPress community itself drives the success of the WordPress platform.
My presentation from WordCamp Orange County 2012. Will post resources on my website eventually, need to re-code a design due to license issues I did not think about upon writing the presentation, d'oh!
Everything is Relative: Frameworks, Plugins & SEOAndy Stratton
This document discusses the pros and cons of using pre-built themes and frameworks versus custom coding. It notes that while pre-built themes can save time and money up front, they often require customization work that negates those savings and can introduce compatibility and security issues. It also argues that pre-built themes alone do not provide "SEO magic" and that content and links are more important ranking factors. The document recommends using best judgment on a case by case basis and educating clients on appropriate expectations.
My presentation at WordCamp Raleigh 2012 entitled "50 Shades of WordPress," a conversational piece on the commercial community (products and services) and the shady happenings of which users, designers and developers should be aware.
This document provides an overview of how to write a WordPress plugin in 3 steps:
1. Plugins add functionality to WordPress through hooks like actions and filters without modifying core code. Actions call functions when events occur, while filters modify values being returned.
2. Plugins include metadata like the name, description, and author to display in the admin interface. Code is hooked into WordPress using actions and filters.
3. More advanced plugins can use objects to organize code, support custom post types and settings, and be submitted to the official WordPress plugin directory. Careful coding and documentation is important to create high quality, well-supported plugins.
This document discusses the importance of the WordPress community. It notes that the success and perception of WordPress relies on contributions from its community. Community members, including designers and developers, are encouraged to contribute code, report bugs, participate in forums and documentation, and ensure the security and quality of plugins, themes and code. The overall message is that the WordPress community itself drives the success of the WordPress platform.
My presentation from WordCamp Orange County 2012. Will post resources on my website eventually, need to re-code a design due to license issues I did not think about upon writing the presentation, d'oh!
Everything is Relative: Frameworks, Plugins & SEOAndy Stratton
This document discusses the pros and cons of using pre-built themes and frameworks versus custom coding. It notes that while pre-built themes can save time and money up front, they often require customization work that negates those savings and can introduce compatibility and security issues. It also argues that pre-built themes alone do not provide "SEO magic" and that content and links are more important ranking factors. The document recommends using best judgment on a case by case basis and educating clients on appropriate expectations.
My presentation at WordCamp Raleigh 2012 entitled "50 Shades of WordPress," a conversational piece on the commercial community (products and services) and the shady happenings of which users, designers and developers should be aware.