Content blocks and page structure
Understand links, compact social rows, media, maps, events and other blocks available in a page.
Last reviewed 24 July 2026A block should reduce the work a visitor must do. OrbitPage includes several formats because a destination, an event and a location need different amounts of context.
Choose the smallest format that explains the action.
Use a standard link when the label is enough. Use a media, event, map or information block when the visitor needs context before acting. Richer does not automatically mean clearer.
Every visible block counts toward the managed plan limit. Hidden blocks stay in the workspace but are not included in the public flow.
Separate primary actions from compact destinations.
A full link card can carry a title, description, media and destination. Compact links place social services or small destinations in a horizontal row near the profile, where their official icons are recognizable without adding another stack of cards.
For supported social services, OrbitPage can build the destination from a username or phone number. Always open the generated destination once before publishing.
Media and embeds should remain optional enhancements.
Images, video, music players and supported embeds can make the page more useful, but third-party providers control whether a specific item may be embedded. A clear fallback link remains important.
Maps use the public destination supplied by the user rather than a metered Google Maps API. Event blocks can include a date, countdown and action without requiring an external calendar.
Organize for a visitor arriving with no context.
Place compact social links below the profile, the primary action immediately after them, and time-sensitive content before evergreen destinations. Separators can introduce a group, but should not become headings for single cards.
Reorder blocks by the decision path rather than by the date they were created.
