obsidian-baseline: A customizable Obsidian theme with Minimal support

Why obsidian-baseline targets Obsidian reading and note organization

Baseline addresses the visual layer of an Obsidian vault rather than note management itself. Its goal is to provide a readable starting interface that works before configuration, then offer detailed controls for readers who want to adjust colors, spacing, typography, and other presentation details. The intended audience includes Obsidian users who spend substantial time reading notes, embedding images, viewing tables, and navigating their vault on both desktop and mobile.

The project describes itself as a foundational theme and presents its default appearance as the important baseline. That design choice favors users who do not want to tune every control immediately. At the same time, the available class system gives users direct formatting controls inside notes. Baseline therefore sits between a conventional fixed theme and a user-built CSS project. It supplies defaults, but its appearance is not fixed to those defaults.

This distinction matters because Obsidian themes can affect reading comfort without adding data-management functions. Baseline changes how notes and Obsidian interface elements appear. It does not claim to provide note versioning, synchronization, search, graph analysis, or a different knowledge-management model. Its scope is presentation and interface styling.

How Baseline combines CSS, Style Settings, and Minimal classes

The repository is primarily written in CSS and includes `manifest.json`, `theme.css`, a `src/` directory, and supporting assets. Based on that repository layout, Baseline follows Obsidian's theme package model: the theme is distributed around a manifest and stylesheet rather than as a separate application with a runtime process. The exact internal build steps are not documented in the README, so they should not be inferred from the directory names alone.

The customization layer has two documented components. First, Baseline integrates with Style Settings. The README specifically identifies colors, spacing, and typography as adjustable details. Second, the theme supports all filter and helper classes from Minimal. That inheritance gives Baseline a broad note-formatting vocabulary without requiring each class to be implemented from the beginning.

The resulting data flow is mostly presentational. A reader changes a Style Settings value, or adds a helper class such as `banner` to an image link in a note. Obsidian then applies the corresponding CSS presentation. This approach is convenient because note formatting remains visible in Markdown, but it also means that a reader must understand class names and their requirements. For example, `banner-fade` requires `banner`, while `banner-title` requires `banner-icon`.

Installing Baseline and completing a first configured note

The README does not provide shell commands, package-manager steps, version numbers, or manual file-copy instructions. It directs readers to the Obsidian community theme page through the “Add to Obsidian” link. Installation should start from that community listing or from the repository release artifacts if they appear there.

After installation, Baseline is intended to work as a selectable theme without requiring settings changes. The first real configuration task documented by the project is adding a helper class to content. For an image banner, add the `banner` class at the end of the image link. Optional additions include `banner-fade` for a faded edge and a `banner-icon` callout for an icon. A `banner-title` class then moves the inline title beside that icon. Vertical positions can be adjusted from `y0` through `y100` in increments of five, but only after the required `banner` class is present.

Readers who are migrating from supported themes can use the project's Style Settings Converter at `https://baseline.svnaxis.me/converter/`. Baseline also provides a Marketplace for community-made presets at `https://baseline.svnaxis.me/marketplace/`. The documentation does not explain preset review criteria, compatibility guarantees, or update behavior, so existing settings should be compared after conversion rather than assumed to transfer perfectly.

Block classes give Baseline notes more than a color palette

The helper classes provide Baseline's most concrete note-level capabilities. Block widths include `wide` and `max` for an entire note, along with pane-relative sizing for tables, Bases, and images. Names such as `table-100`, `table-max`, and `table-wide` control how those elements fill the available pane. These settings can be useful in mixed-content notes where a narrow reading column is comfortable for prose but inefficient for tabular information.

Card formatting covers both Dataview tables and ordinary bullet lists. The required `cards` class establishes card layout for Dataview tables, while `list-cards` applies it to bullet lists. Additional classes control alignment, image fill, aspect ratios, and column count. Supported ratios include `cards-16-9`, `cards-1-1`, `cards-2-1`, and `cards-2-3`. Column counts range from `cards-cols-1` through `cards-cols-8`.

Embed behavior can also be narrowed. `embed-strict` removes the embed background, while `embed-hide-title` conceals an embedded file's title. Images gain filters for blending, inversion according to color mode, circular cropping, outlines, and interface shadows. `img-grid` activates image grids. These controls solve visible layout problems, but they also make note syntax longer. A note that accumulates many classes can become harder to maintain than its rendered appearance suggests.

Baseline's dependency on Minimal creates both reuse and complexity

Support for all Minimal filter and helper classes is Baseline's most consequential comparison point. For an Obsidian user already familiar with Minimal, that compatibility can reduce the need to learn a separate formatting vocabulary. Existing notes using documented Minimal classes may have a more predictable visual result under Baseline, although the README does not promise complete visual equivalence.

The trade-off is an extra dependency in the decision-making process. Baseline is not simply a self-contained visual layer with a few switches. Its supported formatting model includes classes owned by another theme, while configuration is further connected to Style Settings. If a user later removes or replaces those components, some note-level formatting may need another home. The README does not document migration away from Baseline or the behavior of undeclared Minimal classes, so that area remains unconfirmed.

Minimal itself is the more direct alternative for readers whose main priority is that class system rather than Baseline's interface treatment. Choosing Minimal avoids a second theme's interpretation of the same classes. Choosing Baseline instead makes sense when its default workspace styling, Style Settings design, mobile treatment, and converter or preset services are the desired combination. Neither option is universally better; the useful comparison is between Baseline's presentation layer and the user's existing Minimal dependency.

Mobile support and maintenance affect the upgrade decision

Baseline explicitly describes enhanced navigation, refined menus, and comfortable spacing for mobile use. The repository is not archived, and its last push was on 2026-10-12. Recent releases include version 4.1.0 on 2026-10-08, version 4.0.0 on 2026-10-02, and version 3.2.12 on 2026-07-31. These dates indicate recent project changes, but the README does not provide a formal compatibility policy, automated test report, or release-to-release migration guide.

Upgrade cost is therefore tied to settings and note content rather than a documented deployment process. A user who relies on Style Settings, a converted configuration, Marketplace presets, or many helper classes should review the appearance of representative notes after changing theme versions. Documentation is also thin on rollback, removed settings, and backward compatibility. This does not establish that upgrades are unsafe; it means the repository text does not make such a guarantee.

The project uses the MIT license. That permits reuse, modification, distribution, and sublicensing subject to the license's conditions, including preservation of its copyright and permission notice. This is a technical reading of the stated license terms, not legal advice. Organizations should review the actual `LICENSE.txt` before redistributing modified theme files.

Editorial conclusion

Obsidian users who want extensive formatting controls without starting from an empty stylesheet should evaluate Baseline, especially if they already use Style Settings or Minimal conventions. Users who only need a small visual change or do not want community-class dependencies should first confirm that the additional styling layer does not complicate their workflow. Adoption depends on checking the appearance of banners, cards, embeds, images, and tables in the notes that matter most.

Frequently asked questions

Official sources

1. License: MIT
2. Project website
3. README
4. Releases
5. svnaxis/obsidian-baseline on GitHub