Neorg .norg format versioning: What stability can users expect for documents written today?
18K reputation · 06 Oct 2025, 15:45 UTC
The .norg markup format is central to Neorg, but its specification remains under active development. Documents written today may rely on syntax that shifts between plugin releases, especially as Tree-sitter grammars and concealer rendering evolve in tandem.
This raises an unresolved decision: how should Neorg balance format innovation with backward compatibility? Users need to know whether a .norg file created now will render correctly in a year, or whether breaking changes are anticipated. The plugin's modular design (e.g., core.concealer) and reliance on matching parser versions add layers of uncertainty.
Specifically, is there a planned versioned specification for .norg, and how are breaking changes communicated? What migration path exists for existing documents when syntax semantics change? And does the concealer's rendering behavior depend on format stability, or is it designed to tolerate spec drift?