A public page begins with the guest's question
An organizer works with schedules, capacities, sales modes and operational states. A guest usually arrives with a shorter set of questions: What is happening, where is it, when should I be there and what do I need to do next? The redesigned Event experience gives those answers a stronger visual order. Date, location, organizer context and admission action remain close together, while secondary detail supports the decision instead of competing with it.
The same principle shapes the Venue experience. A managed Venue can introduce its public identity and present the published Events that belong there, giving recurring operations a stable destination rather than reducing every visit to an isolated listing. The page does not invent an Event calendar from private planning data. Only public resources that satisfy the existing publication rules can appear, and an archived or unpublished Venue does not remain publicly available merely because it once had a URL.
Managed Venues and one-off locations share one public standard
Many Event portfolios mix permanent locations with temporary ones. A club night may use a saved, managed Venue whose address and public profile are reused across Events. A pop-up, festival stage or partner location may belong only to one Event. Public Pages V2 supports both models: a managed-Venue Event can resolve beneath its Venue, while a published one-off Event has its own public Event address and carries the location facts stored for that Event.
That distinction remains meaningful inside the product. A one-off location is not silently promoted into a managed Venue, and a public page does not require a Venue foreign key in order to describe a legitimate Event. Conversely, managed-Venue pages retain their relationship to the Venue and its published schedule. Guests receive a coherent experience across both cases, while organizers keep the data model that matches how the operation is actually run.
Ticketing states say exactly who operates the sale
The public Event action now follows the Event's explicit ticketing mode. With NOCTRA Ticketing, the page can present the native ticket selection and continue into the NOCTRA-operated purchase path when sale inventory and readiness allow it. With External Ticketing, the page names the separately operated route and sends the guest to the organizer's configured HTTPS destination. With No paid tickets, it does not manufacture a checkout or imply that a paid offer exists.
These are presentation states, not a second source of ticketing truth. The public page cannot turn an external Event into a native sale, bypass payment readiness or publish tickets that the protected ticketing workflow does not make sellable. Likewise, No paid tickets does not erase Guestlist, Door or other admission operations; it states only that the Event is not offering paid tickets through this public surface. The page explains the operational fact already retained by the Event rather than guessing from a link or revenue field.
Designed for the moment a guest actually opens it
Public Event traffic is naturally mobile. Links travel through messages, social posts and search results, often while the guest is already moving between apps. V2 treats the small screen as the primary reading context: the essential Event facts appear early, actions remain easy to reach and the ticketing decision is not buried below internal product language. A focused mobile action can keep the relevant next step available without obscuring the content that helps a guest decide.
The visual system now extends across Event and Venue pages, including resilient cover treatments when an organizer has not supplied a suitable image. Guest-facing navigation and the public footer keep the page connected to NOCTRA without exposing dashboard controls. The result is intentionally different from an internal Event record: it is a public, accessible explanation of a published operation, not a reduced copy of the workspace interface.
Search and sharing reflect the published resource
Each eligible page now emits the signals needed to describe itself consistently. Canonical metadata identifies the authoritative public URL. English and German hreflang alternatives, together with x-default, describe the available localized views. Open Graph and social metadata support shared previews, while dedicated imagery provides a dependable visual even when the underlying Event or Venue media is limited. Event and Venue JSON-LD use the corresponding structured-data types instead of a generic marketing description.
Discovery follows publication authority. NOCTRA's sitemap resolver includes eligible published Venues and Events, including supported one-off Events, and the public robots policy no longer blocks those routes as a class. Search engines still decide whether and when to crawl or index a page; NOCTRA does not claim guaranteed rankings or immediate inclusion. What the product now provides is the truthful prerequisite: a stable, indexable page whose metadata, structured data and visible content agree about the resource being presented.
Publication remains a deliberate boundary
A better public experience is valuable only if private or incomplete work remains private. V2 continues to resolve public data through the existing publication authority. Draft, archived, unpublished or otherwise ineligible resources fail closed rather than falling back to a partial page. Event ownership and Venue relationships are checked by the authoritative resolvers, so a public URL cannot be used to cross from one Workspace's resource into another Workspace's presentation.
This release changes the quality and discoverability of pages that organizers have chosen and are eligible to publish. It does not change checkout formation, payment, tax, reservation or ticket-delivery authority, and it does not claim customer adoption that has not been measured. Public Pages V2 is a product foundation: clearer for guests, more expressive for organizers and more legible to search and sharing systems while retaining the boundaries the operation depends on.