Support Style Settings plugin options

[saberzero1]

Currently, Quartz Themes skips configuration options used by the Style Settings Obsidian plugin.

Whenever possible, the following will be implemented for themes using Style Settings:

• Class toggles will be extracted and combined with the base theme to create variations/palettes of the theme. (Think mocha, latte, macchiato, and frappe variations of the Catppuccin theme)
• Component toggles will be extracted as extras and variations will be generated for all or a selection of them. (Think different callout styles from Glass Robo theme)
• Color settings will be extracted and generated as variations if they are a list of options. If they are a color picker, variations for all base Obsidian named color variables will be used instead. (red, orange, yellow, green, cyan, blue, pink, purple)
• Plugin-specific toggles will be ignored unless they are relevant in Quartz. (Think styling for Kanban boards)
• Layout settings will be ported if feasible (Reproducible in Quartz without heavily hampering user experience) and prioritized based on popularity (Minimal theme's left sidebar is a good example of a popular layout)
• Theme-specific features will be ported depending on their complexity and popularity. (Think the Mado-11 background wave (low complexity) or ITS TTRPG-related callout styles (high popularity))

[saberzero1]

Status:

• Obsidian theme extraction
  • Configure layout elements to extract style from via Obsidian workspaces.
  • Automate setup/teardown of themes.
  • Automate setup/teardown of plugins.
    • Style Settings.
    • Forced view mode (to enforce reading view on notes.)
    • Dataview (to embed Obsidian components into the note. Obsidian separates a lot of components in separate document fragments. This ensures everything is accessible for the extraction.)
  • Map all relevant query selectors from Obsidian to Quartz.
  • Automatically insert CDN fonts or fall back to defaults if not configured.
• Theme variants
  • Variant mappings (basically sets of Style Settings configurations. They are just JSON.)
    • All default (how the theme looks with Style Settings enabled, but no configuration/all default)
    • Predefined by theme author (e.g. Mocha, Latte, Macchiato, and Frappe for Catppuccin theme.)
    • Custom mapping sets.
  • Add variants.json to specify variants.
    • Configure repositories for variants.
    • Generate relevant files (readme and license) and table information.
    • Update setup instructions.

variants.json

• name (variant name)
• parent (name of theme)
• settings (set of Style Settings to use for this variant)
• target (path to theme variant. Probably themes/<parent>/<name>/_index.scss

Non-goals (for now)

• Automated updating of themes.
• Automated installing of new themes.
• Automated deployments of new preview repositories.
• Obsidian Publish mappings.