Thanks for improving layout-style-css. This repository is a CSS layout library, so changes should keep structure, spacing, responsive behavior, and package contracts separate from visual styling.
npm install
npm run build
npm run lint
npm testRun the full release gate before opening a release PR:
npm run release:verify- Keep authored CSS in
styles/. - Regenerate
dist/withnpm run build; do not hand-edit generated dist files. - Keep public layout classes prefixed with
ly-. - Leave colors, typography, borders, shadows, native controls, focus states, themes, and modes to
ui-style-kit-css. - Add structural aliases in
styles/layout-ui-style-kit-bridge.cssonly when they map to layout primitives or layout recipes. - Update README,
docs/wiki, andCHANGELOG.mdwhen a public class, export, recipe, release workflow, or package behavior changes.
Every change that affects public behavior should update or preserve:
test/layout-css-contract.test.mjsfor package, CSS, docs, and tarball contracts.test/demo-smoke.test.mjsfor rendered demo behavior.test/pages-artifact.test.mjsfor GitHub Pages output.stylelintfor authored CSS formatting.
- The package remains publishable as a public npm library.
- The npm tarball contains only intended release files.
- README examples use exported package entrypoints.
- Documentation links resolve to versioned files.
- Demo controls remain compact on mobile and tablet viewports.
- New CSS does not introduce UI Style Kit-owned visual declarations.
The source for the project wiki is docs/wiki/. If GitHub Wiki is enabled for the repository, mirror those files into the wiki remote after the main branch documentation is merged.