Skip to content

Asset Pipeline

This document records the asset strategy before a build pipeline exists.

Current Strategy

  • Keep CSS and JavaScript simple.
  • Load theme-owned assets from the theme directory.
  • Avoid adding Bootstrap, jQuery, or custom frameworks without architecture justification.
  • Do not introduce build steps until they are documented and required.

Future Pipeline

A future pipeline may handle:

  • CSS organisation and minification;
  • JavaScript bundling only if justified;
  • design tokens;
  • image optimisation;
  • generated static assets;
  • versioned assets for cache busting.

Dependency Rule

New dependencies require PR Notes explaining why native OpenCart/theme code is insufficient, how the dependency affects performance, and how it will be maintained.

Documentation Rule

Any build or install steps must be documented in the PR and in this file when they become project-wide behaviour.