Use case or problem
Currently, Bases operates on a One Note = One Record paradigm. While this aligns perfectly with the atomic note philosophy, it creates significant friction for users who prefer to maintain centralized, flat logs (e.g., a single Movie Log.md with 100 movies listed, a Daily Journal.md with a bulleted list of daily tasks, or a Ledger.md of financial transactions).
Forcing these users to split a single, lightweight list into 100 separate Markdown files just to utilize the Table or Cards view adds unnecessary file bloat, complicates vault navigation, and breaks the user’s preferred data structure.
Proposed solution
Introduce a new Source Type when creating or configuring a Base. In addition to “Folder” and “Tag,” add “File Blocks” or “Inline List.”
When a single file is selected as the source, the Base parser should treat individual Markdown elements within that file as the records.
Supported Inline Formats
- Bulleted / Task Lists with Inline Fields (Dataview-style)
The Base parses each list item as a row, reading inline metadata formatting (e.g., [Key:: Value]). - Standard Markdown Tables
The Base natively hooks into an existing Markdown table inside a note, providing the advanced filtering, sorting, and Card layout UI on top of raw pipe-separated text. - Frontmatter Arrays / Sub-properties
Alternatively, the Base could parse a structured YAML/TOML array within the note’s single front matter block.
Examples:
- The Matrix [genre:: Sci-Fi] [rating:: 5] [watched:: 2026-05-10]
- Inception [genre:: Sci-Fi] [rating:: 4] [watched:: 2026-06-01]
OR
movies:
- title: The Matrix
genre: Sci-Fi
rating: 5 - title: Inception
genre: Sci-Fi
rating: 4
UI/UX Implementation Details
The Setup Flow: When creating a Base, selecting “Source: Single File” prompts the user to select the parsing method (e.g., “Parse bullet points,” “Parse Markdown table,” or “Parse YAML array”).
Two-Way Editing (Crucial): If a user edits a property inside a Card or Table view, the Base edits the specific string or block line inside that single file, maintaining Obsidian’s commitment to live two-way data syncing.
The “Card Layout” Render: For a movie list inside one file, selecting the Cards View would instantly turn those 100 bullet points into 100 visual tiles, rendering inline image links as cover art.