TYPO3 websites for cultural events and festivals.
Bundle programmes. Give guests orientation.
We develop and support websites for cultural events, museum associations and festivals. They bring together programmes, venues and practical information and help guests to plan their visit.
Whether the participating institutions maintain their content themselves or the programme is imported from an event platform: we align the website with your processes and, for recurring events, also take the next edition into account.
Many programme items. One shared overview.
For a museum night, content is created in many institutions. For a festival, the programme may be planned centrally in an event platform. Times, places and programme items have to come together understandably on the website.
We clarify who maintains which content and how changes get onto the website. Depending on the starting point, we set up suitable input forms in TYPO3 or connect existing data sources. This avoids additional maintenance where information is already available in structured form.
The event date and the next edition in view.
We plan implementation based on the dates by which information, programme and ticket access must be available. We also take editorial preparation and short-notice changes into account.
For recurring events, we check which structures can be reused. We agree with you whether past programmes remain public, are archived internally or are replaced by new content.
We take the special requirements of public institutions into account in working with public-sector clients.
Functions for organisers and guests.
How we plan your event website.
It is not only the day of the event that counts: the start of ticket sales, the programme announcement and content maintenance also need a coordinated schedule.
Requirements and dates
We clarify who supplies and approves content, which systems are involved and when the individual areas need to be online. This results in the project plan.
Structure and functions
We plan programme data, navigation, filters and, where applicable, further visitor functions. For recurring events, we take the handling of later editions into account.
Implementation and testing
We implement the website in a test environment and accompany the agreed transfer or entry of the content. We check functions, display and accessibility to the intended extent. If load tests are required, we define their scope and conditions in advance.
Publication and further support
After approval, we publish the website. We agree support around the event as well as follow-up and preparation of a further edition to suit your needs.
Clear processes for the team. An overview for the guests.
Your website brings together the programme and the practical information about the event. Guests can find their way around, while it is clear to the participating editorial teams where content is maintained and changes are published.
For the next edition, the existing structures can be built upon. We agree which adjustments are necessary for this based on the new programme and your requirements.
Museum nights, festivals and event days.
Three event projects that we accompany technically.
Frequently asked questions
Questions from organisers.
Yes. We can set up separate access and suitable input forms for the participating institutions. We jointly define which content they may publish themselves and where central approval is required.
Not necessarily. We check which programme data the system provides via an interface or an export. If the required information is available, we can develop an automatic transfer. We take missing information and supplementary editorial content into account in planning.
We agree this with you. Past programmes can remain public as an archive or be backed up internally. For a new edition, we clearly separate current and earlier information and continue to use suitable structures.
We plan the technical environment based on the expected numbers of visits and the required functions. This includes, for example, caching and suitable hosting capacities. We agree additional load tests and support during the event as needed. Unrestricted availability cannot be guaranteed from this.
That depends on the sponsorship, the specific offering and the relevant regulations. Special rules apply to public bodies. For private organisers, online ticket sales, among other things, may fall under the BFSG; possible exceptions must also be taken into account.
Regardless of this, an accessible website helps more people use your offering. We support technical implementation and testing. This does not replace a binding legal classification.
Yes. We also implement event websites in several languages. We jointly define which content is translated and how the language versions are maintained. For connected systems, we also check which languages and translations are available there.
We define in advance where changes are entered and how they become visible on the website. With an interface, we take the possible update intervals into account. If necessary, we also plan an editorial route for short-notice announcements. We agree with you whether cancelled programme items are hidden or marked.
That depends on the scope, those involved, data sources and the state of the content. We are guided by the publication dates, for example for ticket sales and programme, and allow time for filling, coordination and testing. For a reliable estimate, we need an overview of your project.
The decisive factors are design, range of functions, programme maintenance and the connection of existing systems. Added to this, where applicable, are content transfer, language versions, special checks and support around the event. In the quote, we distinguish the services required from possible additions.
Are you planning an event website?
Tell us about the event, the most important dates and, if available, the system for your programme maintenance. Together we clarify which functions are needed and how your project can be implemented.