- Contribute to projects like Calypso. With WordPress.com moving to Calypso, and the potential for self-hosted WordPress.org sites to use it, being able to understand it on a deeper level (along with the API) can help me be able to dig out bugs, submit fixes, and work towards enhancements.
- WordPress Plugins. I’ve got a couple of very niche plugins out on the main WordPress.org plugin directory. While they’re very basic, they work well for what I needed at the time, and it seems a few other folks needed them too! I would really like to work on enhancing one of them with some settings, since it enables Jetpack functionality for a theme framework that otherwise would require the user to modify their theme.
However, a number of sites are also blocking /wp-includes/. While it doesn’t seem obvious, there are a number of things that live here which would need to be accessed by users (i.e., crawlers) to render pages properly. For example, Dashicons, the small icons you generally associate with the admin side of WordPress, can often be called by themes for front-end usage. Another major thing that can hinder proper rendering by crawlers is jQuery. Sometimes, themes will enqueue a different version, but by default, it lives in the /wp-includes/ folder. If we dive even further into the issue, we’d see that the built-in emojis and comment reply handling would also be affected.
So, what can be safely blocked? At this point, here’s what a “compliant” WordPress robots.txt would look like (as far as what is safe to block). Of course, you’d want to add in your own sitemap directives and other special cases, but this is a good starting point.
Questions or comments? Leave them below!
As of 9AM this morning, I officially joined the
ranks of the unemployed freelance community.
I’ve been keeping a radio silence this weekend to mull over and discuss the situation with a few trusted friends/advisors, and making sure I have everything in order. While TopSpot Internet Marketing has been nothing short of an excellent place to work and learn, my first love has always been my freelance gigs.
To the TopSpot friends I’ve made in my time there: Keep #winning. I’ve learned a lot from everyone there (and hey, maybe I taught someone a thing here and there). I couldn’t have asked for a better company to spend my time with. If you ever need anything, you know how to reach me.
There are two areas that I am specifically passionate about: WordPress and Search Engine Optimization. I like to think that I’m extremely talented in both areas. So, that is how I’ll be (and am) making my income, through providing WordPress-specific consulting and programming, and search engine optimization services.
I’ve got a great network of people that have inspired, helped, and pushed me to go for this goal, whether it’s been through an active interaction, or simply letting me observe them in their natural habitat. I won’t name names here, but thanks for letting me be a part of what you’re doing.
While there is absolutely nothing wrong with working for someone else, for the things that I want to do, a “normal job” certainly isn’t in line with those things. Other than working, I’ve set goals to do a few things: travel to a foreign country (I’ve never been outside of the US), be on a panel or a presenter at SXSW, help build the best WordPress Meetup Group ever, and get in better shape than I’ve probably ever been in. There are plenty of other goals, but these are certainly near the top of the list.
Questions? Feel free to ask me in the comments below.