Twentytwelve too complicated.

  • Hi all,

    Is it too late to ask for a more simplified Twentytwelve as a default theme ? I think that Twentytwelve’s CSS is too complicated as a default theme.

    The CSS part of the theme is way bloated with px fall back just to support text-sizing of old IE which is not a problem because IE already has buildin Zoom (Ctrl+/-/0) The size of CSS is way too big and now it has separated CSS file for old IE too !

    I’m not saying that we should giveup IE support, but the px fall back are way too much, think about the performance aspect, why load all this fall back while its benefit is only for very little usecase.

    It’s better to just use rem without px fallback.

Viewing 6 replies - 1 through 6 (of 6 total)

  • Hi Paul,

    I’d consider one of WordPress’ main goals with bundled themes is for them to work the best they can out of the box on as many browsers/delivery platforms as possible.

    As of now, Twenty Twelve still supports (or attempts to support) all the way back to IE7 in some form or function. Yes, I agree that it gets to be kind of a lot doing all of the px and rem conversions, on the other hand, the older browsers will completely ignore the rem values, just as modern browsers will ignore the px values in preference to rem or em.

    Therefore, you’re certainly welcome to build a child theme absent the px values / ie.css, or even use Twenty Twelve as a base for a new parent theme. I don’t anticipate the architects of this theme will be suddenly removing all of the fallbacks, especially as 1.0 is already in the wild.

    Thread Starter paulwpxp

    (@paulwp)

    Hi Drew,

    Thanks for your explanation, I looked into this https://core.trac.www.ads-software.com/ticket/22044 and it only confirms validity of my conclusion that 2012 is way too complicated to be a default theme.

    I do love the aesthetic aspect of 2012, it’s a beauty, but it’s clearly not designed to be a default theme.

    Making a child theme out of 2012 is a pain, especially if 22044.6.patch is used, one has to repeat each bit of css for a child theme, and I can’t see this as a good practice.

    I was hoping this could be handled more gracefully, but as you mentioned, it’s a little too late now.

    ??

    Making a child theme out of 2012 is a pain, especially if 22044.6.patch is used, one has to repeat each bit of css for a child theme, and I can’t see this as a good practice.

    I’m about 90% done with my Twenty Twelve child theme and it hasn’t been any easier or more difficult than any of the others. The fact that the “theme options” are mostly automated and/or in the Customizer make my job a lot easier.

    Everyone is entitled to their own opinion though ?? And don’t forget, Twenty Ten & Twenty Eleven are still very viable, standards-ready themes.

    What about including a easier to handle/customize child theme with Twenty Twelve?

    Well… since the intent of a child theme is personalization/customization – wouldn’t it seem that each person’s goal with a child theme would probably different than the next?

    So what would be included with a child theme? I mean, making a basic child theme for 2012 is no different than 2011 or 2010 – it’s the customization that would be more difficult, and also different for each person!

    That being said – you should start seeing an influx of 2012 based tutorials and child themes all over Google quite soon – just like we did with all the previous themes.

    https://quirm.net/themes/twenty-twelve-child/

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Twentytwelve too complicated.’ is closed to new replies.