Documentation attributions
Some public documentation pages are adapted from open documentation projects and rewritten for Lapis Notes.
Obsidian plugin development docs
Section titled “Obsidian plugin development docs”Developer documentation for plugin anatomy, lifecycle, editor access, events, manifest shape, publishing, and plugin CSS is adapted from Marcus Olsson’s archived Obsidian Plugin Developer Docs repository.
- Source: github.com/marcusolsson/obsidian-plugin-docs
- License: Apache License 2.0
- Changes: rewritten for the Lapis
Appfacade, community plugin host boundary, current manifest guidance, and first-party plugin CSS contract.
Visual Studio Code documentation
Section titled “Visual Studio Code documentation”User-interface documentation for command-driven workflows, sidebars, editor groups, shortcuts, and workspace layout is adapted from the Visual Studio Code Documentation repository.
- Source: github.com/microsoft/vscode-docs
- License: Creative Commons Attribution 3.0 United States
- Changes: rewritten for Lapis Notes, vaults, notes, sidebars, plugin views, and the current web/desktop runtime.
Developer documentation for language extensions, manifest contributions, and the VS Code-to-Lapis mapping draws on structure and terminology from the Visual Studio Code Extension API — Language Extensions Overview and related contribution-point reference pages.
- Source: code.visualstudio.com/api
- Changes: rewritten for Lapis CodeMirror/Lezer editing,
LanguageServiceProvider, andlapis.contributesmanifest metadata rather than TextMate grammars or VS Code extension hosts.
No Microsoft, Visual Studio Code, or Obsidian trademarks imply endorsement of Lapis Notes.