How hoover900/not-so-epic_source-files works
What this project is (type + purpose)
This repository is not an application/codebase; it’s a design/asset working-files repository for the “Not so Epic Noir” theme.
Evidence from structure + README:
• README: “Where all the working files … are stored” → implies source design files, not compiled/runtime artifacts.
• File types:
• .afdesign / .aftemplate → Affinity Designer working files/templates
• .kra → Krita working files
• Directories map to asset domains: UI/, controllers/, logos/, posters/ (organized by platform/console).
How to read the file structure (and what to model)
Top-level components are “asset families”:
UI/
• Represents the core UI kit and templates that likely influence multiple outputs.
controllers/
• Per-console controller art sources (Dreamcast, Genesis, PC-Engine, SNES).
• Mostly .kra → likely raster/painted controller images.
logos/
• Platform/system logos in .afdesign.
• Typically vector sources intended for export as SVG/PNG at multiple sizes.
posters/
• Poster/background sources, organized by platform (PSX, arcade, dreamcast, etc.).
• Mostly .kra → painted/edited backgrounds, platform-specific.
Goal: show how assets are partitioned.
• Nodes:
• UI/
• controllers/<system>/
• logos/
• posters/<system>/
• Node with:
• Primary file formats (.afdesign, .aftemplate, .kra)
• Typical exported outputs (even if implied): PNG, SVG, JPG
• Ownership/concerns (“UI kit”, “Controller overlays”, “System logos”, “Platform posters”)
Goal: show how work files become shipped theme assets.
Suggested components + flows:
Designer workstation
• Tools:
• Affinity Designer (edits .afdesign / .aftemplate)
• Krita (edits .kra)
This Git repository (Working Files)
• Stores editable sources
• “Export assets” produces PNG/SVG/JPG variants
Theme distribution/packaging repo (external)
• Receives exported assets
End user environment (external)
• “Theme engine / frontend” that consumes final assets (keep generic since the repo doesn’t specify)
• Workstation → Git repo (commit/push)
• Git repo → Workstation (pull/checkout)
• Workstation (export) → Distribution repo (add exported assets)
• Distribution repo → End user (release/package)
“Per-Asset-Type Detail” (optional but “most detailed”)
• UI asset lifecycle (templates → UI elements → exports)
• Logo lifecycle (vector master → multi-size exports)
• Poster lifecycle (background master → platform variants → exports)
• Controller lifecycle (base art → button overlays → exports)
Internal components (in-repo)
• UI working files (UI/*.afdesign, UI/*.aftemplate)
• Controller artwork sources (controllers/*/*.kra)
• Logo vector masters (logos/*.afdesign)
• Poster/background masters (posters/*/*.kra)
Tooling components (external but essential)
• Affinity Designer
• Krita
• Git client + GitHub (or remote VCS hosting) (implied by repo)
Output/consumers (external)
• Exported assets (PNG/SVG/JPG; include as an artifact store node)
• Theme package/distribution repo (where exported assets live)
• Theme runtime/consumer (the UI/theme system used by end users)
Interactions:
• Editing happens in Affinity/Krita
• Sources are versioned in Git
• Exports are generated from sources
• Exports are integrated into the final theme package consumed by users
Architectural patterns/principles visible here (call these out)
Even though it’s not code, there are clear organizing principles worth annotating:
• Domain-based asset organization: UI vs logos vs posters vs controllers.
• Platform/system partitioning: posters/controllers grouped by console/system folder.
• Source-of-truth separation: working files (.afdesign, .kra) are “masters”; exports are downstream artifacts (likely stored elsewhere).
• Template-driven design: presence of .aftemplate suggests reusable templates (e.g., poster templates, layout templates).
Important note about unknowns (handle explicitly)
The README is minimal, so don’t invent specifics (e.g., exact theme engine). Instead:
• exact output formats and sizes
• naming conventions
• whether exports are stored in a separate repo or generated during release