CSS Framework recommendations

[Jonathan Hung]

Hi Michelle,

It would be possible to use a CSS framework to replace most of FSS (i.e. a
CSS framework can replace FSS linearization and layout). One sticking point
may be theming since generating themes for a framework is not straight
forward.

Essentially we will need to identify all the relevant CSS rules in the
framework and replace the values with our own. There may be an programmatic
way to do this, but from what I've seen this will largely be a manual
process since each change needs to be visually verified.

Also, when there are updates to the framework, we would have to account for
any changes to the themes. This creates a maintenance burden. Currently
Zurb updates Foundation roughly once a month (reference: Foundation
changelog <http://foundation.zurb.com/docs/changelog.html>) and we would
monitor the _settings.scss
file<https://github.com/zurb/foundation/blob/master/scss/foundation/_settings.scss>for
changes. We can probably expect this pace going forward since this
space changes so rapidly.

However this may present an interesting opportunity to contribute to the
CSS framework community by providing methods for generating inclusive
themes.

I've singled out theming as a possible issue, but there may be other issues
as well. I think this would require a more detailed investigation.

- Jon.



On Tue, Mar 25, 2014 at 10:16 AM, Michelle D'Souza <michelled33 at gmail.com>wrote:

> Thanks for sending this, Jon. I really like the detailed chart that was
> made prior to the recommendation.
>
> Can you please clarify for me what the recommendation is for Infusion in
> terms of getting rid of FSS?
>
> Thanks,
>
> Michelle
>
>
>
>
>
> On 2014-03-25, at 9:59 AM, Jonathan Hung <jhung at ocadu.ca> wrote:
>
> Hi everyone,
>
> After some time doing research into the utility of 3rd party CSS
> frameworks to be used for Fluid, the following is the proposed
> recommendation:
>
> - 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.
>
> For more details, please refer to this document on the Fluid wiki:
>
> http://wiki.fluidproject.org/display/fluid/Fluid+Project+Support+for+CSS+Frameworks
>
>
> Please feel free to comment and ask questions.
>
> Thanks!
>
> - Jon.
>
> PS. Thanks to Johnny and Anastasia for helping out with the research.
> --
>
> *JONATHAN HUNG*
>  INCLUSIVE DESIGNER, IDRC
>
> *T:* 416 977 6000 x3951
>  *F:* 416 977 9844
>  *E:* jhung at ocadu.ca
>
> *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 - fluid-work at fluidproject.org
> To unsubscribe, change settings or access archives,
> see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work
>
>
>


-- 

*JONATHAN HUNG*

INCLUSIVE DESIGNER, IDRC



*T:* 416 977 6000 x3951

*F:* 416 977 9844

*E:* jhung at ocadu.ca



*OCAD UNIVERSITY*

Inclusive Design Research Centre

205 Richmond Street W, Toronto, ON, M5V 1V3



www.ocadu.ca

www.idrc.ocad.ca
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idrc.ocad.ca/pipermail/fluid-work/attachments/20140326/077a518e/attachment.html>