hiloki/flocss resource
CSS organization methodology. observed · 2026-08-28
Health v2 · maintenance only
32/100
- Activity 0
- Release rhythm 35
- Longevity 100
Flags: no_releases no_license
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 4530
- days_rel: n/a
- days_push: 2134
- n_releases_24m: 0
Adoption not part of the score
1007 stars · 66 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
FLOCSS is a CSS organization methodology that structures stylesheets into Foundation, Layout, and Object (Component/Project/Utility) layers, drawing on OOCSS, SMACSS, BEM, and SuitCSS concepts. It is a documented specification with naming conventions rather than a runnable library or framework.
Use cases
- organize css for large projects
- structure stylesheets into layers
- apply bem naming conventions to css
- modular css architecture guidelines
- decide where css rules belong
- scale css across a team
When to choose
- you want a layered, modular CSS architecture inspired by OOCSS, SMACSS, and BEM
- you need clear naming conventions and layer rules for a team's stylesheets
- you are designing a CSS style guide for a web project
When to avoid
- you need an installable CSS framework with ready-made components
- you want utility-first CSS like Tailwind
- you need tooling or automation rather than a written methodology
Facets
learning-resource · maturity maintenance
css-framework documentation web-development frontend web-design css-architecture css-methodology bem oocss smacss naming-convention specification web-server
1 source
- readme: https://github.com/hiloki/flocss · fetched 2026-08-28 · 3c615420b9ea
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| hiloki/flocss | main | 32 |
For agents
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem