Hi Jonathan, Thanks for your hard work researching CSS frameworks for use in Fluid-related websites and demos. I edited your wiki page a bit, just to clarify the goals and approach that we’ve taken. I’ll summarize it here:
Up to version 1.5, Infusion shipped with a built-in CSS framework called the Fluid Skinning System. In the time since FSS’ inception, we've experienced a massive shift in the way websites are designed and implemented. Unfortunately, the Fluid Skinning System hasn't kept pace. As a result, we have deprecated it in Infusion 1.5. We recommend that users of Infusion choose from any of the available third-party frameworks based on their own needs and requirements. As of Infusion 2.0, we will remove FSS entirely. Infusion components don't rely on any CSS framework, and we will continue to ensure that they are styled in a way that is unlikely to conflict with popular tools like Bootstrap and Foundation. For the foreseeable future, we don't plan to include a CSS framework within Infusion, nor to require that our users select a specific framework. For our own demos and websites, you’re recommending Foundation. I think your arguments are compelling, particularly the built-in support for REM sizing. +1. Colin On May 5, 2014, at 2:13 PM, Jonathan Hung <[email protected]> wrote: > Hi everyone, > > I have summarized the recommendation for CSS frameworks here: > http://wiki.fluidproject.org/display/fluid/Fluid+Project+Recommendation+for+Use+of+CSS+Frameworks > > Please take a look and feel free to comment. > > - Jon. > > > On Wed, Apr 23, 2014 at 11:26 AM, Jonathan Hung <[email protected]> wrote: > Hi everyone, > > I'm just trying to wrap up the discussion about the CSS framework > recommendation for Infusion. > > To summarize the following is the updated recommendation based on earlier > discussions: > > - CSS framework is not recommended for Fluid components at this time > primarily due to the lack of custom name spacing. Without proper name > spacing, there is a chance that there will be classname collisions which will > make it difficult to integrate Fluid components. > > - CSS framework is fine to be used for websites, demos, and other integration > / non-component scenarios. > > - Zurb Foundation is the suggested framework to be used. > > - Continue using default styles in Fluid components and leave it to the > integrator to customize with their own CSS framework if they choose to. > > - There may be an opportunity to add new features to Learner Preferences that > can transform CSS framework components (like navigation bars and button > links). Further discussion is encouraged. > > - We will not create contrast themes for CSS frameworks. Creating a theme is > non-trivial (lots of values to adapt) and s high maintenance (each major or > minor release will need to be tested - occurs roughly once a month). > > - Contrast theme generation using a CSS pre-processor to be investigated. > Possible pre-processors include: Less, SASS, and Stylus. This will be a > separate discussion. > > For additional details, please refer to this document on the Fluid wiki: > http://wiki.fluidproject.org/display/fluid/Fluid+Project+Support+for+CSS+Frameworks > > > We have already adopted some of these recommendations internally (i.e for the > FLOE Metadata Authoring demo), and we would like to formalize this going > forward. > > Please chime in. _______________________________________________________ fluid-work mailing list - [email protected] To unsubscribe, change settings or access archives, see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work
