Page 291 of 428

WordPress Settings API Wrapper? No Thanks.

January 8, 2014 / Tom / 0 Comments

From time to time, I end up having conversations with other developers about the state of the WordPress Settings API, whether or not there should be wrappers for it, and/or how the current API can be improved.

Each time the conversation begins, it generally stems from the fact that the Settings API is confusing, can be very intimidating to work with the first time, and it’s not as intuitive as some of the other WordPress APIs.

As with anyone who’s worked with WordPress long enough, I have my own opinions about this – and this is certainly not a “patches welcome” post – because this has been already been discussed at great length on Trac.

Instead, this is nothing more than my general stance on the WordPress Settings API, and how I see wrappers fitting into the scope of overall WordPress Development.

How To Add Google Fonts To The WordPress Editor

January 7, 2014 / Tom / 0 Comments

When it comes to building themes in WordPress, one of the nicest things that you can do for your users is to implement a stylesheet specifically for the editor so that they get a true WYSIWYG experience.

To be more specific, that is you can (and should!) add a stylesheet specifically for the WYSIWYG editor in the WordPress Dashboard. This stylesheet is normally called `editor-style.css`, but can actually be called whatever it is that you’d like permitting that you enqueue it properly.

With the popularity of web fonts rising – such as those from Google – you have to take a slightly different approach when implementing them in the context of the editor rather than the typical way of doing so with server side hooks.

I’m Officially Looking For Beta Testers For ‘Mayer’

January 6, 2014 / Tom

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.

Starting 2014

January 3, 2014 / Tom / 0 Comments

For many of us who write regularly, it’s hard to fight the urge not to write about what we did last year, what we plan to do this year, and how we’re going to accomplish it.

Though I don’t typically write those types of posts, I absolutely dig reading them for others primarily because:

I think that I follow a lot of really interesting people who are doing a lot of really interesting things,
It’s inspirational to see what others have achieved,
It’s fun to see what’s coming in the next year from said people and watch them make it (or even scrap it!)

And sure, I have my own goals and things that I plan, but I’ve been at this long enough to know that I do best when I forecast for the short term – that is, for the next quarter or so – and then make detailed lists for the given month on what I’d like to accomplish.

Sometimes, items carry over from the previous month; most of the time, the list of full of new things to check off.

In an attempt to cover what I’m planning to achieve in the first part of 2014 (read: January), I thought I’d go ahead and share a couple of notes specifically related to WordPress work – both from a personal stand point and from Pressware’s standpoint.

What I’ve Learned About Open Source Project Management: Releases

January 1, 2014 / Tom / 0 Comments

This is the fifth and final part in a series on What I've Learned About Open Source Project Management.

Though some may argue, I think that all projects – open source or not – ultimately culminate in releases. That is to say that when it comes to building software, your ultimate goal is to provide a solution for your users that gracefully solves their problem.

I think all developers strive for kaizen in their work, but because of our own nature, we end up shipping things that sometimes feel like a step back, sometimes introduce more bugs, or sometimes simply dissatisfy the user.

Of course, that’s only one side of the story, right?

On the other hand, companies and developers do often ship incremental improvements of their software much to the delight of their users. And though that’s not always the case, it’s something for which we all should aim.

Everything that’s been covered in this series leads up and contributes to releases.

How this works in closed source software may or may not be the same as it works within the confines of open source project management – I’d venture to say that there’s overlap – but nonetheless, here are my takeaways with respect to aiming for releases in open source project.

Tom McFarlin

WordPress Settings API Wrapper? No Thanks.

How To Add Google Fonts To The WordPress Editor

I’m Officially Looking For Beta Testers For ‘Mayer’

Starting 2014

What I’ve Learned About Open Source Project Management: Releases