diff --git a/assets/events/2026-portland-or/organizers/jpadams.png b/assets/events/2026-portland-or/organizers/jpadams.png new file mode 100644 index 00000000000..8e91eaec6e8 Binary files /dev/null and b/assets/events/2026-portland-or/organizers/jpadams.png differ diff --git a/assets/events/2026-portland/logo.png b/assets/events/2026-portland/logo.png new file mode 100644 index 00000000000..4770a8573fe Binary files /dev/null and b/assets/events/2026-portland/logo.png differ diff --git a/assets/events/2026-portland/organizers/alastair-drong.jpg b/assets/events/2026-portland/organizers/alastair-drong.jpg new file mode 100644 index 00000000000..9ab9a6f9196 Binary files /dev/null and b/assets/events/2026-portland/organizers/alastair-drong.jpg differ diff --git a/assets/events/2026-portland/organizers/binford2k.jpg b/assets/events/2026-portland/organizers/binford2k.jpg new file mode 100644 index 00000000000..57c3448b6e4 Binary files /dev/null and b/assets/events/2026-portland/organizers/binford2k.jpg differ diff --git a/assets/events/2026-portland/organizers/jberkus.jpg b/assets/events/2026-portland/organizers/jberkus.jpg new file mode 100644 index 00000000000..eae4af0d717 Binary files /dev/null and b/assets/events/2026-portland/organizers/jberkus.jpg differ diff --git a/assets/events/2026-portland/organizers/jyee.jpg b/assets/events/2026-portland/organizers/jyee.jpg new file mode 100644 index 00000000000..a752142ede3 Binary files /dev/null and b/assets/events/2026-portland/organizers/jyee.jpg differ diff --git a/assets/events/2026-portland/organizers/sshastri.jpg b/assets/events/2026-portland/organizers/sshastri.jpg new file mode 100644 index 00000000000..65adaf029a6 Binary files /dev/null and b/assets/events/2026-portland/organizers/sshastri.jpg differ diff --git a/content/events/2026-portland-or/sponsor.md b/content/events/2026-portland-or/sponsor.md index 9b3d61adde6..f53938552c5 100644 --- a/content/events/2026-portland-or/sponsor.md +++ b/content/events/2026-portland-or/sponsor.md @@ -1,66 +1,44 @@ +++ Title = "Sponsor" Type = "event" -Description = "Sponsor devopsdays portland 2026" +Description = "Sponsor Devopsdays Portland 2026" +++ -We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}]. +DevOpsDays Portland is returning after a 5-year hiatus. DevOpsDaysPDX is one of the older events, started in 2013, and it's now returning. It is the only event this year focused on Portland DevOps and open source. -
+Sponsor the conference and connect with application developers, engineers, team leads, startup owners, and agile practitioners. These are the people influencing decisions about security, monitoring, operations, engineering, quality, and product development at leading companies in the greater Portland area. -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. -

-Gold sponsors get a full table and Silver 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. -

+DevOpsDays Portland 2026 will be held at the at Portland State University, and will accommodate up to 180 attendees. - +- [Sponsor Benefits](#sponsor-benefits) +- [Prospectus](#prospectus) +- [Lead Gathering](#lead-gathering) +- [Contracts](#contracts) +- [Ready to Sponsor?](#ready-to-sponsor) + +### Sponsor Benefits + +* Audience of technical decision-makers from top companies, many of which will be previous year speakers +* Conversations with DevOps experts +* Branding and promotion on the DevOpsDays website, social media, and in our communications + +Historically, DevOpsDays PDX attracted 300 to 400 Oregon and Washington technologists. Since we are resuming after a pause, we are expecting a more modest 180. + +### Prospectus + + View the DevOpsDays Portland 2026 Sponsor Prospectus + +### Lead Gathering + +Note that, [by global DevOpsDays policy](https://devopsdays.org/organizing#essential-rules-for-organizing:~:text=Sponsors%20are%20much%20appreciated%20for%20their%20financial%20assistance%2C%20and%20they%20are%20welcome%20to%20participate%20in%20devopsdays%20events.%20They%20are%20never%20given%20attendee%20contact%20info%20by%20a%20devopsdays%20event%E2%80%99s%20organizers%2C%20nor%20are%20they%20allowed%20to%20purchase%20speaking%20slots%20for%20talks%20or%20ignites%20at%20a%20devopsdays.), we do not provide lead scanning or lead gathering for you. However, many of our attendees stop by the booths and **actively ask for a large sponsor contingent in our post-event surveys** so they can talk with vendors. As a result, many sponsors get good leads through active, opt-in collection using raffles for popular items (we provide a time at the end of the conference to announce the raffle winner live), web forms, and QR codes for newsletters or communities. We are happy to advise you on ideas we've found work for other sponsors in the past; don't hesitate to ask us! + +### Contracts + +DevOpsDays Portland is a non-commercial, community-run event, so we do not have formal contracts. Most companies use the prospectus to provide the list of sponsorship benefits if they need something internally. If you have questions about this policy or need more help, email us at {{< email_organizers >}}. + +### Ready to sponsor? + +We can take payment directly, or we can set up an invoice for you. To get an invoice, email us at {{< email_organizers >}}. Otherwise, please reach out to us for a payment link. We look forward to working with you!

diff --git a/content/events/2026-portland/conduct-fr.md b/content/events/2026-portland/conduct-fr.md new file mode 100644 index 00000000000..b20dc446cbb --- /dev/null +++ b/content/events/2026-portland/conduct-fr.md @@ -0,0 +1,37 @@ ++++ +Title = "Conduct" +Type = "event" +Description = "Code de conduite devopsdays portland 2026" ++++ + +Tous les participants, conférenciers, sponsors et volontaires à devopsdays portland 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 portland 2026 est basé sur [fr.confcodeofconduct.com](https://fr.confcodeofconduct.com)._ diff --git a/content/events/2026-portland/conduct-pt-br.md b/content/events/2026-portland/conduct-pt-br.md new file mode 100755 index 00000000000..6427182d476 --- /dev/null +++ b/content/events/2026-portland/conduct-pt-br.md @@ -0,0 +1,28 @@ ++++ +Title = "Conduta" +Type = "event" +Description = "Código de conduta do devopsdays portland 2026" ++++ + + +Participantes, palestrantes, representantes de empresas e pessoas voluntárias no devopsdays portland 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 portland 2026 é baseado em [confcodeofconduct.com](https://confcodeofconduct.com/index-pt-br.html)._ diff --git a/content/events/2026-portland/conduct.md b/content/events/2026-portland/conduct.md new file mode 100644 index 00000000000..d435a74e088 --- /dev/null +++ b/content/events/2026-portland/conduct.md @@ -0,0 +1,28 @@ ++++ +Title = "Conduct" +Type = "event" +Description = "Code of conduct for devopsdays portland 2026" ++++ + + +All attendees, speakers, sponsors, and volunteers at devopsdays portland 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 portland 2026 Code of Conduct is based on [confcodeofconduct.com](https://confcodeofconduct.com)._ diff --git a/content/events/2026-portland/contact.md b/content/events/2026-portland/contact.md new file mode 100644 index 00000000000..074880579ac --- /dev/null +++ b/content/events/2026-portland/contact.md @@ -0,0 +1,17 @@ ++++ +Title = "Contact" +Type = "event" +Description = "Contact information for devopsdays portland 2026" ++++ + + + +**Our local team** + +{{< list_organizers >}} + + +{{< list_core >}} diff --git a/content/events/2026-portland/location.md b/content/events/2026-portland/location.md new file mode 100644 index 00000000000..b0d0f898ed1 --- /dev/null +++ b/content/events/2026-portland/location.md @@ -0,0 +1,17 @@ ++++ +Title = "Location" +Type = "event" +Description = "Location for devopsdays portland 2026" ++++ + +Watch this space for information about the venue including address, map/direction, parking/transit, and any hotel details. + + + + + + diff --git a/content/events/2026-portland-or/propose.md b/content/events/2026-portland/propose.md similarity index 100% rename from content/events/2026-portland-or/propose.md rename to content/events/2026-portland/propose.md diff --git a/content/events/2026-portland/registration.md b/content/events/2026-portland/registration.md new file mode 100644 index 00000000000..8b82e9bb118 --- /dev/null +++ b/content/events/2026-portland/registration.md @@ -0,0 +1,11 @@ ++++ +Title = "Registration" +Type = "event" +Description = "Registration for devopsdays portland 2026" ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2026-portland/sponsor.md b/content/events/2026-portland/sponsor.md new file mode 100644 index 00000000000..9b3d61adde6 --- /dev/null +++ b/content/events/2026-portland/sponsor.md @@ -0,0 +1,66 @@ ++++ +Title = "Sponsor" +Type = "event" +Description = "Sponsor devopsdays portland 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. +

+Gold sponsors get a full table and Silver 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. +

+ + +

diff --git a/content/events/2026-portland/welcome.md b/content/events/2026-portland/welcome.md new file mode 100644 index 00000000000..e92532f3247 --- /dev/null +++ b/content/events/2026-portland/welcome.md @@ -0,0 +1,87 @@ ++++ +Title = "devopsdays portland 2026" +Type = "welcome" +aliases = ["/events/2026-portland/"] +Description = "devopsdays portland 2026" ++++ + +
+ {{< 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" >}} +
+
+ + + diff --git a/data/events/2026/portland-or/main.yml b/data/events/2026/portland-or/main.yml index 1205563c2a4..68c569a1925 100644 --- a/data/events/2026/portland-or/main.yml +++ b/data/events/2026/portland-or/main.yml @@ -10,15 +10,15 @@ ga_tracking_id: "" # If you have your own Google Analytics tracking ID, enter it # 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: # The start date of your event. Leave blank if you don't have a venue reserved yet. -enddate: # The end date of your event. Leave blank if you don't have a venue reserved yet. +startdate: 2026-09-08T12:00:00-07:00 +enddate: 2026-09-10T18:00:00-07:00 # 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_date_start: 2026-05-08T00:00:00-07:00 +cfp_date_end: 2026-06-15T18:00:00-07:00 +cfp_date_announce: 2026-07-01T00:00:00-07:00 -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. +cfp_link: "https://talks.devopsdays.org/devopsdays-portland-2026/cfp" #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. @@ -32,14 +32,14 @@ registration_link: "" # If you have a custom registration link, enter it here. T location: "Portland" # 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! +location_address: "Smith Memorial Student Union, 1825 SW Broadway, Portland, OR 97201" #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://linkedin.com/company/DevOpsDaysPDX" # Change this to the url to your Linkedin group, company, or page. # event_social_slack: "https://join.slack.com/t/DevOpsDaysPDX/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: "DevOpsDaysPDX" # Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp +# event_social_twitter: "DevOpsDaysPDX" # Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp # event_social_mastodon: "https://mastodon.social/@DevOpsDaysPDX" # Change this to url to your mastodon page # event_social_bsky: "https://bsky.app/profile/DevOpsDaysPDX.bsky.social" # Change this to url to your bluesky page event_social_youtube: "devopsdaysportland" # Change this to the youtube channel handle for your event such as devopsdaysrox @@ -53,7 +53,7 @@ event_social_youtube: "devopsdaysportland" # Change this to the youtube channel 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: propose # - name: location # - name: registration # - name: program @@ -93,6 +93,12 @@ team_members: # Name is the only required field for team members. github: "sshastri" linkedin: "https://www.linkedin.com/in/shobshas3/" image: "sshastri.jpg" + - name: "Jeremy Adams" + website: "https://jeremyadams.dev" + github: "jpadams" + linkedin: "https://www.linkedin.com/in/jeremy-adams-pdx" + image: "jpadams.png" + organizer_email: "portland-or@devopsdays.org" # Put your organizer email address here @@ -112,13 +118,28 @@ sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link # 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: platinum + label: Platinum + max: 1 - id: gold label: Gold -# max: 10 + max: 4 - id: silver label: Silver - max: 0 # This is the same as omitting the max limit. - - id: bronze - label: Bronze + max: 12 # This is the same as omitting the max limit. + - id: happyhour + label: Happy Hour + max: 1 + - id: lanyard + label: Lanyard + max: 1 + - id: coffee + label: Coffee Break Sponsor + max: 2 + - id: snack + label: Snacks Sponsor + max: 2 - id: community - label: Community + label: Local Community Groups + - id: media + label: Media diff --git a/data/events/2026/portland/main.yml b/data/events/2026/portland/main.yml new file mode 100644 index 00000000000..1153e5f1701 --- /dev/null +++ b/data/events/2026/portland/main.yml @@ -0,0 +1,124 @@ +name: "2026-portland" # 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: "portland" # The displayed city name of the event. Capitalize it. +event_twitter: "DevOpsDaysPDX" # Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp +description: "Devopsdays is coming to Portland!" # 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: # The start date of your event. Leave blank if you don't have a venue reserved yet. +enddate: # 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: "Portland" # 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_linkedin: "https://linkedin.com/company/DevOpsDaysPDX" # Change this to the url to your Linkedin group, company, or page. +# event_social_slack: "https://join.slack.com/t/DevOpsDaysPDX/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: "DevOpsDaysPDX" # Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp +# event_social_mastodon: "https://mastodon.social/@DevOpsDaysPDX" # Change this to url to your mastodon page +# event_social_bsky: "https://bsky.app/profile/DevOpsDaysPDX.bsky.social" # Change this to url to your bluesky page +event_social_youtube: "devopsdaysportland" # 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: 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: "Alastair Drong" + github: "dev-dull" + linkedin: "https://www.linkedin.com/in/alastair-drong-687bb1/" + website: "https://www.devdull.lol" + image: "alastair-drong.jpg" + - name: "Ben Ford" + github: "binford2k" + linkedin: "https://www.linkedin.com/in/binford2k/" + mastodon: "https://hachyderm.io/@binford2k" + website: "https://binford2k.com" + image: "binford2k.jpg" + - name: "Jason Yee" + github: "jyee" + linkedin: "https://www.linkedin.com/in/gitbisect/" + image: "jyee.jpg" + - name: "Josh Berkus" + github: "jberkus" + linkedin: "https://www.linkedin.com/in/josh-berkus/" + mastodon: "https://m6n.io/@fuzzychef" + website: "https://berkus.org/" + image: "jberkus.jpg" + - name: "Shobhna Shastri" + github: "sshastri" + linkedin: "https://www.linkedin.com/in/shobshas3/" + image: "sshastri.jpg" + +organizer_email: "portland@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. +# - 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