Skip to content

Brand Assets Directory

This directory holds the actual binary/source brand asset files — logos, logotype lockups, favicons, and similar visual assets — for Devonshire Digital LLC and its ventures. It is separate from docs/, which holds the records describing what assets exist, what's approved, and what's required (see below) — this directory holds the files themselves.

Structure

  • company/ — assets belonging to the parent entity, Devonshire Digital LLC. See docs/company/brand-assets.md for the record of what's approved here.
  • ventures/<slug>/ — assets belonging to a specific venture, keyed by the venture's stable repository slug (e.g. digital-products), not its public brand name — slugs don't change when a brand name changes, per docs/standards/naming-standard.md. See that venture's own brand-requirements or brand-assets document for what's approved or required.

Within each of company/ and ventures/<slug>/:

  • source/ — editable original files an asset was produced from (e.g. GIMP .xcf, vector source files). These are the files to open and edit when an asset needs to change.
  • exports/ — final, rendered deliverables generated from a source/ file (e.g. .png, .ico, .svg), ready to use in a product, listing, or website. An export should always be traceable back to the source file it came from (matching filename stem is sufficient; no separate manifest is required unless that stops being adequate).

What does not live here

  • Records of what's approved or required — those are Markdown documents under docs/ (for Devonshire Digital LLC) or the relevant venture's own docs/ (for a venture), not in this directory. This directory is asset files only.
  • Per-product marketing assets (e.g. a specific product's marketplace listing screenshots) — those belong under that product's own directory (e.g. ventures/<slug>/products/<product-slug>/assets/), since they're scoped to one product's lifecycle, not the venture's or company's overall brand identity.

Approval status

A file existing in this directory does not by itself mean it is approved. Approval status is tracked in the relevant Markdown record (docs/company/brand-assets.md for the company; equivalent venture-level documents for a venture), never inferred from a file's mere presence here.

Report an issue about this page