The eleven40 theme is the second child theme released here at StudioPress which has been developed to be mobile responsive in design. It’s also the first theme we’ve developed that extends 1140px wide vs. our current themes which are 960px.
Click here to see how the eleven40 theme looks across mobile devices.
The eleven40 theme includes the following features: 6 layout options, 4 theme colors (blue, green, orange, red), custom background, featured images, footer widgets, mobile responsive design and threaded comments.
Genesis 1.8 ships with a hot new default style on the front end. And while we know that you would never activate Genesis directly, this new style can, and no doubt will serve as the basis of many of the beautiful creations our users continue to push out.
This modern new look takes a step into the realm of responsive design, adjusting to fit whatever device on which you happen to be viewing the site, including smart phones and tablet computers.
One of the biggest weaknesses of the Genesis SEO controls was the fact that you couldn’t actually control the text displayed on category, tag, and term archive pages. All you could do was decide whether or not you wanted the term title and description to display.
With Genesis 1.8, this all changes. You now have the ability to control EXACTLY what gets displayed on your term archive pages.

Considering how many Genesis-specific plugins there are out there, we imagine that more than a few developers are frustrated at how difficult it was to add new Genesis admin menus. In Genesis 1.8, it gets about 100x easier. How much easier? See for yourself.
If you’ve ever build a Genesis Child Theme for a client, and knew you’d have no use for the Primary or Secondary Navigation menu, you know how hard it can be to keep your client from messing with the Theme Settings and potentially ruining your beautiful design.
So, with one line of code, you can now disable either menu. It works using the “theme support” method. By default, both menus are enabled. But, you can use this line of code to change which menus are supported via your child theme.
remove_theme_support( 'genesis-menus' );
This line will remove both menus. But let’s say you just want to remove the secondary nav menu, and leave the primary menu intact. Easy.
add_theme_support( 'genesis-menus', array( 'primary' => 'Primary Navigation Menu' ) );
This line indicates that you ONLY want the primary nav menu to be enabled.
If you’re building a child theme and want to give users the ability to choose a color scheme from the Theme Settings page, this option is for you.
add_theme_support( 'genesis-style-selector', array( 'theme-blue' => 'Blue', 'theme-green' => 'Green', 'theme-orange' => 'Orange', 'theme-red' => 'Red' ) );
Just add this to your child theme’s functions.php file, and Genesis will handle the rest. A new box will appear in Theme Settings, and users can choose the color scheme for their site.

Genesis handles the body class, and all you have to do is build the CSS. Less coding. More designing. You know you love it! More here.
One of the core values of the Genesis coding style is that we want you to be able to find what you need without using a Genesis dictionary. Clarity is king. But how awesome would it be if each of the functions in Genesis had an explanation of what it did right above it? Done!
Thanks to Gary Jones, Genesis 1.8 is chock-full of inline documentation.

In addition, Genesis has been trying to move towards the WordPress coding standards for a few versions now. As of 1.8, I think we’re pretty much all the way there. Code now has room to breath, with plenty of whitespace for readability.
Since WordPress 3.3.1 was recently released, Genesis 1.8 does require this latest version of WordPress. It’s always good to stay up to date anyway, so go ahead and upgrade with confidence knowing that Genesis is fully compatible.
To see a more comprehensive list of changes in Genesis 1.8, check out this page.
Note: Users of WordPress 3.2.1 or older will not be prompted to upgrade to Genesis 1.8 via their dashboard. Please upgrade to WordPress 3.3.1 first, then our update servers will prompt you to update within 24 hours.
So what are you waiting for?! Go upgrade, already!
A very special thanks goes out to the developers that helped make Genesis 1.8 happen. Jared Atchison, Charles Clarkson, Chris Cochran, Nick Croft, David Decker, Remkus de Vries, Bill Erickson, Gary Jones, Travis Smith and Ade Walker.
]]>Sales for StudioPress themes stayed strong through the end of the year, letting us pay our top affiliate $6,235.65 in commissions last month, just for promoting Genesis and our themes.
(are you a StudioPress affiliate yet?)
To make our “most popular Genesis Framework child themes” posts more interesting, this month we’re going to start listing our Top 10 best selling themes instead of only our Top 5.
In December 2011, the top 10 selling StudioPress child themes were:
Separating the best from the rest is the Driskill theme by Bill Erickson, StudioPress’ first responsive design. Clean and contemporary, it’s no surprise this is used for both personal and professional sites of all kinds.
Sometimes less really is more. The popularity of StudioPress’ Minimum theme proves that solid content with great navigation can be all you need.
A strong seller since its introduction to the Genesis Child Theme Marketplace in September, Lindsey Riel’s Modern Blogger theme marries comfortable design with modern sensibilities.
When your company’s image is on the line, you need to be sure you’re putting your best foot forward. The Associate theme empowers you to do just that.
If this theme had another day or two to sell, it would have likely made the Top 5. Released last month to rave reviews, Generate is the theme to use if you’re serious about growing your email list.
When you have a ton of content and need a sleek way to organize it on your site, the Magazine theme is an excellent choice. With lots of customization options and easy navigation, your content is free to steal the spotlight.
The Lifestyle theme never ceases to amaze me. People are using this flexible theme for every kind of site imaginable, and considering the number of design options provided, Lifestyle isn’t going anywhere anytime soon.
The Enterprise theme offers a professional frame for corporate-style sites, giving you the approachability you desire and the trustworthy image you require.
Savvy publishers know that the key to content-heavy sites is simple, yet stunning, navigation. The News theme offers that and more for publishers of every type of media.
Boasting 5 color styles, smart homepage designs, IDX integration and simplified posting options for listings, AgentPress continues to lead the StudioPress theme charge. Check out the AgentPress showcase to see how smart real estate professionals are letting Genesis work for them.
Were these the themes you expected? Have a favorite you think should be in the Top 10 for January?
Sound off in the comments!
]]>As you can see, the default look for Genesis has been updated. We’ve also added 2 media queries to the style sheet, which makes it mobile responsive for devices such as the iPad and iPhone.
Click to view the updated Genesis demo.
We’ve also consolidated some of the CSS required for menus, which you can read about here.
Check out the Genesis 1.8 changelog and you’ll see that a number of things were fixed, added and modified. One of the biggest features that we’ve added is the Color Styles function.
Many of our child themes have color styles, which are currently being made available by code that’s included in the child theme’s function file as well as an additional file found within a ‘lib’ folder.
The new code that is required in the child themes would look like this:
/** Create additional color style options */ add_theme_support( 'genesis-style-selector', array( 'agentpress-gray' => 'Gray', 'agentpress-green' => 'Green', 'agentpress-red' => 'Red', 'agentpress-tan' => 'Tan' ) );
As with all functions that end up being placed into a number of child themes (custom header, footer widgets, etc) we’ve extracted that code out of them and placed it in to Genesis core.
One of the very cool features that we’ve included in Genesis 1.8 is the ability to automatically update to Beta versions of Genesis. This is similar to the WordPress Beta Tester plugin that exists – the only difference is that users won’t have access to the bleeding version of Genesis.
Because the Genesis Beta Tester plugin relies on code that’s in Genesis 1.8, users will have to force the auto update script by replacing code. (This will only be required this time around.)
Inside the lib/functions/upgrade.php file, on line 29 you’ll see this:
'genesis_version' => PARENT_THEME_VERSION,
Replace that with this:
'genesis_version' => '0.1.3.3.7',
Once you have that uploaded the file to your server, click on the Appearance link in your WordPress dashboard, then head to the Dashboard main page and you should see a notification to update to Genesis 1.8 Beta.
Moving forward, once users have Genesis 1.8 any beta versions that are released will prompt an auto update notice for those who have the Genesis Beta Tester plugin active.
If you are testing Genesis 1.8 Beta and would like to report a bug, please reply to this thread on our forums. Please do not use that for feature requests, as we are done adding those into Genesis 1.8.
We’d like to thank the following developers for their contributions with the update to Genesis v1.8: Jared Atchison, Charles Clarkson, Chris Cochran, Nick Croft, David Decker, Remkus de Vries, Bill Erickson, Gary Jones, Travis Smith and Ade Walker.
]]>Pure Elegance was developed by Auxano Creative, and can be found on the StudioPress Marketplace. As a reminder, these themes are not included in the Pro Plus All-Themes package, but we assure you that the design and coding of the themes are top-notch.
The Pure Elegance child theme includes the following features: 3 color styles, 6 layout options, custom background, custom header, featured images, fixed width, theme options, threaded comments.

Whether you’re just starting out with the Genesis Framework for WordPress, or you’ve been enjoying its power and flexibility for a while, this download should prove very helpful.
The guide is packed with 44 pages of useful and specific instructions on getting started with Genesis, including:
This is also a living document, so be sure to check back often for updates and improvements as Genesis itself evolves with the future web.
Click here to download The Genesis Guide for Absolute Beginners (PDF) 1.4 MB
]]>The Generate theme is the first child theme released here at StudioPress which has been developed to be mobile responsive in design.
The Generate theme includes the following features: 6 layout options, 4 theme colors (blue, green, orange, red), custom background, featured images, footer widgets, mobile responsive and threaded comments.


Sometimes the director brings a moment to the screen that just isn’t possible in real life. One of these moments happened for me when I first watched The Matrix and encountered “bullet time.” I didn’t get to see it in the theater but I remember rewinding that initial rooftop scene at least ten times while watching at a friend’s apartment. Another awe-inspiring experience was flying with the camera as it panned over and revealed the massive structure of Minas Tirith in Lord of the Rings: Return of the King.
These effects create profound experiences that enhance the movie and take the storytelling to another level entirely.
Would The Matrix have been a good movie without “bullet time”? Sure, it possessed both a good story, and good cinematography. But it was the “bullet time” effect that sent it over the top, that made you remember.
Would Lord of the Rings have been a good movie without its visual effects? Yes, because the story is so incredible. But with the amazing effects, the story was taken to a whole new level that gave us a truly magical experience.
The same can be said for CSS3.
Is it absolutely necessary to use CSS3 on our sites today? No. You still need a good foundation of content, usability and markup. But using it to enhance these things can take a site over the top and give the user a wonderful experience.
Some have said that using CSS3 is akin to cheap parlor tricks and that by using them we’re trying to pull the wool over the eyes of our users. This may be true in some cases where the content is weak, but our job is much like a movie effects designer in that we want our users to have the best experience possible. Consider what John Gaeta, the head of effects for The Matrix said about this:
My job has nothing to do with making zingers. The point is not to knock you over with a visual trick. The point is to be able to construct events that are so complex, in terms of what human bodies need to do, that the total ‘effect’ is impossible choreography. ‘My God! It looks real, but it just can’t be.’
As web designers we want to enhance our content to the point where it gives the user pleasure to be on our site. Much like advances in technology have allowed amazing effects to be brought to the silver screen, CSS3 allows us to bring really cool enhancements for our users to experience.
CSS3 is the third iteration of the CSS specification recommended by the W3C.
So, way back in the day, around 1996, a group of people called the World Wide Web Consortium put together a document called a specification or spec that officially recommended ways for browsers to handle CSS. It included suggested standards for things like font properties, text color, alignments and so on. This was CSS1.
Always wanting to push the boundaries as to what browsers could possibly display, the CSS2 specification was officially recommended in 1998 and included things such as positioning and layering attributes. There were a number of errors in this spec which were corrected. And the spec was enhanced in what was called CSS2.1 which was officially recommended in June 2011.
The Consortium decided to split up the next iteration of the spec — CSS3 — into modules. Theoretically this spec would allow browsers to adopt and support new selectors getting them into the hands of designers more quickly. And that’s where we are at right now.
Since the spec has been split into modules — and with the introduction of CSS3 — browser support for new selectors has been good across the board with the exception of Internet Explorer.
Generally IE6, 7 or 8 do not support CSS3. The good news is that the current version, IE9, implements a majority of the working draft and IE10 supports even more.
My answer is yes—regardless of browser support.
In Dan Cederholm’s book CSS3 for Web Designers he talked about the reality of implementing CSS3:
…the truth is everyone can begin using CSS3 right now. And fortunately you don’t have to think differently or make drastic changes to the way you craft websites in order to do so. How can anyone use CSS3 on any project? Because we’re going to carefully choose the situations where we apply CSS3, focusing squarely on the experience layer.
As I stated above, we don’t absolutely need these things, because we still have our content and markup. CSS3 serves to enhance the experience.
The latest browser statistics have the market share of IE anywhere from 30%-50% depending on which study you look at. So is it realistic to not give half of my users an experience? I’ll defer again to Cederholm as he says we need to group the elements of our sites into critical and non-critical categories.
| Critical | Non-Critical |
|---|---|
| Branding | Interaction |
| Usability | Visual Rewards |
| Accessibility | Feedback |
| Layout | Movement |
For those items that are critical we would not use elements that are not compatible with all of our target browsers.
For example, if part of the branding and distinct look of your site is to have all of your containers with rounded corners you’re probably going to have to use images, or a different solution than the CSS3 border-radius selector. But, if having rounded borders is just an enhancement — not critical to the site’s look — you can freely use it now.
There are a couple decent solutions to using CSS3 with all versions of IE now.
In the past, when presented with the problem of designing for multiple browsers, the typical solution was to make sure our sites “degraded gracefully.”
We would design sites for the latest browsers, but would make sure they would look ok in the older ones. I always pictured the user wincing and shying away from their computer as the page loaded, not sure if their computer would explode …
Progressive Enhancement takes the exact opposite approach.
We design initially for the lowest common denominator and then progressively build in enhancements. This is one reason this idea works so well with mobile sites and responsive design.
Using progressive enhancement as a design philosophy caters more to users that can’t upgrade because of IT policies. It also saves the designer loads of time and headaches because they aren’t forced to come up with crazy hacks and solutions to make everything look the same.
Say I want to use drop shadows on images in my blog posts. I have basically three options:
All three will work, but:
- I’m spending loads of time creating these shadows for every image and increasing my file size
- I have to have crazy markup and rules to fit every image size or be restricted to one size. I also lose the ability to use the background selector for other purposes.
When I use the css3 box-shadow element I save myself developing time. I can preview changes quickly in the browser without having to create multiple images. I have the option to use my background for something other than a shadow and I save file size and processing time.
Just because some people are color blind doesn’t mean we design a site without color.
Multiple Backgrounds
This property allows you to specify multiple backgrounds in a container with nothing more than a comma separated list in your css. The image listed first will appear on top of all others. In this example I’ve actually used only two images but have re-used the airmail strip to have it appear on the bottom of my container.
.envelope {
background-color: #e3dfba;
background:
url(images/airmail.png) top repeat-x,
url(images/airmail.png) bottom repeat-x,
url(images/grunge.jpg) no-repeat;
height: 400px;
width: 600px;
}
Border Radius
The border-radius property allows you to round the borders of your element. To learn more visit The Art of the Web.
.envelope {
-moz-border-radius: 10px;
-webkit-border-radius: 10px;
border-radius: 10px;
}
.env-inner {
background-color: #1699e5;
background: url(images/blue-grunge.jpg);
-moz-border-radius: 20px;
-webkit-border-radius: 20px;
border-radius: 20px;
height: 319px;
float: left;
margin: 42px 20px;
width: 560px;
}
Box Shadow
In the example below we’ve added a shadow to our container. There are four parts to box shadow:
.shadow {
-moz-box-shadow: 0 0 5px #666;
-webkit-box-shadow: 0 0 5px #666;
box-shadow: 0 0 5px #666;
}
CSS Transforms
The transform property is used to rotate, skew and scale elements. It can be applied to images, containers, and text elements.
In our example below we’ve rotated our containing element basically 1 degree backwards. It would have also worked to use -1deg for our value.
We’ve also used a scale transform on the sun graphic. Most often this property is used in conjunction with a hover action. Make sure you hover over the sun to see it in action. The last example in the article shows how this can be done smoothly with a transition property added.
For more information on using the transform property click over to zenelements.
.rotate {
-moz-transform: rotate(359deg);
-webkit-transform: rotate(359deg);
transform: rotate(359deg);
}
.sun {
-moz-transform: scale(1);
-webkit-transform: scale(1);
transform: scale(1);
}
.sun:hover {
-moz-transform: scale(2);
-webkit-transform: scale(2);
cursor: pointer;
transform: scale(2);
}
Child Pseudo-Selectors
ul.envelope-list li {
background-color: #e3dfba;
background:
url(images/airmail.png) top repeat-x,
url(images/airmail.png) bottom repeat-x,
url(images/grunge.jpg) no-repeat;
float: left;
height: 98px;
list-style-type: none;
margin: 10px 10px 10px 0;
width: 98px;
}
ul.envelope-list li:last-child {
margin: 10px 0 10px 0;
}
In this example we are changing the margin for the last list item. Last child refers to the last child of the parent item. So in this case the css will be applied to last li of the ul with the class of evelope-list.
ul.envelope-list-2 li:nth-child(2) {
background:
url(images/airmail.png) top repeat-x,
url(images/grunge.jpg) no-repeat;
}
In this example we are changing the background for the second item in the list. So nth-child lets us specify a specific numbered item of the parent element to change.
ul.envelope-list-3 li:nth-child(3n) {
background:
url(images/airmail.png) bottom repeat-x,
url(images/grunge.jpg) no-repeat;
}
In this last example we are applying a formula where the css is being applied to every 3rd item in the list. So every 3rd list item in the ul will have a different background.
In this last example we’ll combine several of the examples we’ve already done plus add in some transitions to smooth everything out.
<div class="envelope radius">
<div class="env-inner shadow airplane">
<div class="text">
<div class="wave">Wave Next Time</div>
<div class="iowa">Iowa</div>
<div class="fly">You Fly Over</div>
</div>
<div class="sun-animate"><img src="sun.png"></div>
</div>
</div>
.airplane {
-moz-transition: all 0.7s ease-in-out;
-webkit-transition: all 0.7s ease-in-out;
background:
url(images/airplane.png) no-repeat 600px -34px,
url(images/blue-grunge.jpg);
transition: all 0.7s ease-in-out;
}
.airplane:hover {
background:
url(images/airplane.png) no-repeat 0 -34px,
url(images/blue-grunge.jpg);
}
.sun-animate {
-moz-transform: scale(1);
-webkit-transform: scale(1);
-moz-transition: all 0.7s ease-in-out;
-webkit-transition: all 0.7s ease-in-out;
float:left;
margin-top:-270px;
opacity: 1;
transform: scale(1);
transition: all 0.7s ease-in-out;
}
.sun-animate:hover {
-moz-transform: scale(10);
-webkit-transform: scale(10);
cursor: pointer;
opacity: 0;
transform: scale(10);
}
.text {
color:#efefef;
float:left;
font-family: Oswald;
margin-top:60px;
text-align:center;
text-transform:uppercase;
width:100%;
}
.iowa {
font-size: 130px;
height: 116px;
line-height: 107px;
}
.wave {
font-size: 40px;
height:36px;
line-height:35px;
margin:5px 0;
}
.fly {
font-size: 45px;
height:40px;
line-height:37px;
}

Find out what CSS3 properties and selectors can be used by today’s browsers:
http://www.findmebyip.com/litmus/
http://caniuse.com
All Around CSS Information and Goodness:
http://css-tricks.com
http://www.w3schools.com/css/default.asp
http://www.zenelements.com/blog/
http://trentwalton.com/category/articles/
Experimental Uses of CSS3
http://tympanus.net/codrops/
As many of you know, WordPress 3.3 was officially released. We wanted to let you know that we’ve updated the StudioPress site and all of the Genesis child theme demo sites — and all is well.
This is our way of saying “Go for it, you should safely be able to update to WordPress 3.3!”
Experienced users will appreciate the new drag-and-drop uploader, hover menus for the navigation, the new toolbar, improved co-editing support, and the new Tumblr importer. They’ve also been thinking a ton about what the WordPress experience is like for new users.
Version 3.3 has significant improvements there with pointer tips for new features, a friendly welcome message for first-time users, and revamped help tabs throughout the interface. They’ve improved the dashboard experience on the iPad and other tablets with better touch support.
There is a ton of candy for developers as well. I’d recommend starting your exploration with the new editor API, new jQuery version, better ways to hook into the help screens, more performant post-slug-only permalinks, and of course the entire list of improvements on the Codex and in Trac.
The development team here at StudioPress is always working with the bleeding version of WordPress. As a result, we can confidently say that there aren’t any known issues with WordPress 3.3 and Genesis 1.7.1.
We cannot promise that all of your plugins are compatible, so make sure you check those for compatibility before updating.
Now that WordPress 3.3 has been released, we’ll be working hard over the next week or two to prepare Genesis 1.8 for release. Until then, Happy Updating!
]]>