Three Reasons I Switched To The Genesis Framework

Three Reasons I Switched To The Genesis Framework

I have been working with WordPress as a hobby for the past two years. Having wanted to start a career with WordPress for the past few months, I knew a theme framework would help me reduce the repetitive process associated with theme building.  After looking around for a few weeks, I decided on the Genesis Framework.

By Word of Mouth

On a daily basis I see developers showcase their work with Genesis on Twitter. It was not hard to find developers (and users) showing their support for Genesis. In fact, I found a lot of posts describing why Genesis was their choice.

From Online Presence

Genesis developers are active within the WordPress community. The same developers I see on Twitter showcasing their work are also sharing their knowledge. I have always felt this promotes overall growth. This was the biggest influence for choosing Genesis.

Price and Support

I love the price. $59.95 for the Genesis Framework which includes unlimited updates and support. No developer, pro, pro-plus, single user, yearly type licenses. Just one price to use the framework on as many sites as I want.

After the switch

Working with the Genesis Framework took some adjusting. I had previously worked with underscores and Twenty Twelve for themes, so Genesis felt different. Not bad, just different. I was used to a ton of theme files for structure. Genesis utilizes actions and filters for looping and structure, which I found easy to work with. Happy I made the switch.

Published by

rfmeier

Product developer at Rainmaker Digital and runner from Hampshire, Illinois. I work with php a lot; Spending most of my time digging into source code to see how it all works. You can find me on Twitter @rfmeier.

6 thoughts on “Three Reasons I Switched To The Genesis Framework”

  1. I even started knowing/learning WordPress along with Genesis side by side and after these 2 years I can say that I am more than happy that I did it that way. 🙂

  2. For couple of months I’ve been reading about Genesis and thinking about using it however I really like using Foundation to build the layout and adjust it for mobile just the way I want.
    Reading about Genesis I found that I couldn’t combine the two of them and I find it dificult to work with Genesis.
    I know that you can achieve the same results but I find it way harder.

    Can you give me some insight into how I can migrate to Genesis based on my workflow with Foundation and _underscores?

    1. Best advice I can give is to learn Genesis from the source code. It will pay off in the long run. I have only used Foundation at work and have mixed feeling about it, so I haven’t even attempted to make it work with Genesis. With the attribute filters in Genesis, I am sure you could get it to work.

  3. I know that you need coding knowledge to create a child theme for genesis, but how much coding knowledge do you mean? Right now I create child themes for twenty eleven, and the only files I work with are style.css and occasionally some php files, though only very minor edits. Will I be able to code a child theme for genesis or do I need to know how to actually write php to do that?

    1. Melanne,

      I myself started with the twenty* themes. I have found it to be less work when using Genesis to create child themes. Personally, I usually use the starter child theme provided by StudioPress.

      As with any programming language or framework, it will take time to learn how it works. The Genesis framework allows you to do a lot of your modifications from the functions.php file and the style.css file.

      It would be best to checkout some tutorials;

      You could always ask for help on Twitter with the #genesiswp tag; as the community is really helpful and active.

      Good luck!

Leave a Reply

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