Layout Pattern
Timeline
Show events or milestones in chronological order. Label each item with a date or stage and a concise description.
How to Use It
Show events or milestones in chronological order. Label each item with a date or stage and a concise description.
Preview + source
Explore this layout
Show ordered milestones and their timing; give each event a distinct label.
All people, quotations and business figures in these examples are illustrative.
This prepared preview and the OPF describe the same example. Region outlines show measured allocation; toggling them does not change the slide.
Inspect compact default-catalog references. Your host must register the matching catalog; source identifies it without fetching over the network. Copy always includes complete embedded records.
{5 keys
"design": {1 key
"slides": [1 item
{4 keys
"blocks": [2 items
{2 keys
"timeline": {1 key
"events": [3 items
{2 keys
{2 keys
{2 keys
{2 keys
"catalogs": {1 key
"default": {1 key
Regions, in reading order
This layout is one list of 3 regions, declared once. The list runs as a column; a split nests a list that runs the other way. Each size is a share of its parent’s width (row) or height (column).
Schematic of the list: each box is drawn in proportion to its size; an auto entry gets a fixed band. Dashed boxes are heading regions.
Column, stacked, top to bottom. No anchor is written on the layout: body regions start at the top unless they set their own.
- 1titleauto
auto, the height the content needs
Heading region: holds the slide’s title, with its tag and subtitle. It takes a size and no content rules.
- 2timeline100%
size 1: 100% of what the auto entries leave
- Accepts
- timeline
- Role
- primary
- Flow
- none, up to 1 block
- Anchor
- top (default)
- 3notesauto
auto, the height the content needs
- Accepts
- textlistmetric
- Role
- supporting
- Flow
- auto, up to 6 blocks
- Anchor
- top (default)
Layout structure and reference fields
How automatic composition differs
Try dynamic composition
Explore how a text slide reflows as you change its content and shape. These examples use OPF’s shared composition rules; the copied document includes your choices.
All sample text fits within its content boxes.
View the complete OPF example
{
"$schema": "https://openpresentation.org/schema/opf/v1",
"name": "Dynamic composition example",
"design": {
"dimensions": {
"widthInches": 13.333333333333334,
"heightInches": 7.5
}
},
"slides": [
{
"title": "Let the content find its space",
"composition": {
"mode": "auto"
},
"blocks": [
{
"text": "Start with the decision. State what the audience should understand or do."
},
{
"text": "Show the evidence. Give each supporting idea enough space to be read."
},
{
"text": "Make the next step clear. Keep the action specific and easy to remember."
}
]
}
]
}Composition rules and examples as JSON · Pagination rules and example JSON
Related Layouts
Similar OPF layout slugs with matching content types, spatial patterns, or presentation use cases.
Groups Of Items
Process
Explain an ordered sequence of steps. Give each step a clear action and enough context to understand the transition.
/layouts/process
Groups Of Items
Comparison
Compare alternatives using parallel information. Keep the same criteria and level of detail for every option.
/layouts/comparison
Groups Of Items
Pillars
Show the main themes or principles behind an idea. Give each item a short heading and a comparable amount of detail.
/layouts/pillars
Text
Two columns
Place two bodies of content beside each other. Use it for paired explanations or an argument with supporting evidence. Pictures remain visible in full unless an explicit fit overrides the layout default.
/layouts/two-column
Visuals
Chart beside
Pair a chart with an explanation of its result. Keep the text focused on the pattern or decision supported by the data.
/layouts/chart-beside
Groups Of Items
FAQ
Answer the questions an audience is likely to ask. Pair each question with a direct answer and group related questions together.
/layouts/faq