TypedMark Typed Markdown note systems
Essentials

Getting Started

Audience: first-time collection authors.

See also:

This non-normative tutorial builds a Core collection from one configuration, one concrete schema, and one note. A template is optional.

1. Create typedmark.md#

At the root of your notes folder, create typedmark.md. The frontmatter is the configuration; the body is yours to use for explanations (governed artifact format).

---
specification_version: 0.1.0
name: my-notes
description: My personal notes.
---

# My Notes

Meeting notes live in Meetings/ and are typed as `meeting`.

Those keys suffice for the configuration. Defaults include .typedmark, Git exclusion, UTC, validation severities, and stored note_type association.

2. Define a note type#

Create .typedmark/schemas/meeting.md. The file name (without .md) must equal the note_type (Note Type Schemas).

---
specification_version: 0.1.0
note_type: meeting
label: Meeting
icon: calendar
description: Notes for one meeting.
storage:
  folder_pattern: "Meetings"
  note_name_pattern: "{meeting_date} - {title}"
frontmatter:
  title:
    type: text
    not_blank: true
    nullable: false
  meeting_date:
    type: date
    generated: now
    nullable: false
---

A meeting note records one meeting: who, what, decisions.

This declares where meeting notes live and how they are named (storage rules), and which frontmatter fields they carry (Field Definition Reference). relationships, headings, and guidance are optional and default to "no constraints".

note_type can be omitted from the schema because its basename supplies it. Label and icon are optional. Without archive patterns, active storage applies.

3. Optionally add starter content#

Without a template file, starter state is derived. To add prose, create .typedmark/templates/meeting.md; its frontmatter can be partial or absent.

---
note_type: meeting
title: ""
meeting_date: null
---

## Agenda

## Decisions

The empty title and null meeting_date are template placeholders. A tool instantiating the template replaces them with user-provided and generated values before writing a conforming managed note (template placeholder rules).

4. Write a note#

Create Meetings/2026-06-10 - Kickoff.md:

---
note_type: meeting
title: Kickoff
meeting_date: 2026-06-10
---

## Agenda

Project kickoff.

## Decisions

We ship.

That note is a conforming managed note: its note_type maps it to the meeting schema (note-type mapping), its path matches the storage pattern, and every declared field is present with a valid value (managed note contract).

Where to go next#