Skip to content
This repository has been archived by the owner on Dec 10, 2024. It is now read-only.

Principles

Dieter Peirs edited this page Oct 18, 2016 · 2 revisions

Chopstick Boilerplate is built upon the following principles. Please keep these in mind when contributing and/or using this framework.

Low specificity

A single-depth-class-based architecture based on the BEM naming methodology.

Highly decoupled

Avoid reliance on other bits.

  • Separation of Concerns: let each piece of code solve its own problems
  • Single Responsibility Principle: one thing, one thing only, one thing well
  • Open/Closed Principle: add via extension, not modification

Highly composable

  • We build the bits that build the bits
  • Make everything opt-in and configurable: expose API-like CSS

Keep it simple

  • The Principle of Least Surprise: make sure expectations are met, and nothing else
  • Murphy’s Law: Pick the option that is the most resilient, even if it is the most boring one
Clone this wiki locally