# dracula/dracula-theme architecture

> Architecture diagram of the GitHub repository dracula/dracula-theme, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2026-04-10). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/dracula/dracula-theme
- Repository: https://github.com/dracula/dracula-theme

## Overview

1. This repository is the Dracula Theme umbrella/organization repo, not a single application. Its main role is to document the design system, coordinate contributions, and provide a directory of many independently maintained theme repositories.

2. The core architectural pattern is “many small theme projects, one shared brand.” The top-level repo contains a large `themes/` directory where each subdirectory represents a target application or tool, such as `visual-studio-code`, `vim`, `alacritty`, `terminal-app`, `jetbrains`, and hundreds more.

3. These theme folders are managed as Git submodules, which is supported by the presence of `.gitmodules` and the `update-submodules` GitHub Action. That means the umbrella repo does not own all theme files directly; it points to separate repositories and pulls them in as versioned dependencies.

4. The repository boundary is split between shared governance and per-app implementation. The top-level README defines the canonical Dracula palette, accessibility expectations, and contribution workflow, while each theme repo contains the actual app-specific theme assets and installation instructions.

5. The shared design input is the color palette documented in the README. The “Dracula” and “Alucard” palettes act as the source of truth for all downstream themes, ensuring visual consistency across editors, terminals, UIs, and syntax highlighters.

6. The downstream data flow is straightforward: maintainers take the shared palette/spec, map it to a target application’s theming model, and publish that as an individual theme repository. Users then install the theme from the app-specific repo or from draculatheme.com.

7. The external website, `draculatheme.com`, is a major distribution and documentation surface. The README repeatedly directs users there for installation instructions, the full theme catalog, contribution guidance, and the color specification reference.

8. Governance and community management live in GitHub. The repo includes issue and pull request templates, indicating a standardized contribution intake process, and a `stale.yml` workflow for maintenance automation on issues/PRs.

9. This repository has no application runtime, backend service, or build pipeline for producing a single deployable artifact. It is primarily a catalog, specification, and coordination layer for a distributed set of theme packages.

10. The main architectural diagram should therefore show a central Dracula brand/spec hub feeding many independent theme repos, with GitHub Actions maintaining repository hygiene and submodule synchronization, and draculatheme.com serving as the public documentation/installation portal.

11. In practical terms, the strongest boundaries are:
- shared design system and documentation at the top level,
- independent theme implementations per application,
- GitHub-based automation and contribution workflow,
- external installation/distribution via the website and each theme’s own repo.

12. If you want to diagram this repo accurately, treat `themes/` as an index of externalized modules rather than a single codebase, and treat the README as the authoritative specification that all subprojects conform to.

Main entry points: [`README.md`](https://github.com/dracula/dracula-theme/blob/main/README.md) (README), [`themes`](https://github.com/dracula/dracula-theme/tree/main/themes) (Themes), [`.gitmodules`](https://github.com/dracula/dracula-theme/blob/main/.gitmodules) (Submodules), [`.github/issue_template.md`](https://github.com/dracula/dracula-theme/blob/main/.github/issue_template.md) (Issue form)

## Diagram (Mermaid)

```mermaid
flowchart TD

subgraph group_governance["Governance"]
  node_issue_template["Issue form<br/>template<br/>[issue_template.md]"]
  node_pr_template["PR form<br/>template"]
  node_contributors(("Contributors<br/>community workflow"))
  node_contribution_flow(("Contribution flow<br/>governance flow"))
end

subgraph group_spec["Brand & Spec"]
  node_readme["README<br/>spec docs<br/>[README.md]"]
  node_palette{{"Palette<br/>color spec<br/>[README.md]"}}
end

subgraph group_distribution["Distribution"]
  node_site["Website<br/>docs portal"]
  node_install_flow(("Install flow<br/>user path"))
  node_catalog["Catalog<br/>directory index"]
end

subgraph group_themes["Theme Index"]
  node_themes_index[("Themes<br/>submodule index")]
  node_theme_repos[("Theme repos<br/>external repos")]
  node_app_mapping["App mapping<br/>theme adaptation"]
end

subgraph group_automation["Automation"]
  node_gitmodules["Submodules<br/>git config<br/>[.gitmodules]"]
  node_update_action["Sync themes<br/>github action"]
  node_stale_action["Stale bot<br/>github action<br/>[stale.yml]"]
end

node_readme -->|"defines"| node_palette
node_readme -->|"describes"| node_themes_index
node_readme -->|"points to"| node_site
node_themes_index -->|"backed by"| node_gitmodules
node_gitmodules -->|"references"| node_theme_repos
node_update_action -->|"syncs"| node_gitmodules
node_stale_action -->|"maintains"| node_contribution_flow
node_issue_template -->|"standardizes"| node_contribution_flow
node_pr_template -->|"standardizes"| node_contribution_flow
node_contributors -->|"follow spec"| node_readme
node_palette -->|"feeds"| node_app_mapping
node_app_mapping -->|"implements"| node_theme_repos
node_site -->|"hosts"| node_install_flow
node_theme_repos -->|"publishes"| node_install_flow
node_themes_index -->|"organizes"| node_catalog
node_catalog -->|"mirrors"| node_site
node_contribution_flow -->|"produces"| node_theme_repos
node_readme -->|"references"| node_site

click node_readme "https://github.com/dracula/dracula-theme/blob/main/README.md"
click node_palette "https://github.com/dracula/dracula-theme/blob/main/README.md"
click node_themes_index "https://github.com/dracula/dracula-theme/tree/main/themes"
click node_gitmodules "https://github.com/dracula/dracula-theme/blob/main/.gitmodules"
click node_update_action "https://github.com/dracula/dracula-theme/blob/main/.github/workflows/update-submodules.yml"
click node_stale_action "https://github.com/dracula/dracula-theme/blob/main/.github/workflows/stale.yml"
click node_issue_template "https://github.com/dracula/dracula-theme/blob/main/.github/issue_template.md"
click node_pr_template "https://github.com/dracula/dracula-theme/blob/main/.github/pull_request_template.md"
click node_catalog "https://github.com/dracula/dracula-theme/tree/main/themes"

classDef toneNeutral fill:#f8fafc,stroke:#334155,stroke-width:1.5px,color:#0f172a
classDef toneBlue fill:#dbeafe,stroke:#2563eb,stroke-width:1.5px,color:#172554
classDef toneAmber fill:#fef3c7,stroke:#d97706,stroke-width:1.5px,color:#78350f
classDef toneMint fill:#dcfce7,stroke:#16a34a,stroke-width:1.5px,color:#14532d
classDef toneRose fill:#ffe4e6,stroke:#e11d48,stroke-width:1.5px,color:#881337
classDef toneIndigo fill:#e0e7ff,stroke:#4f46e5,stroke-width:1.5px,color:#312e81
classDef toneTeal fill:#ccfbf1,stroke:#0f766e,stroke-width:1.5px,color:#134e4a
class node_issue_template,node_pr_template,node_contributors,node_contribution_flow toneBlue
class node_readme,node_palette toneAmber
class node_site,node_install_flow,node_catalog toneMint
class node_themes_index,node_theme_repos,node_app_mapping toneRose
class node_gitmodules,node_update_action,node_stale_action toneIndigo
```

## Components

### Governance

Contribution intake and repository hygiene

- [Issue form](https://github.com/dracula/dracula-theme/blob/main/.github/issue_template.md): template · Standard intake for reports and requests · `.github/issue_template.md`
- [PR form](https://github.com/dracula/dracula-theme/blob/main/.github/pull_request_template.md): template · Standard contribution checklist for theme updates · `.github/pull_request_template.md`
- **Contributors**: community workflow · Governed entry point for maintaining the shared brand and individual themes
- **Contribution flow**: governance flow · Issues and pull requests feed maintenance and theme changes

### Brand & Spec

Canonical Dracula palette and documentation

- [README](https://github.com/dracula/dracula-theme/blob/main/README.md): spec docs · Canonical palette, contribution guidance, and umbrella repo overview · `README.md`
- [Palette](https://github.com/dracula/dracula-theme/blob/main/README.md): color spec · Dracula and Alucard source colors used across themes · `README.md`

### Distribution

Public site and downstream theme delivery

- **Website**: docs portal · draculatheme.com as the public catalog, installation, and reference surface
- **Install flow**: user path · Users install from the website or from individual theme repositories
- [Catalog](https://github.com/dracula/dracula-theme/tree/main/themes): directory index · Entry point to browse the many theme subprojects · `themes`

### Theme Index

Large catalog of submodule-backed theme repositories

- [Themes](https://github.com/dracula/dracula-theme/tree/main/themes): submodule index · Directory of independently maintained theme repositories · `themes`
- **Theme repos**: external repos · Independent app-specific theme implementations maintained outside the umbrella repo
- **App mapping**: theme adaptation · Translates the shared palette into each target application's theming model

### Automation

GitHub Actions that maintain the umbrella repo

- [Submodules](https://github.com/dracula/dracula-theme/blob/main/.gitmodules): git config · Maps theme folders to external repositories · `.gitmodules`
- [Sync themes](https://github.com/dracula/dracula-theme/blob/main/.github/workflows/update-submodules.yml): github action · Keeps submodule pointers and theme directories aligned · `.github/workflows/update-submodules.yml`
- [Stale bot](https://github.com/dracula/dracula-theme/blob/main/.github/workflows/stale.yml): github action · Automates issue and pull request hygiene · `.github/workflows/stale.yml`

## Connections

- README → Palette: defines · Documents the canonical Dracula color system
- README → Themes: describes · Positions themes as a directory of many independent projects
- README → Website: points to · Routes users to the public documentation and installation portal
- Themes → Submodules: backed by · Theme folders are managed as submodules
- Submodules → Theme repos: references · Each folder points to an external repository
- Sync themes → Submodules: syncs · Automates submodule updates
- Stale bot → Contribution flow: maintains · Cleans up stale issues and pull requests
- Issue form → Contribution flow: standardizes · Provides a structured issue intake path
- PR form → Contribution flow: standardizes · Provides a structured pull request path
- Contributors → README: follow spec · Use the README as the source of truth
- Palette → App mapping: feeds · Shared colors are adapted per target app
- App mapping → Theme repos: implements · Produces app-specific theme assets
- Website → Install flow: hosts · Public entry point for installation and reference
- Theme repos → Install flow: publishes · Individual repositories distribute installable themes
- Themes → Catalog: organizes · Acts as the browsable theme catalog in the umbrella repo
- Catalog → Website: mirrors · The website is the main external catalog and docs surface
- Contribution flow → Theme repos: produces · Community contributions land in downstream theme repos
- README → Website: references · Documentation repeatedly defers to the website
