How to Publish an Experience to the Public

This guide shows you how to publish an Experience in Ligantic so that it's publicly accessible to end-users.

Prerequisites

• Access to a Space with the ADMIN role
• A Space configured for public access (see How to Configure a Space for Public Access)

Create the Experience

1. In Studio, open your Space.
2. Click the Experience link in the navigation or use the Create menu.

3. Fill in the required fields:

   • Name — the display name, for example Contact Form
   • Pathname — the URL slug, for example contact-form
4. Click Create Experience.

Result: You'll be redirected to the Experience designer.

Design the Content

Use the Experience designer to build your user interface:

1. Add blocks by dragging from the block palette
2. Configure each block's properties in the right panel
3. Changes are auto-saved (watch the save status indicator)

Wait for the save status to show Saved before publishing.

Configure the Pathname

The pathname determines the URL where your Experience is accessible.

1. In the Experience designer, locate the Pathname field in the settings
2. Enter a URL-friendly slug (lowercase, hyphens instead of spaces)
3. The pathname supports dynamic parameters using :paramName syntax
4. Optional segments can end with ?, and a catch-all * is allowed only at the end of the path
5. Dots, backslashes, and file-like probe paths such as admin.php are not supported

Example pathnames:

• contact → https://your-space.ligantic.app/contact
• products/:id → https://your-space.ligantic.app/products/123
• docs/:section? → https://your-space.ligantic.app/docs
• assets/* → https://your-space.ligantic.app/assets/images/logo

Publish the Experience

1. Ensure all changes are saved (save status shows Saved)
2. Click the Publish button in the top toolbar
3. Wait for confirmation that the Experience was published

Result: The edit state indicator will change to Published.

Note: You can continue editing after publishing. Edits create a new draft version that won't be visible until you publish again.

Grant Access via Space Role

For the Experience to be publicly accessible, your public Space Role must grant access to it.

1. Open Space Settings → Auth
2. Find the Space Role used by your Guest authentication strategy
3. Edit the role's Experience capabilities
4. Add read access for this Experience
5. If the Experience uses Schemas or triggers Flows, grant those permissions too
6. Save the role

Result: The Experience is publicly accessible at the URL shown below.

Access the Public URL

Your Experience is now accessible at:

https://<spaceName>.ligantic.app/<pathname>

Example: https://my-company.ligantic.app/contact-form

From the Experience Designer

• Click the Public link in the toolbar to open the public URL in a new tab
• Click the Cloud link to preview within Studio

Manage Published Experiences

Update a Published Experience

1. Open the Experience in the Experience designer
2. Make your changes
3. The edit state will show Draft (unpublished changes)
4. Click Publish to make changes live

Result: Your changes are live.

Version History

Each publish creates a new version. You can view version history in the Experience settings.

View All Experiences

Open Space Settings → Experiences to see all Experiences with their publish status.

Troubleshooting

Experience Not Accessible at Public URL

• Verify the Experience is published (edit state shows Published)
• Confirm the Space has a Guest authentication strategy configured
• Check that the Space Role grants read access to this Experience

Changes Not Appearing

• Ensure you've clicked Publish after making changes
• Clear your browser cache or try an incognito window
• Wait a few moments, then reload the page