We’ve decided to pledge our support to Open to All, a national nonprofit campaign based around the idea that everyone should be welcome regardless of race, ethnicity, national origin, sex, sexual orientation, gender identity and expression, immigration status, religion, or disability.
Being a good — or even great — developer is more than just shipping clean code (though this is certainly a necessary skill). It’s also about creating a content management experience for your client that isn’t a nightmare to manage, or as I’d like to call it: “client-first development.”
Whether your client is a mom and pop corner store or the New York Post, it’s your job as a developer to make their content management experience as painless as possible. Developers need not only to build themes, but also to build solid solutions for clients — client-first development is a front end WordPress developer’s real job.
Imagine a client who only logs into their site once every other month to update content. It’s very easy for them to forget things like image sizes, what content is displayed where, or even how to enter content in the first place. WordPress offers a lot of built-in functionality — most notably custom post types (CPTs) — that can aid us in this sometimes daunting task.
At WordCamp Minneapolis, I’ll be speaking on the need for client-first development, and how to implement this approach using WordPress. With the right attitude we can help clients have a more intuitive (rather than a confusing) experience when updating content.
WordCamp Minneapolis 2014
University of St. Thomas
Thornton Auditorium, 1 PM ET