About this page
This document will only show the basics in a condensed syntax. It is highly recommended that you review the in-depth walkthroughs and introductions for more information.
Please Note the order of the files is still under development.
The order of class names is anything from FSS goes first and your own custom CSS files go last, for example:
The order of class names is anything from FSS goes first and your own custom class names goes last, for example:
This is intended as a broad overview of changing FSS. All changes should be done in your stylesheet. For a more detailed explanation, please see [Overriding FSS].
To override any FSS you should have a selector that at the very least [matches the specificity of the FSS selector].
An example of over-riding FSS could be when you want to change a columns default width:padding:margin values.
Assuming you have an
fl-col-flex3 instance somewhere you want to change. You can do this 2 ways:
- To change this setup for all
fl-col-flex3instances, change the selector definition itself in your stylesheet (ie. copy and rewrite the
- To change this setup for just one
fl-col-flex3instances, in your stylesheet you should have a selector that at the very least [matches the specificity of the FSS selector] in your stylesheet, and change the values there.
A Caveat in Overriding FSS
In some situations, we have used the
!importantrule to ensure things behave as intended for [UI Options]. You might be required to add this to your new rules as well.
Please see the [FSS API] document to view all available FSS CSS convenience class names.
Contains containers, columns, basic layout management, and layout linearization class names. These class names can go on virtually any element.
Example this would make a 250 pixel wide container aligned to the right:
Example this would make 3 flexible width columns of link containers:
Advanced layout mechanisms (formlery known as Helpers) are CSS class names structured in such a way to lay out widgets, tabs, menus, and other common GUI concepts. These mechanisms make certain best practice and sound markup assumptions (ie. tabs require anchors inside list items).
Example this would make a series of 3 tabs aligned to the right of the page
Text in FSS basically means changing the font-family, size, letter spacing, line-height, and alignment.
Example this would justify text within a paragraph, and set the size to 1.3 ems
Themes are colorizations and stylistic decorations added to text and containers. Themes can also remove these attributes too. Themes work best with other aspects of FSS, but they have broad effects that work on general markup too.
Example this would make itself and everything nested within it colorized according to the rules outlined in the High Contrast theme:
FSS and Fluid both adhere to a strict naming convention for class name selectors.
The template for FSS looks like fl-[thing][role][state], with some rules:
- multiple words are in camelCase, so they might look like fl-[thingWithMultipleWords][roleWithWords][state]
- components are always the first "thing", so they would look like fl-[componentName][thing][role]-[state]
[thing] = required the concept the class name is referring to at the most general yet still meaningful level (eg. fl-tabs, fl-widget, fl-component, fl-col, fl-container, etc)
[role] = optional the purpose or action of
THING, which could be a more detailed version of
THING (eg. fl-tabs-centered, fl-col-flex, fl-container-500, fl-widget-titleBar)
[state] = optional a modifier of the
THING, which is only temporary and dependant on other actions (eg. fl-button-left-disabled, fl-widget-content-draggable)
The template for FLUID selectors looks like flc-[componentName][thing][role]-[state], with the same rules as FSS selectors.
The reason we do this is to separate the different purposes of selectors: one to style things, one to find things in the DOM. This way, you could change your behavioural code without affecting your appearance and vice versa.