Shared Documentation
This section contains guidance and reference material for the entire LongitudeOne Spatial ecosystem.
The Documentation contribution workflow explains how to write, validate, review and maintain documentation changes, including standards citations and the documentation Definition of Done.
The Portable Markdown publication contract defines the strict publication rules that keep generated HTML and Markdown semantically equivalent while remaining portable and independently usable.
The Spatial reference documentation architecture defines the Standards, Concepts and DBMS domains, their responsibilities, and their relationship to versioned library documentation.
The Markdown export example demonstrates content preserved in both published representations.
The Documentation migration rules define how collected sources retain their ownership and version context when converted into published pages, while the original migration corpus remains unchanged.
Using documentation assets shows how to add and reference shared images, diagrams, schemas, examples and downloads.
Generating library support timelines defines the shared JSON contract, Node.js renderer and deterministic SVG calendar rules used by library roadmaps.
The Shared assets publication contract defines supported formats, validation, the generated manifest and atomic publication.
Validating generated documentation explains the final publication gate, integrity manifests, reports and reproducibility checks.
HTML search indexing and SEO validation describes canonical URLs, alternate representation indexing, structured data and publication checks. The HTML SEO audit records the Story 39 assessment.