WordPress, WordPress, and Duplicate Skills on LinkedIn

Capital P Dangit

I’ve had a ton of people endorsing me for stuff on my LinkedIn profile. Skills is potentially a killer feature, where people I’ve worked with professionally are the ones who are confirming the strengths I’m attempting to market.

However, one thing that is killing me is WordPress — or should I say “WordPress” (with a “lower-case p dangit“).

My issue is that friends/colleagues have been endorsing me more in “WordPress” than “WordPress”. Unfortunately, for someone who markets himself on LinkedIn as a WordPress expert, this makes me look like an idiot to true WordPressers. Here’s a screenshot of my LinkedIn profile:

LinkedIn Duplicate Skills Example

I looked to LinkedIn’s support documentation for relief — and had my mellow harshed:

Question: I have duplicate skills on my profile. Can I merge them?

Answer: Unfortunately, skills cannot be merged. If you have duplicate skills on your profile, we suggest one of the two following options:

  • Delete the skill with the least amount of endorsements. Unfortunately, the endorsements will be deleted as well. They cannot be transferred over to the remaining skill at this time.
  • Keep both skills on your profile if you do not want to lose any endorsements.

So the answer is continue using the mis-spelled skill and dishonor the proper way to spell WordPress. Or, delete it and look like I don’t know shit about WordPress. LinkedIn needs to provide some method for correcting grammatical issues such as this.

No Letter PCompounding this pain-in-the-arse is WordPress core’s interference with recording this argument — specifically, its function that auto-capitalizes the middle “P”. Just to properly present my rant, I had to install a plugin or consider customizing my theme.

Photo credits: myself inspired by Capital P in WordPress; Leo Renyolds on Flickr

How I Added Instagram to My WordPress Self-Hosted Site

I’m a big-time user of Instagram, the photo sharing service with the great iOS application. Recently, I setup this blog to display my most-recent pics. Below is a short recap of how I did it — and I mean short, as it was very easy.

Initial Setup

It started with a decision on how to present my Instagram content. My original goal was pulling each photo into its own individual WordPress post, which from there I could use as emergency content during weeks I wasn’t able to write more frequently.  However, I didn’t find any solution which behaved like this (I’m sensing a business opportunity here).

The best compromise I found was the Instapress plugin for WordPress. It seemed to be the most flexible compared to the other options currently available.  It comes delivered with a shortcode that can display my feed (or anyone else’s) with different options for picture count, size, and more.

The Actual Execution

The only issue I’ve had with Instapress is how it outputs its HTML. I would have preferred for it to publish HTML similar in look and feel to a WP Gallery.

WP Galleries are a nest of <dt> and <dl> tags, mixed in with a wealth of gallery-specific CSS classes. Instead, Instapress posts each photo wrapped in a <div> and entirely-different classes.

My site is currently employing the Wumblr theme from Themify. It’s control panel allows me to insert custom CSS without modifying the theme itself.  So I just cribbed Wumblr’s WP Gallery styles and applied them in duplicate to the Instapress classes. It does the trick well enough.

OpenCamp Dallas 2010 Post-Game

It’s the Tuesday after the Tuesday after one of the most-amazing things I’ll ever accomplish: co-organizing the OpenCamp Dallas 2010 conference.

I still can’t believe we pulled it off: a core team of 11 individuals from all walks of media banded together to program a four-day event that attracted 600 participants. We did things that hadn’t been done before, and the foundation has been laid for a sustainable event that can only grow to be more impressive in future years.

Continue reading “OpenCamp Dallas 2010 Post-Game”