How a local-first Markdown editor should explain file access
Users should understand how Boreal Markdown handles files, settings, PDF export, and the absence of account-based cloud processing.
File-based Markdown users care about where their documents live. They want a tool that helps the file, not a hidden system that quietly becomes the real source of truth.
For Boreal Markdown, the public answer should be simple: version 1.0 opens Markdown files selected through iOS file access, previews them, edits source text, saves user-directed changes, and exports PDFs.
Durable content
The durable content is the user’s .md or .markdown file.
Boreal Markdown may keep local preferences, recent file references, editor defaults, preview defaults, export defaults, and save state so the app feels predictable.
Those records support the document workflow. They are not a hosted document store.
Website and app boundary
The app does not need accounts, hosted sync, cloud AI, or server-side document processing for P0. Those features would change the trust model and should be treated as later product decisions, not quiet website claims.
This companion site mirrors that boundary: it serves product pages, FAQ, blog, RSS, robots.txt, llms.txt, llms-full.txt, and lightweight /v1/* protocol routes.
It does not pretend the Worker stores the user’s Markdown files.