Editors, language services, and layout
Authoring Toolkits
Build serious .NET authoring tools from focused, reusable subsystems.
Explore source ↗Capability
Standalone HTML, Markdown, document, PDF, graph, split-layout, minimap, XAML, JavaScript, TypeScript, and debugger packages extract reusable tooling from the inspector workspace.
- 01
HTML, Markdown, document, and PDF surfaces
- 02
JavaScript and TypeScript language services
- 03
Node editor and split layouts
- 04
XAML, C#, V8, source-map, and WebAssembly tooling
How it composes
From intent
to working system.
Model
Purpose-built ASTs preserve document or language structure.
Engine
Layout, render, parse, or graph services remain UI-independent.
Control
Avalonia surfaces add selection, caret, navigation, and editing.
Workspace
Split, minimap, and language services compose full tools.
Quick start
Adopt this
capability.
Start with the primary module, then add the related packages only when the application needs those layers. Replace VERSION with the current NuGet version.
<markdown:MarkdownEditor Document="{Binding Document}" Selection="{Binding Selection}" />Modules in this capability
Use one layer.
Compose the rest.
Interactive Markdown editor canvas.
↗02Chrome.DevTools.Document.EditorRich document editor for office formats.
↗03Chrome.DevTools.Pdf.EditorInteractive PDF editor canvas built with PdfPig and SkiaSharp.
↗04Chrome.DevTools.Html.RendererLow-allocation HTML/CSS parsing, layout, and SkiaSharp rendering.
↗05Chrome.DevTools.Editor.NodesGeneric graph node editor.
↗06Chrome.DevTools.Editor.SplitsDynamic binary split layout.
↗07Xaml.CompilerLossless XAML AST and mutation engine.
↗Source of truth
Read the module beside the complete system.
The implementation, samples, issues, and release notes stay in the parent repository so module details remain connected to the product architecture.