Write¶
Zensical Studio works inside modern IDEs and code editors such as Visual Studio Code (support for other editors will be added soon). It understands Python Markdown and its extensions, the same authoring language documented in Zensical's authoring guide. That guide is the complete reference for syntax. The pages in this section show you how Zensical Studio helps you write and maintain content in your project.
CommonMark and components
In the medium-term, we are going to introduce support for CommonMark, with a component model as an alternative to Markdown extensions. See our roadmap for more information.
Start with the basics¶
These six pages describe some basics of working with Zensical Studio in Visual Studio CodeCursorZedJetBrains IDEs:
| Basic task | Page |
|---|---|
| See Markdown structure as you type | Markdown highlighting |
| Find your way around a project | Finding your way around a project |
| Keep Markdown structure consistent | Formatting |
| Catch structural and accessibility problems | Linting |
| Keep links intact when you reorganize files | Moving and renaming files |
| See the rendered result beside your source | Live preview |
Two more things are woven into every page rather than having one of their own:
-
DiagnosticDiagnosticDiagnosticInspections are inline messages about something that needs attention. A diagnosticdiagnosticdiagnosticinspection usually appears as an underline in the Markdown source and as an item in the Problems panelProblems panelDiagnostics panelProblems tool window, so you can fix a problem immediately instead of waiting for a QA process to flag it.
-
Completions suggest what you can insert next: page links and anchors, definition labels, snippet paths, or emoji and icon shortcodes. Suggestions often appear automatically; if not, use Ctrl+Space. Zensical Studio also closes common Markdown pairs as you type (an opening
[or`gets its closing counterpart), and selecting a completion fills in a missing closing],), or:for you.
Workflows that cut across features¶
Some tasks are bigger than one Markdown construct. The workflow pages show how common end-to-end edits are handled in Zensical Studio when they span links, headings, reusable content, formatting, and preview. You can find these guides in the Workflows section.
| Workflow | Page |
|---|---|
| Rename or move a page without breaking links | Keep links valid while editing |
| Keep an external link working after a reword | Keep your content externally addressable |
| Reuse shared content without losing context | Reuse content |
| Normalize structural markup | Auto-format Markdown |
| Catch broken links and definitions before you publish | Catch and repair problems |
| Preview each documentation variant as you write | Preview documentation variants |
| Keep navigation paths correct as pages move | Define navigation |
If something doesn't behave as this section describes, see troubleshooting.