diff --git a/assets/events/2026-berlin/logo-square.jpg b/assets/events/2026-berlin/logo-square.jpg new file mode 100644 index 0000000000..711ec87788 Binary files /dev/null and b/assets/events/2026-berlin/logo-square.jpg differ diff --git a/assets/events/2026-berlin/logo-square.png b/assets/events/2026-berlin/logo-square.png new file mode 100644 index 0000000000..1fed191494 Binary files /dev/null and b/assets/events/2026-berlin/logo-square.png differ diff --git a/assets/events/2026-berlin/logo.png b/assets/events/2026-berlin/logo.png new file mode 100644 index 0000000000..fdb88485cb Binary files /dev/null and b/assets/events/2026-berlin/logo.png differ diff --git a/assets/events/2026-berlin/organizers/ralph-angenendt.png b/assets/events/2026-berlin/organizers/ralph-angenendt.png new file mode 100644 index 0000000000..5738a11069 Binary files /dev/null and b/assets/events/2026-berlin/organizers/ralph-angenendt.png differ diff --git a/content/events/2026-berlin/conduct-fr.md b/content/events/2026-berlin/conduct-fr.md new file mode 100644 index 0000000000..f9a56a25cc --- /dev/null +++ b/content/events/2026-berlin/conduct-fr.md @@ -0,0 +1,37 @@ ++++ +Title = "Conduct" +Type = "event" +Description = "Code de conduite devopsdays Berlin 2026" ++++ + +Tous les participants, conférenciers, sponsors et volontaires à devopsdays Berlin 2026 doivent accepter le code d'éthique et de déontologie, ou « code de conduite » suivant. Les organisateurs s’attacheront à faire respecter ce code durant l’événement. Nous attendons la coopération de chacun‧e pour assurer un environnement sain pour tous. + + +### La Version Rapide + +Notre conférence tient à être une expérience sans harcèlement pour tous, quel que soit votre sexe, votre identité sexuelle, votre âge, votre orientation sexuelle, votre handicap, votre apparence physique, votre poids, votre race, votre ethnie, votre religion (ou absence de religion), ou vos choix technologiques. + +Nous ne tolérons aucun harcèlement des participant‧e‧s à la conférence, sous quelque forme que ce soit, quelles qu’en soient les circonstances. Les expressions et les images à connotation sexuelle ne sont pas appropriées lors de l'événement. Ceci inclut les conférences, les ateliers, les soirées, Twitter et les autres médias en ligne. + +L'organisation s'engage à prendre des sanctions appropriées pour les personnes qui violent ces règles, jusqu'à l'exclusion sans remboursement et le recours légal. + + +### La Version Moins Rapide + +Le harcèlement comprend les commentaires à l'oral ou à l'écrit ainsi que les gestes offensants sur le sexe, l'identité sexuelle, l'âge, l'orientation sexuelle, le handicap, l'apparence physique, le poids, la race, l'ethnie, la religion, les choix technologiques, les images à connotation sexuelle dans des lieux publics, les intimidations délibérées, la traque, la poursuite, un harcèlement photographique ou vidéo, une suite d'interruptions des conférences et des autres sessions, un contact physique inapproprié et des avances sexuelles non désirées. sans son consentement ou à son insu. + +Les participant‧e‧s à qui il sera demandé d'arrêter tout comportement de harcèlement doivent arrêter immédiatement. + +Les sponsors sont aussi sujet à la politique anti-harcèlement. En particulier, les sponsors ne doivent pas utiliser d'images ou de supports à connotation sexuelle. Ils ne doivent pas non plus se livrer à des activités à connotation sexuelle. L'équipe du stand (y compris les bénévoles) ne doit pas utiliser de vêtements, uniformes ou costumes à connotation sexuelle. Ils ne doivent pas non plus créer un environnement sexualisé. + +Face à un comportement de harcèlement, l'équipe d'organisation de la conférence peut prendre toute action qui lui semble adéquate. Cela va d'un simple avertissement à l'exclusion sans remboursement de la conférence. + +Si vous vous sentez harcelé‧e, si vous pensez que quelqu'un se fait harceler, et plus généralement en cas de problème, merci de contacter immédiatement l’équipe d’organisation de l'événement. + +Les membres de l'organisation sont facilement identifiables grâce à un badge "STAFF". Les membres de l'organisation seront ravi‧e‧s d'aider les participants à contacter la sécurité de l'événement, ou les forces de l'ordre ; à fournir une escorte ainsi qu'à aider de toute autre façon les personnes victimes de harcèlement, pour garantir leur sécurité pendant la durée de l'événement. Nous apprécions votre participation à l'événement. + +Nous attendons de chacun‧e le respect de ces règles dans le bâtiment des conférences et des ateliers, ainsi que pendant les événements sociaux relatifs à la conférence. + + + +Le code de conduite devopsdays Berlin 2026 est basé sur [fr.confcodeofconduct.com](https://fr.confcodeofconduct.com)._ diff --git a/content/events/2026-berlin/conduct-pt-br.md b/content/events/2026-berlin/conduct-pt-br.md new file mode 100755 index 0000000000..cf364bbddc --- /dev/null +++ b/content/events/2026-berlin/conduct-pt-br.md @@ -0,0 +1,28 @@ ++++ +Title = "Conduta" +Type = "event" +Description = "Código de conduta do devopsdays Berlin 2026" ++++ + + +Participantes, palestrantes, representantes de empresas e pessoas voluntárias no devopsdays Berlin 2026 são requeridos a concordar com o seguinte código de conduta. A organização irá aplicar este código pelo evento. Nós esperamos cooperação de todas as pessoas participando para garantir um ambiente seguro para todas as pessoas. + +### A versão rápida + +Nossa conferência é dedicada a prover um uma experiência de conferência sem assédio para todos, independente de gênero, identidade de gênero e expressão, idade, orientação sexual, deficiência, aparência física, tamanho corporal, raça, etinia, religião (ou a falta dela) ou escolhas de tecnologias. Nós não toleramos assédio de participantes da conferência de qualquer forma. Linguagem e imagens sexuais não são apropriadas em nenhum local, incluindo palestras, workshops, festas, Twitter e outras mídias online. Violações destas regras poderão causar expulsão da conferência, sem reembolso a critério da equipe organizadora. + +### A versão não tão rápida + +Assédio inclui comentários verbais ofensivos relacionados a gênero, identidade de gênero e expressão, idade, orientação sexual, deficiência, aparência física, tamanho corporal, raça, etinia, religião (ou a falta dela) ou escolhas de tecnologias, imagens sexuais em espaços públicos, intimidação deliberada, stalking, perseguição, fotografias ou filmagens constrangedoras, interrupção contínua das apresentações ou outros eventos, contato físico inapropriado e atenção sexual indesejada. Participantes que receberem uma solicitação para interromper qualquer comportamento de assédio devem fazer isso imediatamente. + +As políticas antiassédio também se aplicam a representantes de empresas patrocinadoras. Em particular, não devem usar imagens, atividades ou outro material de cunho sexual. As equipes de estandes e tendas (incluindo pessoas voluntárias) não devem utilizar roupas, uniformes ou trajes sexualizados ou criar um ambiente sexualizado de quaisquer formas. + +Se alguém se envolver em comportamento de assédio, a equipe organizadora pode tomar qualquer ação que considerar apropriada, incluindo avisar a pessoa ofensora ou expulsá-la da conferência sem reembolso. + +Se você estiver sofrendo assédio, notar que alguém está sofrendo assédio, ou tenha alguma dúvida, por favor contate alguém da organização imediatamente. + +As pessoas da equipe da conferência podem ser identificadas por crachás distintos da organização. A organização estará disposta a contatar a segurança do hotel/local ou a polícia local, fornecer escolta ou ajudar pessoas que sofrerem assédio para que se sintam seguras durante a conferência. Nós valorizamos a sua participação. + +Esperamos que todas as pessoas participantes sigam estas regras em salas de apresentação e workshops da conferência, além de eventos sociais relacionados. + +_O código de conduta do devopsdays Berlin 2026 é baseado em [confcodeofconduct.com](https://confcodeofconduct.com/index-pt-br.html)._ diff --git a/content/events/2026-berlin/conduct.md b/content/events/2026-berlin/conduct.md new file mode 100644 index 0000000000..9b1f4cdcdf --- /dev/null +++ b/content/events/2026-berlin/conduct.md @@ -0,0 +1,28 @@ ++++ +Title = "Conduct" +Type = "event" +Description = "Code of conduct for devopsdays Berlin 2026" ++++ + + +All attendees, speakers, sponsors, and volunteers at devopsdays Berlin 2026 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 Berlin 2026 Code of Conduct is based on [confcodeofconduct.com](https://confcodeofconduct.com)._ diff --git a/content/events/2026-berlin/contact.md b/content/events/2026-berlin/contact.md new file mode 100644 index 0000000000..2b5009809b --- /dev/null +++ b/content/events/2026-berlin/contact.md @@ -0,0 +1,14 @@ ++++ +Title = "Contact" +Type = "event" +Description = "Contact information for devopsdays Berlin 2026" ++++ + +If you'd like to contact us by email: {{< email_organizers >}} + +**Our local team** + +{{< list_organizers >}} + + +{{< list_core >}} diff --git a/content/events/2026-berlin/location.md b/content/events/2026-berlin/location.md new file mode 100644 index 0000000000..647bf45301 --- /dev/null +++ b/content/events/2026-berlin/location.md @@ -0,0 +1,26 @@ ++++ +Title = "Location" +Type = "event" +Description = "Location for devopsdays Berlin 2026" ++++ + +The DevOpsDays Berlin 2026 conference will take place at the KINDL – Zentrum für zeitgenössische Kunst (KINDL – Centre for Contemporary Art) in Berlin Neukölln. The KINDL is located in a former brewery building, with a huge former Kesselhaus (kettle house) that is used for e.g. site specific art. + +The KINDL also hosts events of all sorts, and in 2026 you can be there, too. + +The industrial complex that is now the KINDL was built between 1926 and 1930 based on a design by architects Hans Claus and Richard Schepke in the style of Expressionism. The Sudhaus with its six giant copper vats—once the largest of their kind in Europe—was previously known as the Palace of Berlin Beer Culture. After its partial destruction in World War II, it was rebuilt in the early 1950s according to plans by the cinema architect Gerhard Fritsche, who also designed the Zoo Palast cinema in Berlin. The conversion of the site, now a protected historical monument, into a centre for contemporary art was the visionary idea of Salome Grisard and Burkhard Varnholt, who acquired the building complex in 2011 and had it carefully renovated. Thanks to the historically sensitive renovation work—for example, the foyer with an exterior stairway in exposed concrete and glass leading to the exhibition areas—the result is a modern venue that can be used in a variety of ways for presenting art, while preserving the industrial character of the building. + +https://www.kindl-berlin.com/institution + + +{{< event_map >}} + + +The whole KINDL area is wheelchair accessible, and handicapped-accessible +bathrooms are available. If you need parking, there are four disabled parking +spaces on the west side of the building. Hearing assistance is available at +events. + -- All information taken from https://www.kindl-berlin.com/visit + +If you have any questions regarding accessibility, don't hesitate to contact us: +{{< email_organizers >}} diff --git a/content/events/2026-berlin/propose.md b/content/events/2026-berlin/propose.md new file mode 100644 index 0000000000..0ec5d5d032 --- /dev/null +++ b/content/events/2026-berlin/propose.md @@ -0,0 +1,35 @@ ++++ +Title = "Propose" +Type = "event" +Description = "Propose a talk for devopsdays Berlin 2026" ++++ + {{< cfp_dates >}} + +
+ +There are three ways to propose a topic at devopsdays: +
    +
  1. A 30-minute talk presented during the conference, usually in the mornings.
    2. +
  2. An Ignite talk presented during the Ignite sessions (scheduling varies). These are 5 minutes slots with slides changing every 15 seconds (20 slides total).
    3. +
  3. 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 +
    +
  1. Type (presentation, panel discussion, ignite)
    2. +
  2. Proposal Title (can be changed later)
    3. +
  3. Description (several sentences explaining what attendees will learn)
    4. +
diff --git a/content/events/2026-berlin/registration.md b/content/events/2026-berlin/registration.md new file mode 100644 index 0000000000..6dcd5088fa --- /dev/null +++ b/content/events/2026-berlin/registration.md @@ -0,0 +1,11 @@ ++++ +Title = "Registration" +Type = "event" +Description = "Registration for devopsdays Berlin 2026" ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2026-berlin/sponsor.md b/content/events/2026-berlin/sponsor.md new file mode 100644 index 0000000000..95e688cfeb --- /dev/null +++ b/content/events/2026-berlin/sponsor.md @@ -0,0 +1,48 @@ ++++ +Title = "Sponsor" +Type = "event" +Description = "Sponsor devopsdays Berlin 2026" ++++ + +We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}]. + +
+ +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 have the opportunity to have short elevator pitches during the program and 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. +

+

+

+Platinum sponsors get a full table and Gold sponsors a shared table where they can interact with those interested to come visit during breaks. All attendees are welcome to propose any subject they want during the open spaces, but this is a community-focused conference, so heavy marketing will probably work against you when trying to make a good impression on the attendees. +

+

+The best thing to do is send engineers to interact with the experts at devopsdays on their own terms. +

+ +
+ +
+ + + + + + + + + + + + + + + + + + +
Packages
Silver
1500 EUR
Gold
3500 EUR
Platinum
6500 EUR
2 included tickets   
logo on event website   
logo on shared slide, rotating during breaks   
logo on all email communication   
logo on its own slide, rotating during breaks   
1 minute pitch to full audience   
2 additional tickets (4 in total)   
4 additional tickets (6 in total)   
shared table for swag   
booth/table space   
thank you tweet   
+
+
+

+There are also opportunities for exclusive special sponsorships. We'll have sponsors for various events with special privileges for the sponsors of these events. If you are interested in special sponsorships or have a creative idea about how you can support the event, send us an email {{< email_organizers >}}. +
+

diff --git a/content/events/2026-berlin/welcome.md b/content/events/2026-berlin/welcome.md new file mode 100644 index 0000000000..372163f39a --- /dev/null +++ b/content/events/2026-berlin/welcome.md @@ -0,0 +1,93 @@ ++++ +Title = "devopsdays Berlin 2026" +Type = "welcome" +aliases = ["/events/2026-berlin/"] +Description = "devopsdays Berlin 2026" ++++ + +
+
+ + Berlin Skyline by Fred3rik in Wikipedia licensed under CC BY-SA 3.0 + +
+
+ +
+ {{< event_logo >}} +
+ +
+
+ Dates +
+
+ {{< event_start >}} - {{< event_end >}} +
+
+ + + + + + + + + + + + +
+
+ Sponsors +
+
+ {{< event_link page="sponsor" text="Sponsor the conference!" >}} +
+
+ +
+
+ Contact +
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}} +
+
+ +{{< event_twitter >}} diff --git a/data/events/2026/berlin/main.yml b/data/events/2026/berlin/main.yml new file mode 100644 index 0000000000..24e34c422e --- /dev/null +++ b/data/events/2026/berlin/main.yml @@ -0,0 +1,128 @@ +name: "2026-berlin" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: "2026" # The year of the event. Make sure it is in quotes. +city: "Berlin" # The displayed city name of the event. Capitalize it. +event_twitter: "blndevops" # Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp +description: "Devopsdays is coming back to Berlin!" # Edit this to suit your preferences +ga_tracking_id: "" # If you have your own Google Analytics tracking ID, enter it here. Example: "UA-74738648-1" + +event_logo: "logo-square.png" +# sharing_image: "2022-sharing-logo-berlin.png" +masthead_background: "berlin-masthead.png" + +# All dates are in unquoted 2026-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 2026-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: 2026-09-29T00:00:00+02:00 # The start date of your event. Leave blank if you don't have a venue reserved yet. +enddate: 2026-09-30T00:00:00+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: # start accepting talk proposals. +cfp_date_end: # close your call for proposals. +cfp_date_announce: # inform proposers of status + +cfp_link: "" #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: # 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: # close registration. Leave blank if registration is not open yet. If you set "registration_date_start" you need a value here. + +registration_closed: "" #set this to true if you need to manually close registration before your registration end date +registration_link: "" # 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: "KINDL – Zentrum für zeitgenössische Kunst" # Defaults to city, but you can make it the venue name. +# +location_address: "Am Sudhaus 3, 12053 Berlin" #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/devopsdaysberlin/about/" # Change this to the url to your Linkedin group, company, or page. +# event_social_slack: "https://join.slack.com/t/devopsdays/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: "blndevops" # Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp +event_social_mastodon: "https://social.devopsdays.org/@berlin" # Change this to url to your mastodon page +# event_social_bsky: "https://bsky.app/profile/devopsdays.bsky.social" # Change this to url to your bluesky page +# event_social_youtube: "devopsdays" # Change this to the youtube channel handle for your event such as devopsdaysrox + + +# Social Share Buttons +# Optional: Specify which social share buttons to display on event pages. +# If not specified, defaults to all: ["email", "twitter", "facebook", "linkedin"] +# Valid values: "email", "twitter", "facebook", "linkedin" +# Example: social_shares: ["email", "linkedin"] # Only show email and LinkedIn share buttons +social_shares: # ["email", "twitter", "facebook", "linkedin"] + +nav_elements: # List of pages you want to show up in the navigation of your page. + # - name: propose + # - name: registration + # - name: program + - name: location + # - 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: "Bernd Erk" + twitter: "gethash" + employer: "NETWAYS" + - name: "Martin Alfke" + twitter: "tuxmea" + employer: "Example42" + - name: "Markus Neder" + twitter: "markusneder" + employer: "NETWAYS" + - name: "Norman Messtorff" + twitter: "nmesstorff" + github: "nmesstorff" + employer: "Deutsche Post IT Services" + website: "https://normes.org" + - name: "Ralph Angenendt" + mastodon: "https://toot.berlin/@der_mit_ph" + github: "range" + image: "ralph-angenendt.png" + - name: "Simon Hoenscheid" + twitter: "simonhoenscheid" + - name: "Travis Theune" + twitter: "tenminutesout" + - name: "Carlos Tadeu Panato Jr" + twitter: "comedordexis" + github: "cpanato" + employer: "Chainguard" + - name: "Verena Traub" + +organizer_email: "berlin@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: + # url: http://mysponsor.com/?campaign=me # Use this if you need to over-ride a sponsor URL. + - id: arresteddevops + level: community + +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: 10 + - id: silver + label: Silver + max: 0 # This is the same as omitting the max limit. + - id: bronze + label: Bronze + - id: community + label: Community diff --git a/static/_redirects b/static/_redirects index e700857ed5..a797366eb6 100644 --- a/static/_redirects +++ b/static/_redirects @@ -12,7 +12,7 @@ /belem/* /events/2019-belem/:splat 302 /belo-horizonte/* /events/2025-belo-horizonte/:splat 302 /bengaluru/* /events/2023-bengaluru/:splat 302 -/berlin/* /events/2022-berlin/:splat 302 +/berlin/* /events/2026-berlin/:splat 302 /birmingham-al/* /events/2024-birmingham-al/:splat 302 /birmingham-uk/* /events/2023-birmingham-uk/:splat 302 /bogota/* /events/2025-bogota/:splat 302 diff --git a/static/events/2026-berlin/berlin-masthead.png b/static/events/2026-berlin/berlin-masthead.png new file mode 100644 index 0000000000..5f556c2a4b Binary files /dev/null and b/static/events/2026-berlin/berlin-masthead.png differ