diff --git a/assets/events/2027-zurich/logo-square.png b/assets/events/2027-zurich/logo-square.png
new file mode 100644
index 00000000000..23b570ba88b
Binary files /dev/null and b/assets/events/2027-zurich/logo-square.png differ
diff --git a/assets/events/2027-zurich/logo.png b/assets/events/2027-zurich/logo.png
new file mode 100644
index 00000000000..74e932637c9
Binary files /dev/null and b/assets/events/2027-zurich/logo.png differ
diff --git a/assets/events/2027-zurich/organizers/dirk-lehmann.jpg b/assets/events/2027-zurich/organizers/dirk-lehmann.jpg
new file mode 100644
index 00000000000..223be1938fb
Binary files /dev/null and b/assets/events/2027-zurich/organizers/dirk-lehmann.jpg differ
diff --git a/assets/events/2027-zurich/organizers/flavio-monigatti.jpg b/assets/events/2027-zurich/organizers/flavio-monigatti.jpg
new file mode 100644
index 00000000000..306593bcd20
Binary files /dev/null and b/assets/events/2027-zurich/organizers/flavio-monigatti.jpg differ
diff --git a/assets/events/2027-zurich/organizers/franziska-buehler.jpeg b/assets/events/2027-zurich/organizers/franziska-buehler.jpeg
new file mode 100644
index 00000000000..da4c90d5a92
Binary files /dev/null and b/assets/events/2027-zurich/organizers/franziska-buehler.jpeg differ
diff --git a/assets/events/2027-zurich/organizers/isabel-schacher.jpg b/assets/events/2027-zurich/organizers/isabel-schacher.jpg
new file mode 100644
index 00000000000..ea51caa2cde
Binary files /dev/null and b/assets/events/2027-zurich/organizers/isabel-schacher.jpg differ
diff --git a/assets/events/2027-zurich/organizers/jan-moser.jpeg b/assets/events/2027-zurich/organizers/jan-moser.jpeg
new file mode 100644
index 00000000000..1d354d6f97a
Binary files /dev/null and b/assets/events/2027-zurich/organizers/jan-moser.jpeg differ
diff --git a/assets/events/2027-zurich/organizers/martin-thalmann.jpg b/assets/events/2027-zurich/organizers/martin-thalmann.jpg
new file mode 100644
index 00000000000..b74132de9bb
Binary files /dev/null and b/assets/events/2027-zurich/organizers/martin-thalmann.jpg differ
diff --git a/assets/events/2027-zurich/organizers/nadine-broghammer.jpg b/assets/events/2027-zurich/organizers/nadine-broghammer.jpg
new file mode 100644
index 00000000000..2abe122afd0
Binary files /dev/null and b/assets/events/2027-zurich/organizers/nadine-broghammer.jpg differ
diff --git a/assets/events/2027-zurich/organizers/romano-roth.jpg b/assets/events/2027-zurich/organizers/romano-roth.jpg
new file mode 100644
index 00000000000..cb337413c9a
Binary files /dev/null and b/assets/events/2027-zurich/organizers/romano-roth.jpg differ
diff --git a/assets/events/2027-zurich/organizers/selina-reist.jpg b/assets/events/2027-zurich/organizers/selina-reist.jpg
new file mode 100644
index 00000000000..1ff0598ad23
Binary files /dev/null and b/assets/events/2027-zurich/organizers/selina-reist.jpg differ
diff --git a/assets/events/2027-zurich/organizers/tobias-weinmann.jpg b/assets/events/2027-zurich/organizers/tobias-weinmann.jpg
new file mode 100644
index 00000000000..50301e11ece
Binary files /dev/null and b/assets/events/2027-zurich/organizers/tobias-weinmann.jpg differ
diff --git a/assets/events/2027-zurich/organizers/zoltan-vitus.jpg b/assets/events/2027-zurich/organizers/zoltan-vitus.jpg
new file mode 100644
index 00000000000..3a55c69542c
Binary files /dev/null and b/assets/events/2027-zurich/organizers/zoltan-vitus.jpg differ
diff --git a/content/events/2027-zurich/conduct.md b/content/events/2027-zurich/conduct.md
new file mode 100644
index 00000000000..d1fae395e8e
--- /dev/null
+++ b/content/events/2027-zurich/conduct.md
@@ -0,0 +1,28 @@
++++
+Title = "Conduct"
+Type = "event"
+Description = "Code of conduct for devopsdays zurich 2027"
++++
+
+
+All attendees, speakers, sponsors, and volunteers at devopsdays zurich 2027 are required to agree with the following code of conduct. Organizers will enforce this code throughout the event. We are expecting cooperation from all participants to help ensure a safe environment for everybody.
+
+### The Quick Version
+
+Our conference is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion (or lack thereof), or technology choices. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks, workshops, parties, Twitter, and other online media. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
+
+### The Less Quick Version
+
+Harassment includes offensive verbal comments related to gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion, technology choices, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
+
+Sponsors are also subject to the anti-harassment policy. In particular, sponsors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
+
+If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
+
+Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
+
+We expect participants to follow these rules at conference and workshop venues and conference-related social events.
+
+_The devopsdays zurich 2027 Code of Conduct is based on [confcodeofconduct.com](https://confcodeofconduct.com)._
diff --git a/content/events/2027-zurich/contact.md b/content/events/2027-zurich/contact.md
new file mode 100644
index 00000000000..ae02d18f698
--- /dev/null
+++ b/content/events/2027-zurich/contact.md
@@ -0,0 +1,15 @@
++++
+Title = "Contact"
+Type = "event"
+Description = "Contact information for DevOpsDays Zurich 2027"
++++
+
+If you'd like to contact us by email: {{< email_organizers >}}
+
+**Our local team**
+
+{{< list_organizers >}}
+
+**The core devopsdays organizer group**
+
+{{< list_core >}}
diff --git a/content/events/2027-zurich/diversity.md b/content/events/2027-zurich/diversity.md
new file mode 100644
index 00000000000..7320a77ddca
--- /dev/null
+++ b/content/events/2027-zurich/diversity.md
@@ -0,0 +1,47 @@
++++
+Title = "Diversity"
+Type = "event"
+Description = "Diversity for devopsdays zurich 2027"
++++
+
+
+
+
+ At DevOpsDays Zürich we don’t want to be a tech-conference only — instead we want to be a conference focusing on knowledge, networking and a connecting atmospheric vibe, welcoming a range of backgrounds, experiences and opinions.
+
+
+ Wether you are a speaker or a participant, maybe something’s missing for you? Would you be happy to have some mentoring on your first conference talk? Would you need some assistance in getting to Winterthur? Would you need childcare to be at the conference? Whatever it is, please do not hesitate to contact us.
+
+
+ We might not have a solution in every case or right away – but you can be sure that we are passionate and eager to find one!
+ Here’s among others what we already thought of:
+
+
+
trying some sort of “diversity in tech”-stream or talk at the conference itself
+
have gender neutral toilets (if feasable with the location)
+
check the location with zugangsmonitor.ch
+
have reserved seating for people with mobility issues
+ The access monitor documents the accessibility of cultural institutions for people with a visual, mobility or hearing impairment. Here you can find the accessibility of the Alte Kaserne Winterthur.
+ Zugangs Monitor
+
+
+
+ We believe in promoting equal opportunities for diverse talents in the IT industry. DevOpsDays Zurich supports the empowering of refugees & migrants for an IT career with a partnership with powercoders.
+
+
+
+ We encourage girls to discover coding and explore a career in tech. DevOpsDays Zurich supports GirlsCodeToo, a non-profit organization, sparking talent and curiosity by introducing girls to software tools, different coding languages and processes that are used to build apps, games, websites, and robots.
+
+
+
+ We are committed for the integration of diverse perspectives in tech and innovation. DevOpsDays Zurich is proud to collaborate with Be Like Grace, a network dedicated to fostering inclusion and diversity in Bern's tech scene. By empowering women and embracing varied backgrounds, languages, and cultures, we support Be Like Grace's commitment to enriching workplace discussions, enhancing decision-making, and creating more enjoyable work environments. This partnership reflects our shared belief that diversity not only brings more excitement and fun to our daily work but also drives the creation of superior products and services.
+
diff --git a/content/events/2027-zurich/propose.md b/content/events/2027-zurich/propose.md
new file mode 100644
index 00000000000..de607efa79d
--- /dev/null
+++ b/content/events/2027-zurich/propose.md
@@ -0,0 +1,35 @@
++++
+Title = "Propose"
+Type = "event"
+Description = "Propose a talk for devopsdays zurich 2027"
++++
+ {{< cfp_dates >}}
+
+
+
+There are three ways to propose a topic at devopsdays:
+
+
A 30-minute talk presented during the conference, usually in the mornings.
+
An Ignite talk presented during the Ignite sessions (scheduling varies). These are 5 minutes slots with slides changing every 15 seconds (20 slides total).
+
Open Space: If you'd like to lead a group discussion during the attendee-suggested Open Space breakout sessions, it is not necessary to propose it ahead of time. Those topics are suggested in person at the conference. If you'd like to demo your product or service, you should sponsor the event and demo it at your table.
+
+
+
+
+Choosing talks is part art, part science; here are some factors we consider when trying to assemble the best possible program for our local audience:
+
+- _broad appeal_: How will your talk play out in a room of people with a variety of backgrounds? Technical deep dives need more levels to provide value for the whole room, some of whom might not use your specific tool.
+- _new local presenters_: You are the only one who can tell your story. We are very interested in the challenges and successes being experienced in our local area. We are happy to provide guidance/coaching for new speakers upon request.
+- _under-represented voices_: We want to hear all voices, including those that may speak less frequently at similar events. Whether you're in a field not typically thought of as a technology field, you're in a large, traditional organization, or you're the only person at your organization with your background, we are interested in your unique experience.
+- _original content_: We will consider talks that have already been presented elsewhere, but we prefer talks that the local area isn't likely to have already seen.
+- _no third-party submissions_: This is a small community-driven event, and speakers need to be directly engaged with the organizers and attendees. If a PR firm or your marketing department is proposing the talk, you've already shown that as a speaker you're distant from the process.
+- _no vendor pitches_: As much as we value vendors and sponsors, we are not going to accept a talk that appears to be a pitch for your product.
+
+
+
+How to submit a proposal: Send an email to [{{< email_organizers >}}] with the following information
+
+
Type (presentation, panel discussion, ignite)
+
Proposal Title (can be changed later)
+
Description (several sentences explaining what attendees will learn)
+If you have any questions please contact us at {{< email_organizers >}}.
+
diff --git a/content/events/2027-zurich/sponsor.md b/content/events/2027-zurich/sponsor.md
new file mode 100644
index 00000000000..58aa8b2b191
--- /dev/null
+++ b/content/events/2027-zurich/sponsor.md
@@ -0,0 +1,251 @@
++++
+Title = "Sponsor"
+Type = "event"
+Description = "Sponsor DevOpsDays Zurich 2027"
++++
+
+We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at zurich@devopsdays.org. With sponsoring this event you accept our {{< event_link page="conduct" text="Code of Conduct" >}} and the General Sponsorship Rules.
+
+We do not sell or bundle speaker spots as part of any Sponsoring activities with our conference. Do not ask for it. We don’t do it. No DevOpsDays conference does it. Never. Period.
+We encourage everyone, including Sponsor employees, to take part in our open Call for Proposals process. However, working (or any other relation) to a Sponsor does not result in preferences or disadvantages in our selection process.”
+
+We do not sell or distribute attendee information. Do not ask for it. We don’t do it. No DevOpsDays conference does it. Never. Period.
+Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers (e.g. via proposing OpenSpace topics). Any Sponsor is free to collect attendee information with mutual consensus at their booth.
+
+### Sponsoring packages
+
+
+
+
+
Gold
+
Silver
+
Bronze
+
Evening Event
+
Coffee
+
Meals
+
Snacks
+
+
+
Social Media & Web Sites
+
x
+
x
+
x
+
x
+
x
+
x
+
x
+
+
+
Logo in emails
+
x
+
x
+
x
+
x
+
x
+
x
+
x
+
+
+
Logo shown during event1
+
x
+
x
+
x
+
x
+
x
+
x
+
x
+
+
+
Booth (9sqm) main room2
+
x
+
+
+
+
+
+
+
+
+
Booth (9sqm) foyer/1st floor2
+
+
x
+
+
+
+
+
+
+
+
Sponsoring Pitches (1min)3
+
x
+
+
+
x
+
x
+
x
+
x
+
+
+
Sponsoring Bingo
+
x
+
x
+
+
+
+
+
+
+
+
Logo shown at Evening Event
+
+
+
+
x
+
+
+
+
+
+
Logo on A4 table displays @ lunch
+
+
+
+
+
+
x
+
+
+
+
Logo on Coffee Cups4
+
+
+
+
+
x
+
+
+
+
+
Logo on Snacks4,5
+
+
+
+
+
+
+
x
+
+
+
# Tickets included
+
4
+
4
+
1
+
2
+
2
+
2
+
2
+
+
+
# Available Packages
+
SOLD OUT
+
SOLD OUT
+
SOLD OUT
+
SOLD OUT
+
SOLD OUT
+
SOLD OUT
+
SOLD OUT
+
+
+
Price (CHF excl. 8.1% VAT)
+
8'000.-
+
5'000.-
+
750.-
+
4'000.-
+
4'000.-
+
4'000.-
+
4'000.-
+
+
+ 1 Company logo will be in slide rotation on video projectors during breaks
+ 2 Gold/Silver sponsors may choose their preferred booth location on first come, first serve basis
+ 3 Sponsor pitches take place on day 1 or 2 on main stage in front of full audience (exception "Evening event": pitch takes place at the Evening Event venue on day 1)
+ 4 Snacks an coffee are served during breaks on day 1 & 2 of the conference
+ 5 Snacks are included/provided by organizers/venue. Sponsor needs to send 1000 stickers (max. 5cm x 10cm) with company logo to organizers (costs are not included in the package)
+
+
+### Why DevOpsDays?
+
+DevOpsDays is a self-organizing conference for practitioners that depends on sponsorships. We do not have vendor booths, sell product presentations, or distribute attendee contact lists. Sponsors will get recognition on the website and social media before, during and after the event. Sponsors are encouraged to represent themselves by actively participating and engaging with the attendees as peers. Any attendee also has the opportunity to demo products/projects as part of an open space session.
+
+### Sponsoring future DevOpsDays
+
+Thanks for your interest in sponsoring our conference! In the last years our sponsorship packages got sold out very quick, as we sell them on a first-come, first-serve order.
+If you want to be informed, when we publish our sponsorship packages for the next conference, so that you are ahead of the crowd, please register yourself to our sponsor mailling list below:
+
+
+
+
+
+
+
+
+
diff --git a/data/events/2027/zurich/main.yml b/data/events/2027/zurich/main.yml
new file mode 100644
index 00000000000..cdbf066ceee
--- /dev/null
+++ b/data/events/2027/zurich/main.yml
@@ -0,0 +1,175 @@
+name: "2027-zurich" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
+year: "2027" # The year of the event. Make sure it is in quotes.
+city: "Zurich" # The displayed city name of the event. Capitalize it.
+event_twitter: "DevOpsZH" # Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp
+description: "Devopsdays is coming to Zurich!" # Edit this to suit your preferences
+ga_tracking_id: "UA-174260535-7" # If you have your own Google Analytics tracking ID, enter it here. Example: "UA-74738648-1"
+event_group: "Zürich"
+
+# All dates are in unquoted 2027-MM-DDTHH:MM:SS+TZ:TZ, like this:
+# variable: 2019-01-04T00:00:00+02:00
+# variable: 2019-01-05T23:59:59+02:00
+# Note: we allow 2027-MM-DD for backward compatibility, but it can lead to unexpected behaviors (like your event disappearing from the front page during your last day)
+
+startdate: 2027-04-14T00:00:00+02:00 # The start date of your event. Leave blank if you don't have a venue reserved yet.
+enddate: 2027-04-15T23:59:59+02:00 # The end date of your event. Leave blank if you don't have a venue reserved yet.
+
+# Leave CFP dates blank if you don't know yet, or set all three at once.
+#cfp_date_start: 2026-10-01T00:00:00+02:00 # start accepting talk proposals.
+#cfp_date_end: 2027-01-31T23:59:59+02:00 # close your call for proposals.
+#cfp_date_announce: 2027-02-28T00:00:00+02:00 # inform proposers of status
+
+#cfp_link: "https://sessionize.com/devopsdays-zurich-2026/" #if you have a custom link for submitting proposals, add it here. This will control the Propose menu item as well as the "Propose" button.
+
+#registration_date_start: 2027-01-04T00:00:00+02:00 # start accepting registration. Leave blank if registration is not open yet. This will make the "Register" button appear on your "Welcome" page.
+#registration_date_end: 2027-04-14T00:00:00+02:00 # close registration. Leave blank if registration is not open yet. If you set "registration_date_start" you need a value here.
+
+#registration_closed: "false" #set this to true if you need to manually close registration before your registration end date
+#registration_link: "https://ti.to/dod/dodzh2026" # If you have a custom registration link, enter it here. This will control the Registration menu item as well as the "Register" button.
+
+# Location
+#
+# coordinates: "" # No longer used
+
+location: "Alte Kaserne Winterthur" # Defaults to city, but you can make it the venue name.
+#
+location_address: "Technikumstrasse 8, 8400 Winterthur, Switzerland" #Optional - use the street address of your venue. This will show up on the welcome page if set. Also used by the event_map shortcode!
+
+# Optional - Social badges
+# These can be used in the body of any page via matching shortcodes. See sample: https://devopsdays.org/events/2025-denver/welcome/
+event_social_linkedin: "https://www.linkedin.com/company/devopsdays-zurich/" # Change this to the url to your Linkedin group, company, or page.
+# event_social_slack: "https://join.slack.com/t/DevOpsZH/custom_shared_invite_url" # Change this to your slack invite link.
+# event_social_listserv: "https://lists.devopsdays.org/subscription?custom_listserv_invite_url" # Change this to your mailing list subscription form url.
+event_social_twitter: "DevOpsZH" # Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp
+event_social_mastadon: "https://social.devopsdays.org/@zurich" # Change this to url to your mastadon page
+# event_social_bsky: "https://bsky.app/profile/DevOpsZH.bsky.social" # Change this to url to your bluesky page
+event_social_youtube: "DevOpsDaysZurich" # Change this to the youtube channel handle for your event such as devopsdaysrox
+# legacy
+# event_twitter: "DevOpsZH" # This will create a traditional "Follow" twitter button. Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp.
+
+nav_elements: # List of pages you want to show up in the navigation of your page.
+ # - name: propose
+ - name: location
+ # - name: registration
+ # - name: program
+ # - name: speakers
+ - name: sponsor
+ - name: contact
+ - name: conduct
+# - name: example
+# icon: "map-o" # This is a font-awesome icon that will display on small screens. Choose at http://fontawesome.io/icons/
+# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site
+
+
+
+# These are the same people you have on the mailing list and Slack channel.
+team_members:
+# Name is the only required field for team members.
+- name: "Martin Thalmann"
+ twitter: "martin_thalmann"
+ employer: "monum GmbH"
+ bio: "I’m a passionate DevOps Enthusiast who strongly believes in the power of this movement. As a DevOps and Agile Coach, I support companies in creating more value for their customers. My background as a software developer & project manager as well as my practical experience in different agile roles help me to understand the needs well, find pragmatic solutions and anchor agile principles sustainably. In addition, I am co-study director at the Lucerne University of Applied Sciences and Arts and co-host of the DevOps Meetup Zurich."
+ github: ""
+ facebook: ""
+ linkedin: "https://www.linkedin.com/in/martinthalmann/"
+ website: ""
+ image: "martin-thalmann.jpg"
+- name: "Dirk Lehmann"
+ twitter: "doergn"
+ employer: "SAP"
+ bio: "
Dirk is a DevOps evangelist and Continuous Delivery expert at SAP.
Since 2001 Dirk worked in various roles at SAP including Development and Operations.Together with his former team \"TwoGo by SAP\" he established the first Continuous Delivery implementation at SAP, delivering value daily to their customers.
Dirk is a frequent speaker at international conferences on DevOps and Continuous Delivery.
I'm a DevOps enthusiast and the Head of DevOps at Zühlke. My passion is helping companies bringing people, processes and technology together so that they can deliver continuously value to their customers.
Having worked as a developer, systems engineer and team lead in IT operations, the ideas and concepts behind DevOps are very close to my heart. As I am passionate about coding since my teenage years, I am fascinated by concepts like Infrastructure as Code, Social Coding, and cloud native technologies trying to get hands-on whenever possible. I enjoy lateral thinking and my basic premise is that we cannot solve our problems with the same thinking we used when we created them (Albert Einstein).
In my current role I dedicate all my energy to introducing and spreading DevOps principles and practices in the broader organization.
I am an enthusiast for everything visual:photography, movies and animations, pictograms, infofraphics, visual design, graphical recordings, UX-Design. I also like to combine these skills in crossfunctional teams to enable app development, transformation processes and last but not least communicate and teach DevOps practices in large federal organizations
"
+ linkedin: "https://www.linkedin.com/in/selina-reist-1b7704181/"
+ image: "selina-reist.jpg"
+- name: "Flavio Monigatti"
+ twitter: "monfla00"
+ employer: "Inspify Pte Ltd"
+ bio: "Flavio is a passionate advocate for DevOps and MLOps (DevOps for Machine Learning), bringing with him a dynamic enthusiasm for these transformative methodologies. With a rich background in engineering, Flavio is also deeply involved in the practical application of these principles, helping customers realize the benefits of how DevOps and MLOps revolutionizes the way we think about and execute software development and operations."
+ linkedin: "https://www.linkedin.com/in/flavio-monigatti-5065076/"
+ image: "flavio-monigatti.jpg"
+- name: "Nadine Broghammer"
+ twitter: ""
+ employer: "ERNI Schweiz AG"
+ bio: "Nadine Broghammer is an experienced delivery manager and agile coach. After completing her master’s degree in business administration and management at the University of Zurich, she continously broadend her knowledge and brings a wide range of expertise in requirements engineering, project and product management and as well as a trainer and coach in agile frameworks and delivery. Her focus industries are healthcare as well as banking/finance and transportation. With her direct collaboration style and accessible nature, she ensures a transparent information flow and target focus. Her passion is people relationships and the transformation of corporate practices and strategies."
+ github: ""
+ linkedin: "https://www.linkedin.com/in/nadinebroghammer"
+ image: "nadine-broghammer.jpg"
+- name: "Isabel Schacher"
+ bio: "
I'm all about exceptional user experiences, having a background in UX engineering, interaction design, and even game design – because software should be fun, right? Crafting inclusive interfaces in interdisciplinary teams, that work seamlessly and bring smiles to users - that's my jam! Beyond work, I'm a passionate saxophonist. I'm looking forward contributing my skills to the media team of this year's DevOpsDays, ensuring every visitor leaves with a smile.
Jan Moser works since many years in different software architecture positions for national and international companies. With a background in software engineering, he successfully planned, designed and helped implement solutions in various business fields such as defence, automotive, pharma or finance. Jan works at the moment as lead enterprise architect at TWINT and helps to simplify peoples daily payment processes.
Franziska loves to combine her favorite topics DevOps, IT security and open source software. And that's exactly what she can pursue as an security engineer at SBB! As a former speaker at the DevOpsDays Zurich, organizer of the ModSecurity CRS Meetup Bern and an enthusiastic OWASP member, Franziska also has the opportunity to share her passion with others. When she isn't disassembling highly optimized regexes or automating security, she enjoys spending time with her family.
"
+ image: "franziska-buehler.jpeg"
+ employer: "SBB CFF FFS"
+ github: "franbuehler"
+ twitter: "@bufrasch"
+ linkedin: "https://www.linkedin.com/in/franziska-buehler-bb037a163/"
+- name: "Zoltan Vitus"
+ twitter: "vituszoli2"
+ employer: "Federal Office of Information Technology"
+ bio: "Experienced agile coach, SAFe Program consultant with a demonstrated history of working in the information technology and services industry. Skilled in agile coaching and leadership, enterprise architecture management, portfolio management and IT strategy."
+ linkedin: "https://www.linkedin.com/in/zoltan-vitus-828abb/"
+ image: "zoltan-vitus.jpg"
+organizer_email: "zurich@devopsdays.org" # Put your organizer email address here
+
+# List all of your sponsors here along with what level of sponsorship they have.
+# Check data/sponsors/ to use sponsors already added by others.
+sponsors:
+
+sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
+
+# In this section, list the level of sponsorships and the label to use.
+# You may optionally include a "max" attribute to limit the number of sponsors per level. For
+# unlimited sponsors, omit the max attribute or set it to 0. If you want to prevent all
+# sponsorship for a specific level, it is best to remove the level.
+sponsor_levels:
+- id: gold
+ label: Gold
+ max: 3
+- id: silver
+ label: Silver
+ max: 3
+- id: event
+ label: Evening Event, Coffee, Meal
+ max: 4
+- id: bronze
+ label: Bronze
+ max: 0
+- id: community
+ label: Community
+ max: 0
+- id: partner
+ label: Partner
+ max: 0
diff --git a/static/_redirects b/static/_redirects
index e898de8e96f..d8159fb187b 100644
--- a/static/_redirects
+++ b/static/_redirects
@@ -127,7 +127,7 @@
/warsaw/* /events/2025-warsaw/:splat 302
/washington-dc/* /events/2025-washington-dc/:splat 302
/zaragoza/* /events/2020-zaragoza/:splat 302
-/zurich/* /events/2026-zurich/:splat 302
+/zurich/* /events/2027-zurich/:splat 302
/events/2024-ghent/* /events/2024-antwerp/:splat 302!
/events/2009-ghent/* http://legacy.devopsdays.org/events/2009-ghent/:splat 301!
/events/2010* http://legacy.devopsdays.org/events/2010:splat 301!
+ Contact us!
+ 
+ 
+ 
+ 
+