This page is for anyone who maintains a museum website and wants to offer the go~mus booking directly on it, without a shop of their own and without deep development. If you run a CMS like Typo3 or WordPress, or your own system, this is enough to get going.
First things first. Each bundle is built for your venue and ships with its own documentation, tailored to your instance. That is where your concrete bundle address, your ticket groups and your event categories live. This page explains the basic mechanics that are the same for every bundle. To see it in action, there is a live demo.
What the bundle is
The bundle is the complete go~mus booking as an embedded window. Date, tickets, cart, coupon redemption and guest checkout all run inside your page, styled in your brand. Technically it is a single script that renders the booking in an encapsulated area (shadow DOM) without touching your styles. No iframe, no second CMS.
Adding it: one script and one link
Two lines are enough. Load the script once per page, ideally before </body>, and place a trigger:
<script src="https://<your-bundle>.gomus.de/embed.js" defer></script>
<a href="https://<your-shop>" data-gomus-embed>Book tickets</a>The click opens the booking as an overlay. The href is the fallback without JavaScript and leads into the full shop. Your concrete bundle address is in your delivered docs.
Overlay or inline
Two presentations, the same booking:
| Presentation | Trigger | When it fits |
|---|---|---|
| Overlay (default) | Button or link with data-gomus-embed | The booking should open over the page, narrow as a drawer or wide as a dialog |
| Inline | Container <div data-gomus-embed-inline></div> | The booking should sit fixed in a page, e.g. on a dedicated tickets page |
You can use both together on one page.
Which booking opens
By default the bundle opens ticket sales. Attributes let you target a specific entry point:
data-gomus-flow="tickets"for tickets (default), optionally a specific group viadata-gomus-ticket-groupdata-gomus-flow="events"for public tours and events, optionally a category viadata-gomus-event-category
Which group and category numbers your venue has is in your docs. Several triggers on one page are allowed, e.g. one button each for day tickets, time slots and tours.
Language
The booking window follows the language of your page. The order:
1. data-gomus-locale directly on the trigger or container
2. the ?gomus-locale= parameter in the URL
3. the lang attribute of your <html> tag
4. otherwise the default language (de)
Available are the languages your venue maintains, usually de and en. Others fall back to the default language.
In your brand
Colours and corner radius come from CSS variables that work across the shadow boundary:
--gomus-accent: #0a7d61;
--gomus-accent-strong: #04342c;
--gomus-bg: #ffffff;
--gomus-text: #1c1917;
--gomus-header-bg: #04342c;
--gomus-radius: 6px;For finer adjustments, named areas are addressable via ::part(): backdrop, panel, header, close, content, footer, cta. Even more control over the look comes from the web components, if you assemble individual building blocks yourself.
What else to keep in mind
- Content security policy. If your page sets a CSP, the bundle address has to be allow-listed for script, styles, fonts and API calls. The required entries are in your docs.
- Guest checkout. The bundle sells deliberately lean, without customer accounts. If you need accounts, order history and dedicated SEO pages for tickets, use the standalone shop.
- Updates. The bundle address stays stable. We deliver updates to the same URL automatically, you do not have to follow up.
Successor to the booking widgets
The bundle is the more modern, more flexible evolution of the iframe widgets. For booking individual seats and groups, we plan to replace the existing booking widget with the bundle in coming releases: no more iframe, just a script tag, with theming via CSS variables and overlay and inline from a single source. For new integrations the bundle is therefore already the recommended choice.
Related pages
- go~mus + shop for the three routes to ticket sales at a glance
- Live demo for the bundle as an overlay and inline to try out
- Widgets for the iframe variant the bundle will replace over time
- Web components for individual building blocks in a deep integration
- Website integration for calendar, requests and direct booking around the booking