Recently, I’ve been asked when I’m planning to bring Mayer to self-hosted WordPress installations.
The short answer is that I don’t have a definitive answer, but I am working on the Pressware shop. The longer answer has more to do with my current backlog of work and the things that I’m trying to accomplish before doing so – that is, it has a lot to do with what’s happening within the Pressware pipeline.
To that end, I thought it might be worth sharing the current plans I have for Mayer, the eCommerce gateway I’m working to setup for Pressware as well as my current theme backlog.
I’m proud to announce that, as of today, Mayer is officially for sale on WordPress.com.
This particular release has been a long time coming, so much so that I’ve discussed it a number of times on the blog already:
Of course, after several rounds of beta, code reviews, feature changes, and so on, things are bound to change over the course of development.
But today, Mayer is officially at `1.0` and is ready for purchase.
dog fooding can sometimes give you the monday feels (as one of my dog demonstrates)
As I’ve mentioned in previous posts, I firmly believe that developers should be dog fooding their own work.
This isn’t to say that I don’t believe that assembling a team of beta testers is unimportant – on the contrary – but if you’re building something, and the only people who have experience using said product are people other than you, then I think that’s a problem.
So as of today, I’m proud (if not a little bit embarrassed) to be officially test-driving Mayer – my next WordPress theme that I’ve been discussing for sometime.
When it comes to WordPress theme development, one or the areas that developers often find themselves wrestling with is just how verbose they should make their code.
For example, we’re often taught and strive from principles such as DRY and KISS, but it’s hard to maintain both of these when building WordPress themes from the ground up.
For example (and as according to the Codex):
At the very minimum, a WordPress Theme consists of two files:
And for anyone who has done extensive work in WordPress development knows this to be true; however, if you’re getting into theme development – that is, specifically for bloggers, or digital publishers – then you know there’s a wide variety of templates that are also supposed by the WordPress Template Hierarchy.
To name a few:
- …and so many more
But here’s the deal: it’s nearly impossible to embrace DRY while simultaneously trying to implement each of these templates.
Instead, we’re left with having to repeat a variety of code all the while doing so when much of the code could be produced though template parts and conditional logic.
Though I’m sure we all fall somewhere in between on this issue, he’s where I’ve landed with respect to the various themes that I’ve developed over the last couples of years.
As of today, I’m excited to announce that I am officially looking for a handful of beta testers for Mayer.
In previous blog posts, I’ve shared a bit about the theme:
- Mayer is for bloggers who write frequently and/or write long form content, or want to do either of the above.
- It offers no options – everything is managed via the Theme Customizer.
- This is the theme I will be using in place of Standard
- Fully supports WordPress 3.8
- …and more
But, as they say, I’m too close to the product, and so I need to get it into the hands of others who are willing to install it, toy around with it, try to break it, and report bugs, and other mistakes, and who are willing to do so for a number of rounds of testing.
If this sounds like something you’re interested in doing, then please read on as I’ve got all the details below.