Thanks Jon, In terms of the generation we should be able to use our grunt build scripts to do this. There are plugins for each of the CSS preprocessors you mentioned.
https://www.npmjs.org/package/grunt-contrib-less https://www.npmjs.org/package/grunt-contrib-sass https://www.npmjs.org/package/grunt-contrib-stylus Thanks Justin On Mar 28, 2014, at 12:25 PM, Jonathan Hung <[email protected]> wrote: > Regarding themes, I think we would want to avoid the situation where we're > generating themes for CSS frameworks. There are a lot of CSS rules to theme, > and we would have to maintain this from release to release. > > I think we should create some general themes and let the user extend the > theme into their own application as needed. To create these themes, using > Less, SASS, or Stylus would be great as it will simplify authoring and > maintenance of themes. > > Thinking out loud, we can even use a site generator to generate themes using > source files that consist of only YAML front matter. The source file will > provide the values for the theme via front matter (like primary and secondary > colours), and the site generator would create themes based on a template. > This may not be practical, but I wanted to throw this idea out there in case > it leads to some interesting use cases. > > Otherwise using something more traditional like SASS/Less/Stylus and a > compiler to create contrast themes is fine with me. > > - Jon. > > > On Thu, Mar 27, 2014 at 9:14 AM, Justin Obara <[email protected]> wrote: > > On Mar 27, 2014, at 9:11 AM, Colin Clark <[email protected]> wrote: > > > > > On Mar 27, 2014, at 8:44 AM, Justin Obara <[email protected]> wrote: > > > >> Actually I was suggesting that we may not use the CSS Framework for the > >> Preferences Frameworks contrast themes either. Instead we'd provide a SASS > >> or Less file and some pre-generated versions all based off of custom > >> styles. This will allow it to be focused on Contrast (not general site > >> theming), extensible to different contrast themes that the integrator may > >> want, and also work across a broader range of sites (not just those > >> already using a specific CSS Framework). Although we may want to include > >> extension(s) that work with CSS framework(s) to better cover those cases > >> as well. > > > > Ah, yes. That makes sense. Sorry I misunderstood. So are you thinking that > > maybe we’d essentially just port the theme we’ve already got to Less (or > > SASS) and then go from there? > > Yes, this is what I was thinking. > > > > >> You are right though, from my standpoint this is largely theoretical and > >> could use more detailed exploration. > > > > Let’s do some exploration and see what makes the most sense. > > > > Colin > > > > > -- > JONATHAN HUNG > > INCLUSIVE DESIGNER, IDRC > > T: 416 977 6000 x3951 > F: 416 977 9844 > E: [email protected] > > OCAD UNIVERSITY > Inclusive Design Research Centre > 205 Richmond Street W, Toronto, ON, M5V 1V3 > > www.ocadu.ca > www.idrc.ocad.ca
_______________________________________________________ fluid-work mailing list - [email protected] To unsubscribe, change settings or access archives, see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work
