Skip to content

Documents and components

A Lunar Paper document is a sequence of components arranged on a canvas. Each component holds its own content, properties, and behavior, so you build a structured report rather than one long text field.

Annotated overview of the Document Builder editor showing the three-column layout

Instead of writing everything in one text editor, you add blocks for specific jobs. A Heading carries a section title, a Paragraph carries body text, a Stakeholders table covers roles and influence, and a Functional Requirements matrix covers traceability.

The canvas shows each component as a card with a title, width indicator, and toolbar. You can reorder, duplicate, nest, and style components independently.

The component library groups 57 components into eight categories based on what they do:

  • Content covers basic writing and media blocks.
  • Layout covers Page Break and Section Break for page boundaries, paper size and orientation.
  • Reference covers tables of contents, glossaries, definitions, acronyms, key-value lists, and version history.
  • Requirements covers acceptance criteria, functional requirements, user stories, and interfaces.
  • Analysis covers stakeholders and system context.
  • Integration covers embedded dashboards, data hub tables, and flowcharts.
  • Math covers equations, matrices, theorems, algorithms, and proofs.
  • Science covers abstracts, citations, figures, methodologies, chemical equations, scientific graphs, and unit converters.

Every component has a Properties panel. Common properties include grid width, sequence numbering, nest level, whether to show the component title, custom title text, and linked artifacts. You can also override document typography for a single component.

Layout breaks have full-width markers and are excluded from title, nesting and numbering controls. A Section Break’s properties configure the layout of the following content. See Layout and page breaks.

A component’s Nest level determines where it sits in the outline and table of contents. A component at level 2 appears under the most recent level-1 heading. Use nest levels to build subsections without needing a heading component for every block.

Start adding blocks with Build content with components. Organize and navigate with the outline covers nest levels and ordering in a long document, and the Component library reference describes every component in one place.