Content blocks and page structure

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.

Use recognizable services as actions, players and embeds.

OrbitPage supports dedicated content for Instagram, Facebook, YouTube, WhatsApp and TikTok. Music and media options include Spotify, Apple Music, Deezer, SoundCloud, Mixcloud, Vimeo, Loom and Giphy. Google Calendar, Calendly, Typeform and Google Forms cover booking and response collection, while GitHub can point visitors to a profile or project.

Booking and form blocks support Google Calendar, Calendly, Typeform and Google Forms destinations. The editor normalizes supported URLs and keeps a direct fallback action because each external provider controls whether an individual item may be embedded.

• Use compact icons for profiles people already recognize.
• Use a player or embed when the content itself belongs on the page.
• Keep a clear external action when a provider blocks embedded playback.

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.

Map blocks use the destination supplied by the user without requiring a paid map integration. Event blocks can include a date, countdown and action without requiring an external calendar.

Move from attention to the next useful action.

A restaurant or bar can publish a structured menu with categories, subsections, prices and availability. A venue can add events and countdowns. A professional can connect a booking flow or form without turning the page into a full website.

The managed Shop can present digital products and services and send buyers through a connected payment flow. Use Shop only when the page has a clear offer; a catalog without a focused audience adds noise.

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.