Ahmed Adel6 downloadsCustomize Obsidian and supported community plugin interfaces with profiles and scoped CSS.

Interface preview rendered from the plugin UI. Not a live Obsidian screenshot.
Customization Studio is a non-invasive Obsidian plugin for personalizing the appearance of Kanban, Spaced Repetition, Obsidian Bases, Tasks, Dataview, Calendar, and Day Planner. It keeps module logic separate, applies plugin-owned styles, and stores customization profiles through Obsidian's plugin data API. It does not edit target plugin sources, settings, review schedules, Base definitions, or user content.
Author: Ahmed Adel
Minimum Obsidian version: 1.9.0 (required for Bases support)
Screenshots are not available yet.
Customization Studio has no required account, paid feature, analytics service, or backend. Its runtime code does not upload notes or task content. Profiles, visual settings, and custom CSS are stored locally through Obsidian's plugin data API. Exporting a profile copies its settings and CSS to your clipboard; review them before sharing, as they may include vault-relative paths or URLs.
Network requests are optional and depend on what you configure:
url() or
fonts. Global profile CSS can use @import. Module CSS rejects @import
and scopes selectors, but does not block resource URLs. Selector scoping
is not a security sandbox. Imported profiles can contain CSS and image
URLs, so only import profiles or paste CSS from sources you trust.The runtime reads its own stylesheet in Obsidian's configuration folder and resolves user-selected local background images inside the vault. It does not require access to files outside the vault. It does not modify note content, other plugins' settings, task dates, or review schedules. Obsidian's own sync or installed extensions may handle data separately from this plugin.
Column/card colors and opacity, automatic and manual column coloring, spacing, padding, radii, column blur, board image and overlay options, independent card and column glow, and visual drag states. Local image paths are resolved through Obsidian's vault resource-path API; external images accept HTTP(S) URLs. Column override colors are keyed by visible title and assigned separate temporary DOM tokens, so distinct columns remain distinct during reordering while their DOM elements remain mounted. Overrides cannot distinguish columns with duplicate titles, and title-based overrides do not follow a renamed column.
The inspected selectors correspond to Kanban 2.0.51. The installed target version and live drag interactions have not been tested in a vault. A right-click card color menu is not provided: the inspected Kanban component passes card IDs to its drag/drop components but does not expose a verified stable ID on rendered card DOM; adding DOM context handlers risks interfering with Kanban's native card menu.
Flashcard appearance, shared question/answer typography, review controls, answer/review button colors and states, spacing, and transitions. The inspected selectors correspond to Spaced Repetition 1.15.4. The inspected DOM uses shared content rather than distinct question/answer text containers; progress styling is not provided. Live study-session compatibility has not been tested.
Table and cards-view settings using documented native Bases CSS variables. Bases is detected as an Obsidian core plugin. Some requested visual details have no verified supported hook and are intentionally not exposed. Requires Obsidian 1.9.0 or later.
Query row spacing and dividers, group headings, date metadata chips, and edit
form section spacing. Checkbox status, urgency colors, priority, validation,
and click handlers remain owned by Tasks. Source-inspected at Tasks 8.6.0,
commit 9fecdd6; this version of Tasks requires Obsidian 1.13.1.
Standard result-table padding, text size, headers, alternating rows and
borders, list spacing, and inline-field surfaces. Arbitrary DataviewJS-generated
HTML is not covered. Source-inspected at Dataview 0.5.68, commit 5ad0994.
Calendar text size and outer spacing, today/day/heading/dot colors, and an
optional weekend surface. Uses documented #calendar-container variables,
not generated Svelte class names. Source-inspected at Calendar 1.5.10,
commit ef3f269.
Timeline background and hour separators, time-block font, corner radius,
inner content spacing, and shadow. Time positions, duration geometry, event
colors, native active borders, and drag/resize handlers are not changed.
Source-inspected at Day Planner 0.35.1, commit 9c483b3.
The four new integrations are off by default, including when older profiles load. Duplicate a built-in profile, open Integrations, select the target, and enable customization. Their colors follow the active theme by default; turn off Follow theme colors to apply custom colors. All four support independent settings, module-scoped CSS, profile import/export, and cleanup on disable/unload. These source checks do not certify live-vault behavior; the four installed target plugins still need real in-app tests.
main.js, manifest.json, and styles.css from the same published
release. Put them directly into <vault>/.obsidian/plugins/customization-studio/.data.json if updating, then reload Obsidian and enable
Customization Studio under Community plugins.For releases after the original 0.1.0, only the three standard assets are
attached. The original 0.1.0 also has an installable ZIP and LICENSE; those
published files are left unchanged. Do not install GitHub's automatic
source-code archive as if it were the runtime package. The MIT license remains
in the repository and its full notice is included in main.js.
BRAT can install a repository that publishes releases containing the plugin files. Install BRAT from Community plugins, then:
Ahmedadel200066/Obsidian-Customization-Suite. (including the final period).BRAT and release installation have not been tested in an Obsidian vault.
The repository root is kept installable: it contains the generated main.js,
manifest.json, and generated styles.css. Clone/copy the repository contents
directly into <vault>/.obsidian/plugins/customization-studio/, then enable
the plugin in Obsidian. Do not copy the repository into an additional nested
folder.
Requirements: Node.js 20 or later and npm.
npm ci
npm run build
npm test
npm run build bundles src/main.js and local modules into the root-level
main.js. The Obsidian obsidian API remains external. The build rejects
unresolved local imports and validates the root manifest and generated stylesheet.
It copies styles/core.css to the standard root-level styles.css, which is
the runtime stylesheet distributed with the plugin. Edit the source stylesheet
and run the build rather than editing the generated copy.
To rebuild on source changes:
npm run dev
The workflow in .github/workflows/release.yml runs when a version tag is pushed,
installs locked dependencies, builds and tests the project, validates the
bundle, verifies that the tag matches manifest/package versions and versions.json,
attests main.js, manifest.json, and styles.css using GitHub build
provenance, and publishes those three files as the release assets. It stages the
assets in a draft and publishes only after upload. It refuses to overwrite
an already published release. Attestations are stored by GitHub, not uploaded
as additional release files.
styles.css produces a warning but does not prevent
startup..workspace-tab-header-container
UI class. Zero opacity sets a transparent background without applying
opacity to tab labels or icons. Backdrop blur is ignored by browsers that do
not support backdrop-filter. Neither behavior has been verified against a
live Obsidian window or every theme.fundingUrl link. There is no direct
donation button in the plugin settings. No integration context-menu action
is registered because no
stable, verified menu hook for the supported plugin views was found.@import.Report bugs through the repository Issues tab. Include your Obsidian version, target plugin and version, steps to reproduce, expected and actual behavior, and relevant console errors. Do not attach vault data, private notes, or credentials.
Before proposing changes:
modules/<module-id>/.npm ci, npm run build, and npm test.Please do not commit secrets, user-vault content, or generated dependency directories. Changes to licensing terms require confirmation from the project owner. See LICENSE for the current MIT terms.
See bug-fix verification, growth-change verification, and publishing checklist.
These checks remain necessary before claiming runtime compatibility:
.obsidian/plugins/customization-studio/, enable the plugin, and confirm the
ribbon shortcut opens the settings tab.prefers-reduced-motion enabled.If Customization Studio helps you, you can support Ahmed on Buy Me a Coffee. The same destination is available through the plugin details support link.