Blog

A little freebie: WordPress folder icon

WordPress folder icon previewAt 10up, are freebies usually come in the form of WordPress code: tips, themes, and plug-ins. While a bit atypical, I wanted to share this folder icon we designed from scratch. It incorporates the WordPress logo, which is available here in vector format.

Designed with the gray WordPress color palette in  mind, this icon can add some flair to your WordPress folder(s) on your computer. There’s a full sized, beautiful 256px version, along with a small version fine tuned for the common 16px icon size.

We’re providing them for free with a GPL license, in original vector (Adobe Illustrator CS5 and SVG) formats as well as 256px PNG format and Windows ICO format. As always, we do politely request that if you use these for a client or commercial project, please give us attribution. Donations are welcome!

Download now.

Secondary HTML Content 3.0 preview

As much as we like giving back to the community, it’s often hard to find time to keep some of the more sophisticated plug-ins up to date. One plug-in that hasn’t been updated in some time that I am frequently asked about is Secondary HTML Content.

I’ve had a number of ambitious goals for 3.0 for some time:

  • Enable a more complete editor experience (notably, Visual / HTML tabs)
  • Allow users to customize the labels for each content block
  • Add support for custom post types (not just posts and pages)
  • Remove arbitrary limit of 5 editor blocks
  • Integrate the settings with the “Writing” settings page (a logical place for them; I’m make a conscious effort with my themes and plug-ins to not “clutter” the settings panel)
  • On top of all this, provide a seamless upgrade path for 2.0 users

The first bullet has been by far the most challenging. While WordPress has a number of core functions that simplify adding a visual editor, they simply weren’t built with multiple editors on one page in mind. For the technically savvy, there are many hardcoded ID attributes, interacting with both CSS and JavaScript that rely on those IDs. As we know, the DOM is not intended to have multiple elements with identical IDs (particularly when we’re hooking events with JavaScript).

Nonetheless, I’m excited to say that the biggest hurdles have been tackled. Since we can’t work on hobby projects full time, the release is probably at least a couple of weeks out, mostly having to do with the upgrade path code.