Scoria

The Scoria manual

Scoria is a native knowledge base that opens an Obsidian vault unchanged. A vault is a folder of Markdown files; Scoria reads that folder, reads the .obsidian configuration beside it, and opens. Nothing is imported and nothing is moved.

This manual covers what Scoria does today. Where something is not implemented yet it says so in place, rather than describing Obsidian's behavior and leaving you to find out.

Note

Scoria is an independent implementation and is not affiliated with Obsidian. Obsidian is a trademark of Dynalist Inc.

Warning

This is version 0.1.0. Reading a vault is well covered; writing one is the half being built now. Keep a backup of any vault you open with it, and see what differs from Obsidian for the current gaps.

Getting started

PageWhat it covers
What Scoria isWhat it is, what it is not, and who it is for
Install and runGetting a binary, the command line, NixOS
Open a vaultWhat a vault is, what happens on first open, what gets read
Coming from ObsidianWhat carries over, what to expect, how to try it safely

Using Scoria

PageWhat it covers
The windowThe three panes, tabs, history, the ribbon, what is where
The Files viewThe file tree, sort order, what is hidden, the context menu
Reading viewHow a finished note is displayed, and what is not drawn yet
Editing a noteLive Preview and Source mode, smart lists, saving, undo
Find and replaceThe in-note search panel, regex, multiple cursors
Backlinks and the side panesBacklinks, unlinked mentions, Outgoing links, Outline, Tags
SearchSearching the whole vault, reading the results, explain
Switcher and paletteThe quick switcher and the command palette
The graph viewThe global and local graph, filters, color groups, forces
Managing notesNew, rename, move, copy, delete — and the link rewriting

Writing notes

Scoria understands Obsidian Flavored Markdown: CommonMark, the GitHub extensions Obsidian uses, and Obsidian's own syntax. These pages are the syntax reference.

PageWhat it covers
Basic formattingHeadings, emphasis, lists, quotes, rules, line breaks
Internal links[[Wikilinks]], Markdown links, headings, blocks, aliases
Embedding files![[Embeds]] of notes, sections, blocks and images
Callouts> [!note], the built-in types, folding
Properties and tagsYAML frontmatter, #tags, aliases
Block ids and footnotes^block-ids, footnote definitions, inline footnotes
Tables, code and mathTables, fenced code, $math$, %%comments%%

Settings

PageWhat it covers
SettingsThe tabs Scoria shows, where each value comes from, why it is read-only
HotkeysHow hotkeys.json is applied, rebinding, unbinding

Reference

PageWhat it covers
Search syntaxEvery operator in the query grammar
Commands and hotkeysThe command ids, their names, and the default bindings
Obsidian compatibilityThe four tiers, and the conformance numbers
What differs from ObsidianThe honest list of gaps and deliberate differences
Vault files and formats.obsidian/, Canvas, Bases, what Scoria reads and writes
How Scoria worksThe crates, the one-parser rule, the cache, the renderer
PerformanceMeasured indexing and editor numbers, and what costs time
TroubleshootingThe failures people actually hit
GlossaryThe vocabulary this manual uses

Conventions in this manual

Command ids are written as editor:toggle-source, because that is the string your hotkeys.json uses and the thing you can search for in the command palette. Keys are written as Obsidian labels them — Ctrl + Shift + F — and on macOS, Ctrl means Cmd unless a page says otherwise. Settings are named as the Settings window names them, with the .obsidian key in code beside them, because the file is often the faster way to find out what a setting actually is.

Where a feature is unfinished, the manual says not yet and, where it is useful, why.

Source: sites/scoria/content/docs/index.md