Closed (fixed)
Project:
DrupalCon Denver 2012 Website
Component:
Theme
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
22 Jun 2011 at 22:57 UTC
Updated:
3 Aug 2011 at 05:31 UTC
Jump to comment: Most recent
I'm leaning towards Omega myself. If anyone else feels strongly (and plans to help with theming) please speak up here.
Comments
Comment #1
Anonymous (not verified) commented+1 for the Omega theme.
Comment #2
vegantriathleteI'm good with Omega.
Comment #3
sirkitree commentedThere's also a really great argument for Tao here: I'm inclined to agree with simplicity and not adding complexity. Thoughts?
http://wiredcraft.com/blog/why-we-advise-against-most-starter-and-base-t...
Comment #4
juliaset commentedI usually only borrow parts from base theme...it always feels cleaner to just start a theme in pure HTML/CSS and then add in the appropriate Drupal bits.
Comment #5
kenwoodworth commentedI'm with juliaset on this one. We'll want to really control the experience for different devices so keeping things flexible should be key. To me that means not being tied down to any specific structure/grid system. The structure/grid will be there, but it'll be our own. That article also makes a few good points for not using a base theme.
Comment #6
sirkitree commentedOk, sounds like some good arguments for *no base theme*.
I've really grown accustomed to using LESS for CSS lately. Any thoughts/objections there? I've experimented with both SASS and LESS and found LESS to be cleaner, leaner, and much more CSS-like (and therefore more designer-friendly). The trick is coming up with a good workflow. I've been using Less.app for Mac http://incident57.com/less/ and it makes for a pretty seamless process.
My only thing I think we should NOT do is use the LESS module. Compiling less on the fly can have some benefits, like DOM variables, but I hate to risk WSOD for something like that.
Comment #7
sirkitree commentedI think we've decided to do our own theme with no base.