This repository uses Docusaurus to publish the documentation pages seen at docs.overturemaps.org
blog/: Entries for the Overture engineering blog available at docs.overturemaps.org/blogcommunity/: The community page that showcases Overture data being used in the wild.docs/: The main documentation pages available at docs.overturemaps.org/. The sidebar for these pages is manually curated in thesidebars.jsfile.release-blog/: Release notes for every Overture data release. The latest release is always available at https://docs.overturemaps.org/release/latest/- Notice there is no
schema referencefolder. See below.
The Overture schema repository github/overturemaps/schema maintains the official Overture schema and the documentation surrounding the actual schema reference pages. This is to ensure that the schema, documentation, and relevant examples are always in-sync.
The script fetch_schema.sh injects the contents of the schema's documentation into docs/schema/ and copies the schema YAMl files and examples to docs/_schema and docs/_examples, respectively. This script runs with every build.
Therefore, anything available at docs.overturemaps.org/schema (under the Schema Reference link in the header) comes from the Overture schema repository, not this repository. Any changes to schema will be overwritten on every build.
Docusaurus requires node. First, install the required packages:
npm installThen, start the local server:
npm startNow navigate to http://localhost:3000 to see the live preview.
npm start- Start the development servernpm run build- Build the production site (also shows locale/translation warnings and broken link checks)npm run serve- Serve the built site locallynpm run deploy- Deploy the sitenpm run clear- Clear the Docusaurus cachenpm run swizzle- Customize Docusaurus components by "ejecting" them for modificationnpm run write-translations- Generate translation files for internationalizationnpm run write-heading-ids- Auto-generate heading IDs for better linking