Index
Misc Planning
Expansive Tag Table
I want to have a clear listing of all the “tags” that can be applied to themes. Give me exactly what I want.
Palettes with themes that implement multiple palettes are tricky. I think I’ll just tag the “default”, and multiple_palettes accounts for those willing to put in a minimum of further effort.
However, “features” will always be tagged regardless of the default state.
Having trouble remembering which word variant to use? “Typography versus typographic; alternative vs alternate” - I always will pick the shortest variant.
(The ideal tag gives at least a few good options, but not too many to become meaningless. 1-entry tags should be avoided.)
Comments | Light/Dark Mode[a] | Genre | Palette[b] | Philosophy[c] |
Pre_1.0 Compatibility_issues[d] Broken_functionality[e] requests_font_installation Requests_<plugin> Unavailable[f] Incomplete_light_mode Extra_snippets Contrast_issues, Chinese_only, | Dark Light Dark_and_light Hybrid? (e.g. Kabadoni) | Native[g] Minimalistic > Material > stripped_down[h] Retro Exotic > Glass > Futuristic > Neon > Neumorphism > Fantasy > Brutalist Gradients Rounded[i] Squared Animated Glow Shadows Transparent Inspired-by <inspired by> <color> [j] | Cool Warm Hot Colorful Paper Wood Coffee Darker[k] Lighter Low_contrast High_contrast Pastel Hybrid_brightness <Named palettes> Monochrome Monotonal[l] Bitonal Tritonal Colorblind[m] | Accessibility Opinionated[n] Ergonomics Clean Cozy Playful Typography Focus Readability Meditative Special Purposes – TTRPG Novelty |
Features
Inclusions | Support | Functions | Colorful |
Cssclasses > Kanban > Gallery > Multiple_columns Callouts Cards Banner[o] Custom_html Custom_icons Alternate Checkboxes[p] > Community checkboxes File_explorer_icons | <x>_support (Plugins) <y>_support (Snippets) Modifies_<plugin> Vim Support Mobile Support PDF Export Support | Highlight active line Focus_mode Mini_mode Auto_hiding Image_zoom | Rainbow Folders Multicolor_headers Rainbow headers Colorful_frame Accent_based |
Layout | Layout separation [q] | Style Settings | Text Appearance |
Multiple Palettes Modified_Layout Multiple Layouts Background image Macos_tab_buttons Dense_layout Sparse_layout | Line_layout_separation[r] Padded_layout_separation brightness_layout_separation Borderless | Style Settings Lite Style Settings Medium (40+) Style Settings Large (> 200) | Larger_text Smaller_text Monospace_editor Always_monospace Typographic_customizationCustom_font Preferred_font |
Specifics[s]
Plugins | Snippets | Named Palettes | Inspirations |
Canvas Bases Kanban Excalidraw Dataview Banner Tasks | Community Checkboxes Multi Column Banner | OLED Gruvbox Cappuccin Behave Everforest Coffee_palette Dracula Rose_pine Zenburn Material_ocean Solarized Gruvbox_material Wombat256, Tomorrow, > Base16 Monkeytype Halcyon Flexoki Nightfox Novadust Neovim_default Tiniri Penumbra Atom_one Horizon Kanagawa Biscuit | Ubuntu Notion Things Typora Gnome, adwaita … Typora_vue_theme Wikipedia Github iA_writer monokai_pro |
Potential additions -
File explorer word wrap
Codeblock numbers
,
Breadcrumbs_outline, -> https://github.com/subframe7536/obsidian-theme-maple
readable_line_length_configurability
multicolor_headers
Emphasis patterns
“Paper on desk”, two tones, editor brightest
Retro obsidian; Oldsidian, Obsidian_origin
Based_on, (theme derived from)
Customized_font,
Hybrid-brightness
Minimal Tag Table
Let’s keep things simple. Give me some general, easy to understand options and let me narrow it down.
Definitions of Genre, Philosophy and Features
philosophy is about the dev's approach to making the theme and how they intend to deal with users
genre is the overall flavor of the theme and how it looks/feels
features are self-explanatory.
- Floodlight, 2025
Proposed Tag Table
Genre | Features | Philosophy |
Minimalist Retro Exotic Inspired by x OS or y Desktop Environment | Customizable Vim Support Mobile Support Support for Plugin z Support for Snippet a | Platform-theme Opinionated Cozy Playful |
[a]You don't need to add these, they are here by default.
[b]In order to keep platform themes from dominating here, these tags will only be applied to the theme's default appearance.
[c]These tags should only be applied if the author declares that he's doing that. Very simple descriptions can ignore this section entirely.
[d]This is a gradient. Compatibility issues implies there's something wrong but you can ignore it; broken_functionality implies something isn't working, like a feature, or it's obstructively broken. More ambitious themes are more likely to end up on broken_functionality.
[e]Things being broken is usually just a pre_1.0 thing, but if the theme isn't as advertised, put this down.
[f]The theme can't be found in the theme store. You don't have to finish these.
[g]Replicates an operating system's default look. This is not the case with the default theme.
[h]Not *just* minimalism - actively removing parts of the UI for aggressively simplified presentation.
[i]More rounded than normal
[j]The theme predominantly is this particular color.
[k]Darker / lighter than default dark theme.
[l]This theme uses three "colors" - lighter, darker, and the "accent". Bitonal has two accents, tritonal three. More probably is just "colorful".
[m]Implements or advertises colorblind accessibility.
[n]The author makes clear a particular vision for the theme.
[o]Not the plugin
[p]Alternate_checkboxes is differentiated from community_checkboxes by whether it uses the standard snippet or just does its own thing. Community is standard.
[q]Layout separation is how the sidebars, ribbon, window panes are separated from one another.
[r]The default theme already does this. I typically only use this tag if the theme expands upon this or makes the line clearer than default.
[s]To help keep future tags from being ambiguous, I'd appreciate if you add what tags you get here.