The ASKII Component Standard (ACS)

A parts catalog for the web.

Each component has a code, a contract, and a barebone implementation. Free to use with attribution. CC BY 4.0.

← All standards

CRD001 · why ACS

Why the ASKII Component Standard?

Most projects rebuild the same buttons, forms, and cards from scratch, a little differently every time. That drift makes software harder to maintain and hand off. ACS fixes it by giving each part a name, a contract, and one barebone implementation, so a component means the same thing on every page and in every framework. Build it once, reuse it everywhere, and keep it accessible and fast by default.

CRD001 · naming

A code is a family and a version.

Every component is named by a three-letter family and a version, like BTN001 or NAV002. A version is a distinct component with its own behavior and contract: CRDCON is the Card family scoped to host a contact form, separate from the generic CRD001. Variants are different: a variant is a CSS modifier on an existing component, same contract, different look, written as a class such as .horizontal or .compact. Versions change behavior, variants change appearance.

This very block is a CRD001.

TAB001 · catalog

HDR001HeaderLogo + navigation banner.
NAV002NavigationMenu container; holds links, search, buttons.
FTR001FooterContentinfo landmark.

Proof

This site runs on the parts it documents.

The components listed above are featured across studioaskii.com (codes are listed above their respective components). The site is built with Astro, but the components are framework-agnostic and can be used in any front-end framework or vanilla HTML.