Skip to main content

Snippets Assets Policy

Defines what may be added to snippets/assets/, how assets are organised, and when they may be removed.

Scope


Rules

  1. Reference required before merge — no asset may be added to snippets/assets/ without a verified reference in at least one of: v1/, v2/, snippets/, or docs.json. Unreferenced assets will be removed during audits.
  2. Size limit: 2 MB per image file — images over 2 MB must be optimised before commit. PNG files over 500 KB should be reviewed for WebP conversion. The only exceptions are generated OG images in media/og-images/.
  3. No duplicate files across canonical subdirectories — canonical directory wins and duplicate copies should be removed during the owning migration. Current canonical subdirectories:
    • logos/ — shared logo assets, including the favicon bundle in logos/favicon/
    • media/ — shared raster/video assets, including media/og-images/ and media/images/site/
    • domain/ — legacy assets under audit only; no new permanent additions
    • data/ — non-image data assets
    • scripts/n8n/ — workflow docs pending relocation out of assets
  4. No backup files.bak, .backup, or similarly named files are not permitted. Use git history for rollback.
  5. No new files under the removed site/ bucketsite/ has been dissolved. New favicon assets go to logos/favicon/, new generated OG artifacts go to media/og-images/, and new site-specific images go to media/images/site/.
  6. domain/ is frozen pending phase-two audit — do not add new assets under domain/ unless the work is explicitly part of the approved domain migration. Existing domain assets must be classified as MOVE or ARCHIVE before relocation.
  7. No ad-hoc subdirectories — new subdirectories under snippets/assets/ require a policy update to this document. Use the existing subdirectories.

Canonical Directory Map

snippets/assets canonical directory map

Enforcement


Transition Status (2026-04-04)


Last modified on May 22, 2026