6888901468
* First cut * Temporarily disable composer.json for netlify build * POC * New recursive directory query, various refinements * Fix flexbox * new styled components plugin * Apply frontmatter delimiters * Mobile styles, animation * Search * Redesign, clean up * Nuke the cache, try again * fix file casing * Remove production env file * ID headers * Move app to new repo * Add frontmatter universally * Hide children changelogs * Add how to title * New callout tags * Revert inline code block change * Replace note callouts * Fix icons * Repalce images * Fix icon * Fix image links * Use proper SQL icon
4.0 KiB
| title | summary | iconBrand |
|---|---|---|
| CSS coding conventions | The CSS style guidelines we follow in our open source software | css3 |
CSS and SCSS Coding Conventions
Overview
This document provides guidelines for code formatting to developers contributing to SilverStripe. It applies to all CSS/Sass files in the SilverStripe core modules.
In 2016, SilverStripe started a rewrite of the styles of the CMS interface.
This rewrite is work-in-progress so code written prior to this
rewrite might not follow these conventions, and is placed in a legacy/ folder structure.
Browser support
Check our requirements documentation.
Tools and libraries
Styles are written in the SCSS language. We use Bootstrap 4 styles where possible.
Conventions
We follow the AirBnB CSS Conventions and the BEM methodology (block-element-modifier).
Because we use Bootstrap 4 which does not follow BEM naming convention there will be a lot of places where class names voilate BEM. However, please note that they are not a indicator of how to name classes. Use BEM conventions where possible.
Linting
We use sass-lint to ensure all new SCSS written complies with the rules below. It will be provided as an npm dev dependency. There are also quite a few sass-lint IDE integrations which highlight any linting errors right in your code.
We strongly recommend installing one of these into the editor of your choice, to
avoid the frustration of failed pull requests. You can run the checks on console
via yarn run lint.
File and Folder Naming
- All frontend files (CSS, JavaScript, images) should be placed in
a
client/folder on the top level of the module - Frontend files relating to the
frameworkCMS UI should be placed inadmin/client - The
client/src/componentsfolder should contain only reusable components (e.g. Button, Accordion). Presentation of these components should not rely on the markup context they're embedded in. - The
client/src/containersfolder should contain use-case dependent styles only (e.g. CampaignAdmin). Styles in here should be kept at a minimum. - The file name of styles nested within components and containers should inherit their
respective folder name for easy reference.
For example, a
components/FormActioncomponent has styles namedFormAction.scss). - The
client/src/stylesfolder contains base styles (reset, typography, variables) as well as layout-related styles which arranges components together.
Icons and Graphics
Most graphics used in the CMS are vector based, and stored as generated
webfonts in admin/client/src/font, which also contains a HTML reference.
The webfonts are generated through the Fontastic service.
If you need new icons to be added, please ping us on Github.
Legacy conventions
CSS written prior to SilverStripe 4.0 is not following the conventions outlined above.
It is contained in a legacy/ folder structure. If modifying these styles,
consider porting them over into the new structure. Otherwise, follow these conventions:
- Class naming: Use the
cms-class prefix for major components in the cms interface, and thess-ui-prefix for extensions to jQuery UI. Don't use theui-class prefix, its reserved for jQuery UI built-in styles. - Use jQuery UI's built-in styles where possible, e.g.
ui-widgetfor a generic container, orui-state-highlightto highlight a specific component. See the jQuery UI Theming API for a full list.