Inspiration from the awesome support you get as part of the WordPress ecosystem is either an awesome motivator or a way to fall into the trap of jealousy. It’s your choice. Personally, I’ll admit at times I catch myself choosing wrong.
Earlier this week my company CalderaWP announced a new partner that was made possible by the GPL, but goes beyond what the GPL requires. The GPL fosters community. It does not make community. Our community is based on how we use those freedoms and nurture our relationships.
The WordPress REST API is more then the default routes, its a highly extensible tool for creating APIs. Learn how to extend it and make it fit your own needs.
The WordPress REST API’s inclusion in core “sometime in 2015,” something everyone is excited about, has until this week and everyone couldn’t wait. Now that’s not so certain. But it’s a feature we need in WordPress, and it’s ready. To waste this opportunity now would be a huge mistake.
Working with access control headers and other global headers for the WordPress REST API.
Some thoughts on how I strive to write compelling stories about how my readers are going to learn new things about using WordPress to meet their goals.
I’m proud to be a part of this community, even when things are not so shiny. Despite all the #wpdrama as of late, let’s not forget how awesome ya’ll are.
WordPress is a free software, and those freedoms are partially about providing the ability to learn from the software. Reading the source will provide you with an understanding of your software, and a learning experience that no documentation can provide.
It’s 2015 and I have every right to demand real-time visual feedback for any changes to the presentation layer of a web app, before I save them, and without reloading the page. For more and more of the WordPress admin the Customizer delivers.