I attended most of the developer track presentations at Boston’s Wordcamp 2012. I learned about some interesting tools and techniques that I’d like to document for myself and others.
Talk Optimizing for Speed by Ben Metcalfe
- YouGetSignal’s Reverse IP Lookup – Shows you how many other hosts live on the same IP Address. This can be helpful for anyone using shared hosting or maybe VPS.
- Debug Bar – Get debugging information from each page WordPress page load.
- Google XML Sitemaps – Delete this plugin if you have it. (I had it.)
- YSlow – Get load times and optimization tips of a page request.
WordPress as a Web Framework by Sam Hotchkiss
- MVC frameworks for WordPress
- _s Theme – Use Automattic’s Blank Theme as a good starting point.
Automating frontend workflow by Aaron Jorbin (blog post, slides)
- Autojump – Jump to frequently used directories
- Commander.js (nodejs) – Script working with CLI
- watch (nodejs) – Watch files/dirs
- mockjax – Fake your ajax calls (good for protyping or testing un-related, yet dependent functionality)
- Travis CI – continuous integration service (wordpress plugin tests)
- Glue – generate css sprites
Microdata for SEO by Dave Ross
- Add itemprop, itemscope, etc to any identifiable schema
- Google Rich Snippets Tool – Test your microdata
- Examples: SiteNavigation element for navigation, Blog element for blog posts, etc
- Some quick tidbits: Bing rates sites with microdata higher than sites without, and Google uses the microdata in search results
Enterprise WordPress by Jake Goldman (1up)
- Sites to show clients: showcase, WordPress VIP
- Maintaining a beautiful WordPress admin
Shortcodes by Jon Bishop
- Use oembed rather than plugins to support embedding media from sites like youtube, facebook, etc
Codex by Erick Hitler
- Use santize_* functions to save to db:
- Use esc_* functions to show data to user (
esc_url_raw()is the exception, it is the opposite of
2 thoughts on “Things learned from Wordcamp 2012”
Can you send me an email at my address above? I have some questions for you.
Your email above (email@example.com) is not working.