diff --git a/assets/events/2026-belem/logo.png b/assets/events/2026-belem/logo.png new file mode 100644 index 0000000000..a1a6a2481c Binary files /dev/null and b/assets/events/2026-belem/logo.png differ diff --git a/assets/events/2026-belem/organizers/fabio-figueiredo.jpg b/assets/events/2026-belem/organizers/fabio-figueiredo.jpg new file mode 100644 index 0000000000..1ca55311e3 Binary files /dev/null and b/assets/events/2026-belem/organizers/fabio-figueiredo.jpg differ diff --git a/assets/events/2026-belem/organizers/iago.jpg b/assets/events/2026-belem/organizers/iago.jpg new file mode 100644 index 0000000000..7c40539d5e Binary files /dev/null and b/assets/events/2026-belem/organizers/iago.jpg differ diff --git a/assets/events/2026-belem/organizers/paulo-igor.jpg b/assets/events/2026-belem/organizers/paulo-igor.jpg new file mode 100644 index 0000000000..7183eaea92 Binary files /dev/null and b/assets/events/2026-belem/organizers/paulo-igor.jpg differ diff --git a/assets/events/2026-belem/organizers/ricardo-casseb.jpg b/assets/events/2026-belem/organizers/ricardo-casseb.jpg new file mode 100644 index 0000000000..b590b47913 Binary files /dev/null and b/assets/events/2026-belem/organizers/ricardo-casseb.jpg differ diff --git a/assets/events/2026-belem/organizers/ryan.jpg b/assets/events/2026-belem/organizers/ryan.jpg new file mode 100644 index 0000000000..1a610309a8 Binary files /dev/null and b/assets/events/2026-belem/organizers/ryan.jpg differ diff --git a/assets/events/2026-belem/organizers/thalyson.jpeg b/assets/events/2026-belem/organizers/thalyson.jpeg new file mode 100644 index 0000000000..d2d22b5f8a Binary files /dev/null and b/assets/events/2026-belem/organizers/thalyson.jpeg differ diff --git a/assets/events/2026-belem/organizers/tiago-danin.jpeg b/assets/events/2026-belem/organizers/tiago-danin.jpeg new file mode 100644 index 0000000000..be25f86338 Binary files /dev/null and b/assets/events/2026-belem/organizers/tiago-danin.jpeg differ diff --git a/content/events/2026-belem/conduct-fr.md b/content/events/2026-belem/conduct-fr.md new file mode 100644 index 0000000000..176ca9a4ef --- /dev/null +++ b/content/events/2026-belem/conduct-fr.md @@ -0,0 +1,37 @@ ++++ +Title = "Conduct" +Type = "event" +Description = "Code de conduite devopsdays Belém 2026" ++++ + +Tous les participants, conférenciers, sponsors et volontaires à devopsdays Belém 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 Belém 2026 est basé sur [fr.confcodeofconduct.com](https://fr.confcodeofconduct.com)._ diff --git a/content/events/2026-belem/conduct-pt-br.md b/content/events/2026-belem/conduct-pt-br.md new file mode 100644 index 0000000000..76c5bd0f3f --- /dev/null +++ b/content/events/2026-belem/conduct-pt-br.md @@ -0,0 +1,57 @@ ++++ +Title = "Conduta" +Type = "event" +Description = "Código de conduta do DevOpsDays Belém 2026" ++++ + +## Código de Conduta — DevOpsDays Belém 2026 + +### Nosso compromisso e escopo + +Nosso objetivo é garantir que o DevOpsDays Belém seja um espaço seguro e inclusivo para todas as pessoas. Buscamos promover um ambiente de respeito mútuo, colaboração e crescimento profissional. + +Este Código de Conduta se aplica a todas as pessoas envolvidas no evento, incluindo participantes, organização, palestrantes, representantes de empresas patrocinadoras e pessoas voluntárias, em todas as atividades e espaços relacionados ao evento. + +### Respeito e inclusão + +Esperamos que todas as pessoas tratem umas às outras com respeito, dignidade e cortesia. Estamos comprometidos com um ambiente livre de discriminação, independentemente de gênero, identidade ou expressão de gênero, orientação sexual, raça, etnia, idade, religião, deficiência, aparência física, condição socioeconômica ou escolhas tecnológicas. + +### Comportamentos esperados + +Encorajamos uma participação ativa e respeitosa, promovendo a saúde e a longevidade da nossa comunidade. Esperamos que todas as pessoas participantes: + +- usem linguagem acolhedora e inclusiva; +- respeitem diferentes pontos de vista e experiências; +- aceitem críticas construtivas de forma respeitosa; +- priorizem o que é melhor para a comunidade; +- demonstrem empatia com outras pessoas. + +### Comportamentos inaceitáveis + +Não serão tolerados assédio, intimidação, linguagem desrespeitosa ou qualquer forma de discriminação e humilhação. Isso inclui: + +- comentários ofensivos, depreciativos ou preconceituosos; +- ataques pessoais, bullying, xingamentos ou assédio público ou privado; +- uso inadequado de nudez, imagens sexuais ou representações de violência; +- intimidação deliberada, perseguição ou importunação; +- fotografar ou gravar alguém de modo abusivo; +- perturbar repetidamente apresentações, conversas ou outras atividades; +- contato físico inadequado ou atenção sexual indesejada; +- publicar informações privadas de terceiros sem permissão explícita; +- outras condutas que possam ser razoavelmente consideradas inadequadas em um ambiente profissional. + +### Consequências + +Comportamentos inaceitáveis levarão a ações corretivas consideradas apropriadas pela organização, incluindo advertência ou expulsão do evento, sem reembolso. + +### Denúncia + +Se você testemunhar ou sofrer algum comportamento inaceitável, reporte imediatamente a uma pessoa da equipe do evento. A organização está disponível para ajudar e buscar garantir sua segurança e conforto. + +### Responsabilidades + +Todas as pessoas participantes são responsáveis por seguir este Código de Conduta e contribuir para um ambiente positivo, seguro e enriquecedor. + +### Apoio e assistência + +A equipe estará disponível para oferecer apoio e assistência durante o evento. Contamos com a colaboração de todas as pessoas para manter o DevOpsDays Belém acolhedor e inclusivo. diff --git a/content/events/2026-belem/conduct.md b/content/events/2026-belem/conduct.md new file mode 100644 index 0000000000..05ef6ae340 --- /dev/null +++ b/content/events/2026-belem/conduct.md @@ -0,0 +1,28 @@ ++++ +Title = "Conduct" +Type = "event" +Description = "Code of conduct for devopsdays Belém 2026" ++++ + + +All attendees, speakers, sponsors, and volunteers at devopsdays Belém 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 Belém 2026 Code of Conduct is based on [confcodeofconduct.com](https://confcodeofconduct.com)._ diff --git a/content/events/2026-belem/contact.md b/content/events/2026-belem/contact.md new file mode 100644 index 0000000000..78a4d4d742 --- /dev/null +++ b/content/events/2026-belem/contact.md @@ -0,0 +1,14 @@ ++++ +Title = "Contato" +Type = "event" +Description = "Informações de contato do devopsdays Belém 2026" ++++ + +Se quiser entrar em contato conosco, envie um e-mail para {{< email_organizers >}}. + +**Nossa equipe local** + +{{< list_organizers >}} + + +{{< list_core >}} diff --git a/content/events/2026-belem/location.md b/content/events/2026-belem/location.md new file mode 100644 index 0000000000..99f13f8254 --- /dev/null +++ b/content/events/2026-belem/location.md @@ -0,0 +1,17 @@ ++++ +Title = "Local" +Type = "event" +Description = "Local do devopsdays Belém 2026" ++++ + +Em breve divulgaremos informações sobre o local, incluindo endereço, mapa, estacionamento, transporte e hospedagem. + + + + + + diff --git a/content/events/2026-belem/propose.md b/content/events/2026-belem/propose.md new file mode 100644 index 0000000000..de082e29af --- /dev/null +++ b/content/events/2026-belem/propose.md @@ -0,0 +1,35 @@ ++++ +Title = "Propose" +Type = "event" +Description = "Propose a talk for devopsdays Belém 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-belem/registration.md b/content/events/2026-belem/registration.md new file mode 100644 index 0000000000..b76e9ce94b --- /dev/null +++ b/content/events/2026-belem/registration.md @@ -0,0 +1,11 @@ ++++ +Title = "Registration" +Type = "event" +Description = "Registration for devopsdays Belém 2026" ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2026-belem/sponsor.md b/content/events/2026-belem/sponsor.md new file mode 100644 index 0000000000..77189138ac --- /dev/null +++ b/content/events/2026-belem/sponsor.md @@ -0,0 +1,136 @@ ++++ +Title = "Patrocínio" +Type = "event" +Description = "Patrocine o DevOpsDays Belém 2026" ++++ + +
+ + +Valorizamos o apoio dos patrocinadores a este evento. Se tiver alguma dúvida, esclarecimento ou sugestão, envie um email para {{< email_organizers >}}. +
+ENGLISH: We greatly value sponsors for this open event. Please, let us know if you need any information or suggestion, sending an email to {{< email_organizers >}}. +
+ +### Seja nosso parceiro + +Profissionais de tecnologia irão participar do evento. Esta é uma ótima oportunidade para encontrar os melhores talentos, fazer demonstração dos seus produtos/serviços e tornar sua marca ainda mais conhecida. Também encorajamos nossos parceiros a sugerir temas para os open spaces, sessões auto organizadas abertas para discussões relevantes. Queremos que nossos parceiros se envolvam no evento! + +### Tipos de Patrocínio + +
+ Se você está interessado em um patrocínio especial ou tem uma ideia criativa sobre como pode apoiar o evento, mande um email para nós: {{< email_organizers >}}. +
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
BENEFÍCIOS
Safo1
Bronze
Prata
Ouro
Platina
Diamante
Comunidade2
Contribuição
R$300,00
R$700,00
R$1.000,00
R$2.000,00
R$3.000,00
R$5.000,00
-
 
Disponível
Disponível
Disponível
Disponível
Disponível
Disponível
Disponível
Inscrições para o evento +
(preço especial)1
1
3
5
10
15
-
Espaço para divulgação no local +
-
-
-
-
-
✓
-
Logo no site do evento
✓
✓
✓
✓
✓
✓
✓
Logo nos materiais de marketing
-
-
✓
✓
✓
✓
-
Destaque no Banner
-
-
-
-
✓
✓
-
Material de marketing nos kits
-
-
✓
✓
✓
✓
-
Divulgação nas Redes Sociais
✓
✓
✓
✓
✓
✓
✓
+
+ +

1. Essa cota é válida apenas para empresas e iniciativas locais. O preço do ingresso para os patrocinadores será o mesmo valor do ingresso para estudantes com direito a até 3 ingressos (os nomes e emails das pessoas que serão contempladas com esses ingressos devem ser enviados a organização do evento para checagem na hora do credenciamento).

+ +

2. Patrocinadores que irão apoiar e divulgar o evento na comunidade que representam.

diff --git a/content/events/2026-belem/welcome.md b/content/events/2026-belem/welcome.md new file mode 100644 index 0000000000..2d8d937e2b --- /dev/null +++ b/content/events/2026-belem/welcome.md @@ -0,0 +1,104 @@ ++++ +Title = "DevOpsDays Belém 2026" +Type = "welcome" +aliases = ["/events/2026-belem/"] +Description = "DevOpsDays Belém 2026" ++++ + +
+ {{< event_logo >}} +
+ +

DevOpsDays Belém 2026

+ +
+

+ O DevOpsDays está voltando a Belém em novembro de 2026. Em edições anteriores, + nosso foco sempre foi espalhar a cultura DevOps, fortalecer conexões e trocar + experiências entre profissionais de tecnologia. +

+

+ Se você ainda não participou, essa é a chance de fazer parte. Venha aprender, + trocar ideias, conhecer novas pessoas e se inspirar. Você faz a diferença! +

+

+ Acompanhe o site oficial do evento — + atualizaremos a data, o local, a programação e as oportunidades de patrocínio + conforme tudo for confirmado. +

+

Vamos juntos fazer dessa edição a melhor de todas!

+
+ +
+
+ Data +
+
+ 14 de novembro de 2026, das 09:00 às 18:00. +
+
+ + + + + + + + + + + +
+
+ Patrocínio +
+
+ {{< event_link page="sponsor" text="Patrocine o evento!" >}} +
+
+ +
+
+ Contato +
+
+ {{< event_link page="contact" text="Fale com a organização" >}} +
+
+ +{{< event_twitter >}} diff --git a/data/events/2026/belem/main.yml b/data/events/2026/belem/main.yml new file mode 100644 index 0000000000..61879902ae --- /dev/null +++ b/data/events/2026/belem/main.yml @@ -0,0 +1,118 @@ +name: "2026-belem" # 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: "Belém" # The displayed city name of the event. Capitalize it. +event_twitter: "tasafo" # Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp +description: "DevOpsDays Belém acontece em novembro de 2026!" # 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" + +# 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-11-14T09:00:00-03:00 # The start date of your event. Leave blank if you don't have a venue reserved yet. +enddate: 2026-11-14T18:00:00-03: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: "Belém" # Defaults to city, but you can make it the venue name. +# +location_address: "" #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_twitter: "tasafo" # Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp + + +# 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: Site + url: https://abicora.com/devopsdays-belem + - name: Patrocínio + url: /events/2026-belem/sponsor + - name: Contato + url: /events/2026-belem/contact + - name: Código de Conduta + url: /events/2026-belem/conduct-pt-br + + +# 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: "Paulo Igor" + image: "paulo-igor.jpg" + twitter: "pigodinho" + linkedin: "https://www.linkedin.com/in/pigodinho/" + + - name: "Fábio Figueiredo" + image: "fabio-figueiredo.jpg" + twitter: "fabiolimaf" + linkedin: "https://www.linkedin.com/in/fabiolimaf/" + + - name: "Iago Cavalcante" + image: "iago.jpg" + twitter: "iagoangelimc" + linkedin: "https://www.linkedin.com/in/iago-a-cavalcante/" + + - name: "Ricardo Casseb" + image: "ricardo-casseb.jpg" + linkedin: "https://www.linkedin.com/in/ricardocasseb/" + + - name: "Ryan de Souza" + image: "ryan.jpg" + linkedin: "https://www.linkedin.com/in/theunrealryan/" + + - name: "Thalyson Wilker" + image: "thalyson.jpeg" + linkedin: "https://www.linkedin.com/in/thalysonwilker/" + + - name: "Tiago Danin" + image: "tiago-danin.jpeg" + linkedin: "https://www.linkedin.com/in/tiagodanin/" + +organizer_email: "belem@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: + # - id: samplesponsorname + # level: gold + # url: http://mysponsor.com/?campaign=me # Use this if you need to over-ride a sponsor URL. + +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: Ouro +# max: 10 + - id: silver + label: Prata + max: 0 # This is the same as omitting the max limit. + - id: bronze + label: Bronze + - id: community + label: Comunidade diff --git a/static/_redirects b/static/_redirects index aed8826a05..c57cfe9af7 100644 --- a/static/_redirects +++ b/static/_redirects @@ -9,7 +9,7 @@ /baltimore/* /events/2025-baltimore/:splat 302 /barcelona/* /events/2026-barcelona/:splat 302 /beijing/* /events/2023-beijing/:splat 302 -/belem/* /events/2019-belem/:splat 302 +/belem/* /events/2026-belem/:splat 302 /belo-horizonte/* /events/2026-belo-horizonte/:splat 302 /bengaluru/* /events/2023-bengaluru/:splat 302 /berlin/* /events/2026-berlin/:splat 302