Markdown Database Views Without Giving Up Plain Files

A database view is a saved filter that re-renders your notes as a structured layout — a table of rows, a kanban board grouped by status, or a calendar plotted by due date. The underlying data never moves: it lives in the YAML frontmatter at the top of each Markdown note. What changes is only the lens you use to look at it. That is the idea behind database views in NoteLace: rich structure without a separate locked database.

Your Frontmatter Is Already a Schema

Every Markdown note can carry a frontmatter block — a short section of YAML between two sets of dashes at the very top of the file. NoteLace reads those fields as typed, first-class properties. A note for a blog post you're drafting might start like this:

---
status: drafting
due: 2026-07-01
priority: high
project: content-calendar
---

## How Coffee Affects Focus

Intro paragraph goes here...

The rest of the file is ordinary Markdown. The frontmatter is a thin metadata layer — it doesn't change how the note reads when you open it in the editor or export it to a .md file. But it gives the view engine something to query.

What a Database View Actually Is

A database view in NoteLace is a saved filter: you pick which notes to include (by notebook, tag, or a frontmatter condition), then choose how to render them. Three layouts are available:

• Table — one row per note, one column per property. Good for scanning and sorting a reading list or backlog.
• Board (kanban) — notes grouped into columns by a single property, typically status. Cards move between columns as you update the field.
• Calendar — notes placed on a calendar by a date property, typically due or published. Useful for a content schedule or a deadline overview.

All three views read from the same notes. There is no separate database, no sync to a third-party service, no proprietary format. Open any note from a view and you see the same Markdown file you always had.

A Worked Example: Content Calendar

Suppose you're managing a blog with a handful of posts at different stages. Three notes in a Content notebook:

Note 1 — "Coffee and Focus"

---
status: drafting
due: 2026-07-01
priority: high
project: blog
---

Note 2 — "Local-First Apps"

---
status: review
due: 2026-06-20
priority: medium
project: blog
---

Note 3 — "Keyboard Shortcuts Guide"

---
status: published
due: 2026-06-06
priority: low
project: blog
---

Create a view scoped to the Content notebook, grouped by status. The board renders three columns automatically — drafting, review, and published — with one card each. When "Coffee and Focus" moves through review and gets published, you drag the card and NoteLace writes status: published back into the frontmatter of that note. The calendar view of the same notes plots them by due date so you can see at a glance that a post ships on the 20th and another on the 1st of July.

No extra data entry. The note is the record.

Views Are Per-Workspace

Each workspace in NoteLace is its own self-contained environment: its own notebooks, notes, tags, and views. A Personal workspace and a Client Work workspace don't share views or leak properties between them. Views you create in one workspace stay there, which keeps project contexts clean without any manual filtering overhead.

Practical Use Cases

Reading list. Tag notes with reading and add frontmatter fields like author, rating, and status (to-read / reading / done). A table view sorted by rating gives you a ranked backlog in seconds.

Lightweight project tracker. Use a notebook per project, frontmatter fields status, assignee, and due, and a board grouped by status. It behaves like a stripped-down task board — without leaving your notes app or paying for another tool.

Content calendar. The example above. A calendar view by due keeps your publishing schedule visible; a board view by status shows what needs attention today.

Your Data Stays in Markdown

This is the part worth emphasising. Notes in NoteLace live in a local database on your device — not a proprietary cloud silo. When you export, you get standard .md files with the frontmatter intact. Any editor that understands YAML frontmatter (VS Code, Obsidian, iA Writer, a plain text editor) can read the result. You're not locked in.

The all features page lists what's available today, and Markdown notes app covers the broader editing and organisation story if you're still evaluating whether NoteLace fits your workflow.

Getting Started

NoteLace runs on macOS, Windows, and Linux. There is no free tier, but every plan includes a 14-day card-free trial so you can build real views against your own notes before committing. After any paid period, read and export access is retained — your data is always yours.

If you've been keeping Markdown notes but wishing they had a little more structure, frontmatter properties and database views are the right amount of structure: enough to filter, sort, and visualise, not so much that you're maintaining a separate system alongside your writing.