WordPress/BluePrint theme: SF-BluePrint-WP


SlipFire’s BluePrint CSS Theme for WordPress, is not the first WP theme with BluePrint, but we think it’s the best. The simplicity of the theme is intentional, since it’s been designed to be a template for your own creation.

We first became aware of BluePrint CSS in late 2007 and immediately knew it would change the way we work. With it’s easy to use grid system, BluePrint CSS has dramatically cut down on our website design time.

First we started using the BluePrint CSS Theme designed by Fire and Knowledge. After a while we realized we hacked their theme pretty good and decided to upgrade it to BluePrint 0.7 and release our own version to the WordPress community.


BluePrint CSS: WordPress: Additional:
• An easily customizable grid • Easy to install • XHTML compliant
• Sensible typography • Easy to modify • Bobby Approved for accessibility
• Relative font-sizes everywhere • WordPress 2.3.2 compatible
• A typographic baseline • Widget ready
• Perfected CSS reset
• No bloat of any kind
• Cross-browser compatible
• W3C CSS Valid


  1. Download the latest version here: [download id=”1″]
  2. Unzip the files, and place the entire folder into your “wp-content/themes” director
  3. Select the theme in your admin panel
  4. That’s it!!

Make all changes to your CSS in “Custom.CSS”. Never touch the original BluePrint CSS files.

14 comments for “WordPress/BluePrint theme: SF-BluePrint-WP

  1. hani
    February 29, 2008 at 3:33 pm

    Thanks for such a great accessible theme. And thanks for making it free. I love it.

  2. Michael
    February 29, 2008 at 5:03 pm

    I’ve been looking for a BluePrint CSS theme to use with WordPress. This theme is so simple and elegant. Thank you!

  3. SlipFire
    March 1, 2008 at 11:59 am

    **** VERSION UPDATE TO 0.7B ****
    -Fixed minor typo in footer.php that rendered the theme not XHTML valid.
    -Fixed link decoration in custom.css

  4. Joe
    March 6, 2008 at 8:22 pm

    Hi there.

    You say:
    ” [we] immediately knew [Blueprint] would change the way we work.”
    Besides the decrease in design tim, any other reasons?

  5. SlipFire
    March 7, 2008 at 11:27 am

    Joe: Thank you for your question. Design time is a big part of what we do, so reducing it helps both us and our clients. BluePrint also looks great in all browsers, so we don’t have to spend time checking Firefox, IE, Opera, Safari, etc. And finally, BluePrint allows our websites to be accessible and Bobby Approved, which is important to us as well. Hope that answers your question!

  6. Bruce
    March 17, 2008 at 10:34 pm


    I came across this after playing a bit with one of the other BP themes. As I suggested over there, it’d be nice for you to remove the inline presentation classes and move all that to the CSS files, using compress.rb. Also, I’d include the typographic plug-in as well (also using compress.rb).

  7. May 1, 2008 at 4:01 pm

    Updated to version “c”. Seperated comments and trackbacks. For existing versions, just overwrite the new Comments.php file.

  8. August 14, 2009 at 4:07 pm

    Thanks for working on this, It truely is a step forward for the web design community. I am also working on some great blueprint integration with CMS like systems.

  9. June 30, 2011 at 5:49 pm


    I am getting the following problem:

    Warning: fopen(/home/rgproduc/public_html/wp-content/themes/SF-Blueprint-WP1/style.css) [function.fopen]: failed to open stream: No such file or directory in /home/rgproduc/public_html/wp-includes/functions.php on line 4284

    Warning: fread(): supplied argument is not a valid stream resource in /home/rgproduc/public_html/wp-includes/functions.php on line 4287

    Warning: fclose(): supplied argument is not a valid stream resource in /home/rgproduc/public_html/wp-includes/functions.php on line 4290

    Any thoughts on this please?

    • sbruner
      June 30, 2011 at 7:57 pm

      It looks like the permissions on style.css are too restrictive… but that’s only a guess. It should be 644.

Leave a Reply

Your email address will not be published. Required fields are marked *