obsidian-theme/kleokl7_Claude-Code-Obsidian-Theme
1
0
Fork 0
mirror of https://github.com/kleokl7/Claude-Code-Obsidian-Theme.git synced 2026-07-22 04:50:29 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
kleokl7_Claude-Code-Obsidia.../docs/implementation-roadmap.md
kleokl7 95a4e356bf Review fixes from the eight-angle pass 
- release.sh guard: escape version dots and require the versions.json
  entry to match manifest.json's minAppVersion (stale copy-paste trap)
- chevron: declare position:relative ourselves instead of leaning on
  stock; drop the dead background-image:none; honest comment about
  mirrored stock metrics
- body --font-weight fallback removed — dead since both schemes now
  bind it to their tuning dial
- install script: usage on empty input; read without -r so
  drag-and-dropped (backslash-escaped) vault paths work
- roadmap: note the pre-existing callout-table border gap; point at
  README for the release procedure instead of duplicating it

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-17 01:41:47 +02:00

6.5 KiB
Raw Permalink Blame History

Implementation roadmap — future work

Specs for work that is deliberately not implemented yet. Each item was scoped during the July 2026 design review so it can be picked up later without re-research. Nothing here should be started without owner approval.

Already shipped from that review (July 2026): naming sweep to Claude Code Orange, light-mode tuning dials, accent-aware forwarded-task chevron, table color parity via Obsidian's --table-* variables, companion install script, versions.json + release-script guard, fonts/trademark/scroll-support docs.

1. Coverage gaps — styling recipes

The owner doesn't use these surfaces today. If the theme's audience grows, these are the recipes. Common rule: reuse existing tokens (--cc-bg*, --cc-table-*, --cc-border*, --interactive-accent) — never invent a parallel palette.

Obsidian Bases

Element Treatment
View chrome / toolbar --cc-bg-alt, border --cc-border, radius --radius-m
Table/grid cells reuse --cc-table-bg / --cc-table-header / --cc-table-border
Selected row/cell --cc-selection
Primary buttons --interactive-accent + --text-on-accent
Cards layout card bg --cc-bg, soft border, radius --cc-radius

Scope under the Bases leaf type (confirm the live data-type string before writing selectors). Done when opening a Base doesn't feel like leaving the theme.

Canvas

Canvas bg slightly deeper than --cc-bg (or subtle dot grid in --cc-border-soft); card fill --cc-bg/--cc-bg-alt; card border --cc-border, selected --interactive-accent; group frames faint coral mix with large radius; edges --graph-line, active edge coral; menus styled like the command palette cards.

PDF view

Toolbar/background --cc-bg-alt; warm (not cold black) page shadow; coral find-highlight. Never recolor the PDF page content itself.

Hover popovers / tooltips / suggestion menus

--cc-bg-alt surface, --cc-border, --cc-radius, warm soft shadow. The preview markdown inside inherits note styling once the surface is themed.

Notices / toasts / modals

Modal surface --cc-bg/--cc-bg-alt + --cc-radius + --cc-border; CTAs already covered by button.mod-cta; notices optionally get a coral left border.

Math (KaTeX / MathJax)

.math foreground var(--cc-text); display math gets its own vertical margin (~1em 0) independent of the tight --p-spacing; don't restyle TeX internals beyond foreground color.

Mermaid

Prefer variables Mermaid reads if Obsidian exposes them; else node fill --cc-bg-deep/--cc-bg-alt, stroke --cc-border (coral for emphasis), edges --graph-line, text --cc-text. Needs explicit .theme-light and .theme-dark sets.

Tables inside callouts (known niche gap)

Stock Obsidian re-declares --table-border-color on .callout with a callout-tinted mix, which outranks the theme's body-level mapping — so a table nested in a callout draws callout-tinted outer/widget borders against the theme's warm cell grid (pre-existing behavior, unchanged by the 2026-07 table work). If it ever matters: re-map the variable on .callout too, at the cost of stock's callout-tinting design.

Popular plugins (only if audience demands)

Plugin Direction
Calendar day cells --cc-bg-alt; today = coral ring/fill; note dots in accent
Kanban lane --cc-bg-alt, card --cc-bg, pills reuse tag styles
Dataview tables reuse --cc-table-*; task queries inherit checkbox styles if the DOM matches
Excalidraw theme the canvas background only; don't fight its own theme engine

Print / export

@media print: force light paper tokens, black text, underlined links, hide app chrome. Publish sites use different CSS entry points — separate effort.

2. Sticky-headings header gutters

The breadcrumb overlay clears the nav arrows / view actions with a magic number (padding: 0 110px !important on .sticky-headings-root). Breaks under icon packs, UI font scaling, RTL, narrow panes, or a header redesign.

  • Option A — CSS-only heuristic (interim): padding-left: max(96px, 12vw); padding-right: max(120px, 14vw); — test at 900/1200/1600 px pane widths.
  • Option B — measure (recommended): on layout-change/resize, measure the .view-header-left / actions cluster widths from the companion plugin and set --cc-header-pad-left/right on the leaf; theme consumes var(--cc-header-pad-left, 110px). Fallback keeps today's behavior.
  • Option C — abandon title-bar overlay: style the plugin's default sticky stack. Most stable, loses the breadcrumb-in-title design.

Verify: narrow + wide panes, plugin settings that add icons, RTL if available, mobile untouched (rules already gated :not(.is-mobile)).

3. CSS maintainability

theme.css is ~1700 lines and still navigable via section banners. In order of value:

  1. TOC comment at file top matching the section banners — zero risk.
  2. Strict section discipline — plugin hacks never land inside token blocks; new plugin work goes in section 10+.
  3. Multi-file src/ + concat build — only when a second maintainer exists or the file passes ~2.5–3k lines. Obsidian still ships one theme.css; build.sh concatenates.
  4. Reduce !important on links only if a real conflict appears.
  5. Keep documenting selector contracts for fragile integrations (sticky headings DOM, scroll-map classes, --table-* mapping pinned to the Obsidian version it was inspected against).

4. Community listing quality

Present: manifest.json, theme.css, versions.json (+ release guard), release.sh, README screenshots, MIT license.

Remaining when distribution becomes a priority:

Item Action
Chrome screenshots add screenshots/chrome-light.png / chrome-dark.png showing sidebar + tabs, not just the note body
theme-preview.png regenerate after any visual change; it's the storefront
Release notes always pass real --notes to release.sh
Issue template OS, Obsidian version, light/dark, Style Settings on/off, plugins
README badges latest release + min app version (optional)
Community plugin store submit Claude Scroll Map only if manual/script install proves insufficient

The release procedure itself lives in README → Releasing (maintainers) (release.sh enforces the guards). Roadmap-only additions: update README when user-facing options change, and spot-check installing from the release download rather than the working copy.