+{"id":"bd-4br","title":"Logseq: color-theme entity type + [[Catppuccin]] hub (alias UI/Color/Theme)","description":"## Goal\nIntroduce a **color-theme** Logseq entity type and a first instance hub for **Catppuccin**, so one page holds everything needed to apply that palette across the stack (Ghostty, Neovim, tmux, yazi, etc.), consistent with `[[Logseq/Entity]]` and `[[Logseq/Entity/software-project]]`.\n\n## Canonical naming\n- **Instance page title:** `[[Catppuccin]]` (short top-level canonical name, same spirit as software-project hubs like [[Lazygit]]).\n- **Alias for hierarchy / discoverability:** add page-level `alias:: [[UI/Color/Theme/Catppuccin]]` on `pages/Catppuccin.md` so the graph shows under `[[UI/Color]]` style navigation. Do not use the long path as the primary page title.\n\n## Deliverables\n\n### 1. Entity type page\n- Create `[[Logseq/Entity/color-theme]]` (filename `Logseq___Entity___color-theme.md`) documenting:\n - What counts as a color-theme entity (palette family / design system reused across apps).\n - Recognition and dedup (exact name, aliases, official style guide / org).\n - Frontmatter: instances use `logseq-entity:: [[Logseq/Entity/color-theme]]`.\n - Page shape: lean hub + optional sub-namespaces only when justified.\n - Relationship to `software-project`: ports/plugins can remain software entities linking back to the theme hub.\n - **Do not** prescribe or modify existing pages' `tags::`; follow garden tagging rules.\n\n### 2. Registry\n- Update `[[Logseq/Entity]]` to list **color-theme** alongside **software-project**, with a link to the new type page.\n\n### 3. First instance: Catppuccin\n- Create `pages/Catppuccin.md` with:\n - `logseq-entity:: [[Logseq/Entity/color-theme]]`\n - `alias:: [[UI/Color/Theme/Catppuccin]]`\n - `date-created::` set to the theme family’s real public origin date if discoverable (not “page added today”); omit if unknown.\n - **Identity:** official links, short description.\n - **Flavors:** Latte, Frappe, Macchiato, Mocha — names, light/dark intent, stable config IDs (e.g. `catppuccin-mocha`).\n - **Palette reference:** link official palette docs and/or minimal hex reference; add per-flavor subpages only if needed later.\n - **Stack matrix:** for each of Ghostty, Neovim, tmux, yazi — mechanism (built-in / plugin / package), config hooks, links to existing garden pages ([[Ghostty]], [[Neovim]], [[tmux]], [[yazi]]) and to dotfiles or config subpages (e.g. [[tmux/Config]]) where detail already lives.\n - **see-also::** peer themes as appropriate.\n\n### 4. Light cross-links\n- From relevant existing pages (e.g. [[Ghostty]]), add a brief pointer to [[Catppuccin]] where the theme is already mentioned or implied — no large rewrites.\n\n### 5. Optional bootstrap\n- If still using `.rulesync/config/logseq-entity.md` as fallback, add a short **color-theme** section aligned with the Logseq-native type page (or note that the type page is authoritative).\n\n## Acceptance criteria\n- `[[Logseq/Entity/color-theme]]` exists and reads as the SOP for this entity type.\n- `[[Logseq/Entity]]` links to it.\n- `[[Catppuccin]]` exists with `alias:: [[UI/Color/Theme/Catppuccin]]`, `logseq-entity:: [[Logseq/Entity/color-theme]]`, and enough structure that someone can wire Catppuccin across Ghostty, Neovim, tmux, and yazi from that hub plus linked notes.\n- LFM formatting (bullets, headings, no blank lines between blocks).\n- No changes to `tags::` frontmatter on existing pages unless the human explicitly asks.\n\n## References\n- Pattern model: `[[Logseq/Entity/software-project]]`, `.rulesync/config/logseq-entity.md`, `.rulesync/skills/logseq-entity/references/logseq-entity-type-pages.md`.\n","status":"open","priority":2,"issue_type":"feature","owner":"change-me@example.com","created_at":"2026-03-23T18:26:53Z","created_by":"CHANGE_ME","updated_at":"2026-03-23T18:26:53Z","dependency_count":0,"dependent_count":0,"comment_count":0}
0 commit comments