Lapis Notes Developer Docs

These docs describe the public plugin surface for authors and integrators. Internal boot details stay in the project architecture spec and are not published here.

Start here

1. Read What is a Lapis plugin?.
2. Review the runtime overview.
3. Create a manifest.
4. Build a first plugin.
5. Use the development workflow in a test vault.

Plugins should use documented app services rather than reaching into workspace internals.

Core API topics

• App model
• Commands
• Vault
• Workspace views
• Editor
• Events
• Metadata cache
• Notices & progress
• Settings

TypeScript API reference

Use the generated TypeScript API reference when you need the current exported signatures, parameter descriptions, and source links for the supported plugin-author surface.

Language & editor extensions

If you extend syntax, file types, linting, or editor behavior, start here:

• Overview
• VS Code to Lapis mapping
• Lapis manifest contributions
• Editor views and associations
• Syntax and highlighting
• Language services
• CodeMirror extensions