Skip to content

Meta

Coding Conventions: Group code by module / atomic-ish semantics

I have been following atomic design semantics in all the component libraries I am building at work. But is it worth applying to my small website?

This decision-record was published on


Status Replaced

Replaced by "group components by how they are used".

Details

  • elements, blocks, groups, templates and behaviours (instead of atoms, molecules, ...)
  • see docs/project-structure

Why

  • pedantic
  • atomic-ish design system
  • clearer module boundaries
  • segregate shared components and utils from specific domains

Trade-offs

  • ugly enterprise import statements
  • even uglier with all the ../../ (typescript was struggling with aliases)

Go back to top of the page