# bevacqua/css

:art: CSS: The Good Parts

Repository: https://github.com/bevacqua/css
Canonical: https://ross.abutalabs.com/products/bevacqua-css
Homepage: https://ponyfoo.com
License: MIT
License Family: permissive
Topics: css, style-guide
Last push: 2023-10-30T19:21:37+00:00

## Health v2 (maintenance only)
Score: 32/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 0, release rhythm 35, longevity 100
- inputs: {"age_days": 4492, "days_push": 1038, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: no_releases
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1063, forks 133 (observed 2026-08-28T04:03:26.402404+00:00)

## What it is
A CSS style guide ('nico-style') documenting conventions for class naming, namespacing, selectors, and organization to avoid collisions and confusion in CSS codebases. It is a markdown document meant to be shared and enforced within teams, not a runnable tool.

## Use cases
- establish css naming conventions for a team
- avoid class name collisions in large css codebases
- write a component namespace convention for styles
- reduce use of !important in stylesheets
- onboard new developers to a css code style
- pair with a javascript style guide for frontend consistency

## When to choose
- you want a readable, opinionated baseline for css conventions to adapt for your team
- your team suffers from class name collisions and inconsistent css organization
- you want a lightweight style guide to fork rather than a linter or framework

## When to avoid
- you need automated style enforcement or linting rather than a written guide
- you want a css framework or utility library with actual code
- you prefer methodology-agnostic or tool-enforced approaches like stylelint configs

## Facets
- artifact type: learning-resource
- maturity: maintenance
- function: css-framework, documentation
- domain: web-development, frontend, web-design, documentation
- platform: -
- tags: css, style-guide, naming-conventions, best-practices, code-style, web-server

## Member repositories
- bevacqua/css (main) score 32

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:03:26.402404+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T06:56:38.560067+00:00, confidence not recorded.
  - readme: https://github.com/bevacqua/css (fetched 2026-08-28T04:03:26.402404+00:00, sha d5aefbe7d3f1)
  - homepage: https://ponyfoo.com (fetched 2026-08-29T12:58:26.091362+00:00, sha 4613aa7b65ae)
  - site_page: https://ponyfoo.com/articles/talk-about-web-performance (fetched 2026-08-29T12:58:26.118575+00:00, sha 61fd597bf9fb)
  - site_page: https://ponyfoo.com/articles/9-quick-tips-about-npm (fetched 2026-08-29T12:58:26.121100+00:00, sha 5d8547cfd88e)
  - site_page: https://ponyfoo.com/articles/tiny-story-about-complexity (fetched 2026-08-29T12:58:26.100828+00:00, sha 5e18e44510eb)
  - site_page: https://ponyfoo.com/articles/es2016-features-and-ecmascript-as-a-living-standard (fetched 2026-08-29T12:58:26.108282+00:00, sha ffe22a428009)
  - site_page: https://ponyfoo.com/articles/es6-object-literal-features-in-depth (fetched 2026-08-29T12:58:26.116508+00:00, sha eca1a1333740)
- Data as of 2026-08-30T08:39:29.467469+00:00.