I’ve been mulling over and debating whether to write this post for about a week. It’s a response to this post on ThemeShaper. In the post, Fränk Klein, in no uncertain terms, explains why using Bootstrap with WordPress is a bad idea. Being the author of a WordPress theme that is based on Bootstrap, as well as… Continue reading Bootstrap is NOT a bad fit for WordPress
So I ran across an issue today when creating a custom admin menu and submenu items. I wanted to have a submenu item in the menu that linked to the main admin menu page, but did not have the same anchor as the parent. I kept running into this: You can see that, since I’m currently… Continue reading Code: Getting rid of the duplicate submenu with add_menu_page and add_submenu_page
Newest Pluralsight promo video is out and it’s the first one I’m in (1:39). Authors were encouraged to come up with their own lines. Full disclosure: I suck at RegEx (regular expressions).
Some good reminders in here for devs and people in general. Things every dev needs to be thinking about (myself included).
This quote from today’s Clients From Hell newsletter is a lot like what I posted about last week: Clients will often claim that they can get a man in Malaysia at one-tenth your price point, or that there’s a fresh-faced kid who’s hungry for your work. They’re not wrong, but they are short-sighted. That kid… Continue reading Raising Rates
No matter what else you may pay for when you hire a developer, you will always be paying for these two things:
1) Their time. Every developer I know is busy, including myself. That means, in order for something to be good enough for them to stop whatever else it is that they are working on, you need to be willing to make it worth their time. This may be that the project is particularly interesting to them or it may be monetarily. Either way, you will be bidding on their time against any number of other projects that are already attracting their attention.
2) Experience. By hiring a developer, you are making a leap of faith that they know what they are doing. Generally speaking, experience coincides with cost — you won’t find many (if any) experienced developers working for cheap. The market tends to work these things out naturally — an inexperienced developer, overpricing their work, will end up breaking something or getting in over his/her head and will end up getting negative feedback of one form or another and lose clients.
The more you are willing to value these two things in a potential developer, the better the developer you’ll end up with. Anyone can write code, but not everyone comes with the experience and expertise to write good code. If you are unwilling to apply value to your potential developer’s time and experience, you are unlikely to end up with a very good developer.
I did a writeup on Museum Themes on how to use Bootstrap 3 themes with Museum Core (which this site uses) to get new “skins” for the Core theme. Note: I wouldn’t have even thought of this if it wasn’t for Shawn Wildermuth‘s Bootstrap 3 course on Pluralsight. If you want to check it out, I still have some trial codes to give away over here.
I’ll tell you a secret: up until a few months ago, user roles and permissions in WordPress were a vast, unexplored land of confusing terms (capabilities and — gasp — meta capabilities) and complex relationships. I didn’t know much, but I did know that if you were playing with new user roles or capabilities and messed up… Continue reading New Pluralsight Course: User Roles & Capabilities in WordPress
New favorite WordPress function:
register_taxonomy_for_object_type(). Associate an existing taxonomy with an existing post type.
So Museum Core was pushed live to the WordPress.org repo today. Of course I immediately switched my blog from the Twenty Fourteen theme I was testing to Core because, you know, it’s my freaking theme. And immediately I ran into some issues. If you are using Core and experience any of these, here are the fixes.… Continue reading Theme update and a mad dash to fix broken stuff