Start with the schema
Use a modern schema header and one system block so the document has a clear root.
This guide keeps the same deep-blue presentation language as the main docs while focusing on staged learning: start small, add placements, then preview what your text produces.
WorldOrbit gets easier when you treat it as a sequence: declare a system, place a few objects, then layer presentation and events only after the core structure feels solid.
Use a modern schema header and one system block so the document has a clear root.
Introduce stars, planets, moons, and belts with simple placement fields before adding richer metadata.
Layer viewpoints, annotations, and event snapshots once the underlying atlas structure is stable.
Each example keeps the left side as source and the right side as rendered output so the DSL stays grounded in visible results.
schema 3.0 system Sol object star Sun object craft Scout free 5au
schema 3.0
system Iyath
title "Iyath System"
defaults
view orthographic
scale presentation
preset atlas-card
theme atlas
viewpoint inner
projection perspective
camera
azimuth 28
elevation 20
distance 5
group inner-system
label "Inner System"
object star Iyath
object planet Naar
orbit Iyath
semiMajor 1.18au
eccentricity 0.08
phase 42deg
atmosphere nitrogen-oxygen
groups inner-system
object moon Leth
orbit Naar
distance 384000km
phase 140deg
object structure Relay-One
at Naar:L4
kind relay
object craft Courier
free 9au
trajectory courier-transfer
trajectory courier-transfer
craft Courier
from DeepSpace
to Naar
maneuver departure
deltaV 1.8km/s
maneuver flyby
assist Iyath
around Iyath
periapsis 420000km
turnAngle 13deg
Edit the source, switch between 2D and 3D preview, and use this page as a lightweight practice surface before you move into Studio.
These are the most useful reminders for the first few documents you write.
It is easier to debug one star and one planet than a full atlas. Add bodies incrementally.
defaults and viewpoint are helpful, but they are not required for your first valid document.
Separate the orbital structure from presentation details. That mental split matches how WorldOrbit itself is built.
No. Many good documents begin with just a schema, a system, and a few objects.
When you want a stronger inspection loop, side panels, exports, and a dedicated editing shell beyond the simple docs playground.