diff --git a/assets/events/2025-halifax/halifax-background.png b/assets/events/2025-halifax/halifax-background.png new file mode 100644 index 00000000000..f616c94870a Binary files /dev/null and b/assets/events/2025-halifax/halifax-background.png differ diff --git a/assets/events/2025-halifax/logo.png b/assets/events/2025-halifax/logo.png new file mode 100644 index 00000000000..714878512f2 Binary files /dev/null and b/assets/events/2025-halifax/logo.png differ diff --git a/assets/events/2025-halifax/organizers/dewan-ahmed.jpg b/assets/events/2025-halifax/organizers/dewan-ahmed.jpg new file mode 100644 index 00000000000..3ae94734c31 Binary files /dev/null and b/assets/events/2025-halifax/organizers/dewan-ahmed.jpg differ diff --git a/assets/events/2025-halifax/organizers/nahrin-jalal.jpeg b/assets/events/2025-halifax/organizers/nahrin-jalal.jpeg new file mode 100644 index 00000000000..4d84369e6bd Binary files /dev/null and b/assets/events/2025-halifax/organizers/nahrin-jalal.jpeg differ diff --git a/assets/events/2025-halifax/organizers/seif-elbayomi.jpg b/assets/events/2025-halifax/organizers/seif-elbayomi.jpg new file mode 100644 index 00000000000..de2a93b469f Binary files /dev/null and b/assets/events/2025-halifax/organizers/seif-elbayomi.jpg differ diff --git a/assets/events/2025-halifax/sharing/halifax-sharing.jpg b/assets/events/2025-halifax/sharing/halifax-sharing.jpg new file mode 100644 index 00000000000..c3298bbcd9f Binary files /dev/null and b/assets/events/2025-halifax/sharing/halifax-sharing.jpg differ diff --git a/content/events/2025-halifax/conduct.md b/content/events/2025-halifax/conduct.md new file mode 100644 index 00000000000..681023d3a70 --- /dev/null +++ b/content/events/2025-halifax/conduct.md @@ -0,0 +1,54 @@ ++++ +Title = "Conduct" +Type = "event" +Description = "Code of conduct for devopsdays Halifax 2025" ++++ + +All attendees, speakers, sponsors, and volunteers at devopsdays Halifax 2025 must agree with the following code of conduct. Organizers will enforce this code throughout the event. We expect cooperation from all participants to help ensure a safe environment for everybody. This Code of Conduct may be revised at any time by devopsdays Halifax 2025 and the terms are non-negotiable. Your registration for or attendance at any devopsdays Halifax event, whether it’s held in person or virtually, indicates your agreement to abide by this policy and its terms. + +### 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, or on Twitter and other online media. At the discretion of the conference organizers, participants violating these rules may be sanctioned or expelled from the conference without a refund. + +### 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, and technology choices, as well as 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 behaviour 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 behaviour, 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 the 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. + +### Expected Behaviour + +All event participants, whether they are attending an in-person event or a virtual event, are expected to behave in accordance with professional standards, with both this Code of Conduct as well as their respective employer’s policies governing appropriate workplace behaviour and applicable laws. + +We expect participants to follow these rules at conference and workshop venues and conference-related social events. + +*The devopsdays Halifax 2025 Code of Conduct is based on [confcodeofconduct.com](https://confcodeofconduct.com/) and the [linux foundation code of conduct](https://events.linuxfoundation.org/about/code-of-conduct/).* + +# Code de conduite devopsdays de 2025 à Halifax + +Tous les participants, orateurs, sponsors et bénévoles de devopsdays de 2025 à Halifax doivent accepter le code de conduite suivant. Les organisateurs feront respecter ce code tout au long de l'événement. Nous attendons de la coopération de tous les participants pour assurer un environnement sûr pour tous. Ce code de conduite peut être révisé à tout moment par devopsdays Halifax 2025 et les termes ne sont pas négociables. Votre inscription ou votre participation à l'un des événements de devopsdays Halifax, qu'il soit en personne ou virtuel, indique votre accord pour respecter cette politique et ses termes. + +### La version rapide + +Notre conférence est dédiée à fournir une expérience de conférence sans harcèlement pour tous, indépendamment du genre, de l'identité et de l'expression de genre, de l'âge, de l'orientation sexuelle, du handicap, de l'apparence physique, de la taille du corps, de la race, de l'origine ethnique, de la religion (ou de l'absence de religion) ou des choix technologiques. Nous ne tolérons aucun harcèlement des participants à la conférence sous quelque forme que ce soit. Le langage et les images sexuelles ne sont pas appropriés pour aucun lieu de conférence, y compris les présentations, les ateliers, les fêtes, ou sur Twitter et autres médias en ligne. À la discrétion des organisateurs de la conférence, les participants qui enfreignent ces règles peuvent être sanctionnés ou expulsés de la conférence sans remboursement. + +### La version détaillée + +Le harcèlement comprend les commentaires verbaux offensants liés au genre, à l'identité et à l'expression de genre, à l'âge, à l'orientation sexuelle, au handicap, à l'apparence physique, à la taille du corps, à la race, à l'origine ethnique, à la religion et aux choix technologiques, ainsi que les images sexuelles dans les espaces publics, l'intimidation délibérée, la traque, la photographie ou l'enregistrement harcelants, la perturbation soutenue des discours ou d'autres événements, le contact physique inapproprié et l'attention sexuelle indésirable. On s’attend à ce que les participants à qui on demande de cesser tout comportement de harcèlement se conforment immédiatement. + +Les sponsors sont également soumis à la politique contre le harcèlement. En particulier, les sponsors ne doivent pas utiliser d'images, d'activités ou de matériel sexualisés. Le personnel du stand (y compris les bénévoles) ne doit pas utiliser de vêtements/uniformes/costumes sexualisés, ou de créer un environnement sexualisé. +Si un participant se livre à un comportement de harcèlement, les organisateurs de la conférence peuvent prendre toute mesure qu'ils jugent appropriée, y compris avertir l'auteur ou l'expulser de la conférence sans remboursement. + +Si vous êtes harcelé, si vous remarquez que quelqu'un d'autre est harcelé ou si vous avez d'autres préoccupations, veuillez contacter immédiatement un membre du personnel de la conférence. Le personnel de la conférence peut être identifié par des badges distincts. + +Le personnel de la conférence sera heureux d'aider les participants à contacter la sécurité de l'hôtel/du lieu ou la police locale, de fournir des escortes ou d'aider autrement ceux qui subissent du harcèlement à se sentir en sécurité pendant la durée de la conférence. Nous apprécions votre participation. + +### Comportement attendu + +Tous les participants à l'événement, qu'il s'agisse d'un événement en personne ou virtuel, sont tenus de se comporter conformément aux normes professionnelles, à ce code de conduite ainsi qu’aux politiques de leur employeur régissant le comportement approprié sur le lieu de travail et aux lois applicables. + +Nous attendons des participants qu'ils suivent ces règles dans les lieux de conférence et d'atelier ainsi que lors des événements sociaux liés à la conférence. + +*Le code de conduite de devopsdays Halifax 2025 est basé sur [confcodeofconduct.com](https://confcodeofconduct.com/) et le [code de conduite de la Linux Foundation](https://events.linuxfoundation.org/about/code-of-conduct/).* \ No newline at end of file diff --git a/content/events/2025-halifax/contact.md b/content/events/2025-halifax/contact.md new file mode 100644 index 00000000000..91895be3c1e --- /dev/null +++ b/content/events/2025-halifax/contact.md @@ -0,0 +1,14 @@ ++++ +Title = "Contact" +Type = "event" +Description = "Contact information for devopsdays Halifax 2025" ++++ + +Please contact us by email: {{< email_organizers >}} + +**Our local team** + +{{< list_organizers >}} + + +{{< list_core >}} \ No newline at end of file diff --git a/content/events/2025-halifax/location.md b/content/events/2025-halifax/location.md new file mode 100644 index 00000000000..b03d382cc38 --- /dev/null +++ b/content/events/2025-halifax/location.md @@ -0,0 +1,7 @@ ++++ +Title = "Location" +Type = "event" +Description = "Location for devopsdays Halifax 2025" ++++ + +The location for DevOpsDays Halifax 2025 is yet to be decided. Once it is confirmed, we will update this page with the details. Stay tuned! diff --git a/content/events/2025-halifax/program.md b/content/events/2025-halifax/program.md new file mode 100644 index 00000000000..f23db691b67 --- /dev/null +++ b/content/events/2025-halifax/program.md @@ -0,0 +1,15 @@ ++++ +Title = "Program" +Type = "program" +Description = "Program for devopsdays Halifax 2024" ++++ + +
+
+
+ FYI: The schedule is not available yet. Please check back soon. +
+ If Open Spaces are new to you, you may be interested in more details about Open Space. +
+
+
\ No newline at end of file diff --git a/content/events/2025-halifax/propose.md b/content/events/2025-halifax/propose.md new file mode 100644 index 00000000000..d90389e74cc --- /dev/null +++ b/content/events/2025-halifax/propose.md @@ -0,0 +1,41 @@ ++++ +Title = "Propose" +Type = "event" +Description = "Propose a talk for devopsdays Halifax 2025" ++++ + +The CfP for DevOpsDays Halifax 2024 is now OPEN! + +Visit [this website](https://talks.devopsdays.org/devopsdays-halifax-2025/cfp) to submit your talk. + +Important: The CfP closes on 2025-03-31 23:59 (America/Halifax time). + +
+ +We're looking for speakers for DevOpsDays Halifax 2025. Want to present your thoughts, ideas, and strategies around DevOps to your peers from Atlantic Canada? Submit your talk proposal here for review by the DevOpsDays Halifax organizing committee. + +This is a single track event, with 30 minute slots. We're expecting between 150-200 attendees at the conference. + +Some topic ideas include but are not limited to: + +- Automation: Infrastructure as code (IaC), CI/CD pipelines, configuration management, containerization, and orchestration. +- Cloud Native: Building and deploying applications for the cloud, microservices architecture, serverless computing, and cloud-native security. +- Security: DevSecOps, vulnerability management, secrets management, and compliance. +- Monitoring and Observability: Metrics, logging, tracing, and alerting for performance and incident response. +- Testing: Continuous testing, automated testing frameworks, and chaos engineering. +- Collaboration: Communication, teamwork, and cultural change between development and operations teams. +- Artificial intelligence (AI) and Machine Learning (ML): Applications in DevOps, automation, and anomaly detection. +- Edge computing: Building and deploying applications at the edge of the network. +- Serverless computing: Building applications without managing infrastructure. +- Quantum computing: Potential applications for DevOps and IT. +- Open source tools and technologies: Latest advancements and best practices. + +You can find more information about the conference, including our code of conduct, [here](https://devopsdays.org/events/2024-halifax/conduct). + +First-time speaking? Come on board! + +Do you require funding for travel or accommodation? Please send an email to [{{< email_organizers >}}] with some details. We have a limited budget for speaker travel and accommodation assistance, and we'll allocate this based on need and on a first-come-first-serve basis. + +All submissions will be reviewed blindly, meaning that the program committee is unable to see the submitter’s personal details. Only the title of the talk and the describing abstract will be visible to the reviewers in order to reduce unconscious bias. After all talks are rated, we will inform you about the status of your submission. Talks can either be accepted, rejected or waitlisted. In case your talk is waitlisted, we will message you if a speaking slot opens up before the conference.How to submit a proposal: Visit [this website](https://talks.devopsdays.org/devopsdays-halifax-2025/cfp) to submit your talk. + +If you have any question regarding the CfP, you can send an email to [{{< email_organizers >}}]. \ No newline at end of file diff --git a/content/events/2025-halifax/registration.md b/content/events/2025-halifax/registration.md new file mode 100644 index 00000000000..37211f49a1f --- /dev/null +++ b/content/events/2025-halifax/registration.md @@ -0,0 +1,12 @@ ++++ +Title = "Registration" +Type = "event" +Description = "Registration for devopsdays Halifax 2025" ++++ + +
+ +The registration for DevOpsDays Halifax 2025 is not yet open. Once it is open, we will update this page with the details. Stay tuned! + +
+ \ No newline at end of file diff --git a/content/events/2025-halifax/speakers.md b/content/events/2025-halifax/speakers.md new file mode 100644 index 00000000000..3ebfdb24fbb --- /dev/null +++ b/content/events/2025-halifax/speakers.md @@ -0,0 +1,5 @@ ++++ +Title = "Speakers" +Type = "speakers" +Description = "Speakers for devopsdays Halifax 2025" ++++ diff --git a/content/events/2025-halifax/sponsor.md b/content/events/2025-halifax/sponsor.md new file mode 100644 index 00000000000..cedfa83ce6e --- /dev/null +++ b/content/events/2025-halifax/sponsor.md @@ -0,0 +1,232 @@ ++++ +Title = "Sponsor" +Type = "event" +Description = "Sponsor DevOpsDays Halifax 2025" ++++ + +We greatly value sponsors for this community event. If you are interested in sponsoring, please send us an email. +
+ +DevOpsDays Halifax is a community 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 and Gold sponsors get a full table in the sponsor area 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 Halifax on their own terms. + +

Sponsorship Packages

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
THE GOODSPLATINUMGOLDSILVERBRONZECOMMUNITY
Price$7,500$5,000$3,500$1,500Free
+ Contact us + + Contact us + + Contact us + + Contact us + + Contact us +
Tickets Included64322
Logo on DevOpsDays Halifax websiteYesYesYesYesYes
Social media shout-outYesYesYesYesYes
Logo on marketing materialsYesYesYesYes
Logo on slides at breaksYesYesYesYes
Logo on participant emailsYesYesYesYes
Logo on banner at registration areaYesYesYesYesYes
Shout-out from MC's at kickoff and again at breaksYesYesYes
Dedicated logo slide during breaksYesYesYes
Logo on shared slide during breaksYesYes
Dedicated table in sponsor area (with chairs)YesYesYes
15-minute presentation over lunch hourYes
10-minute presentation over lunch hourYes
+ + +

Special Sponsorships

+ +All special sponsors will have their logo displayed on the DevOpsDays Halifax website, a shoutout on LinkedIn before the conference, and be thanked on stage during the conference. We have some flexibility with these sponsorships, so feel free to reach out with your request! Email us: halifax@devopsdays.org. +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
SponsorshipPriceDescriptionTickets IncludedNumber Available
Lanyard$3,000Your logo and colors around every attendee's credential21
Swag$3,000Sponsor swag for the attendees21
Speaker Dinner$2,500Sponsor the dinner for speakers21
Coffee$2,000Sponsor coffee for the attendees21
ScholarshipsVariesProvide tickets for under-indexed groups to attend42
+ +
+
+
+
+ Sponsors are responsible for providing high-res logos for use on the website and in promotional materials. The preferred file formats are EPS or AI. +

+ All sponsors attendees must be registered to attend. We offer sponsors 20% off all additional registrations. +

+
+
+ + + + + \ No newline at end of file diff --git a/content/events/2025-halifax/welcome.md b/content/events/2025-halifax/welcome.md new file mode 100644 index 00000000000..1d0b7a62dd9 --- /dev/null +++ b/content/events/2025-halifax/welcome.md @@ -0,0 +1,101 @@ ++++ +Title = "DevOpsDays Halifax 2025" +Type = "welcome" +aliases = ["/events/2025-halifax/"] +Description = "DevOpsDays Halifax 2025" ++++ + + + +
+
+ +
+

DevOpsDays Halifax 2025 – bigger, bolder, and back for more!

+

Last year, we welcomed nearly 200 attendees from across the Maritime provinces, hosted 20 expert speakers from around the world, and saw representation from leading tech companies. With a three-day program featuring conference sessions, hands-on workshops, a social networking event, and a speaker dinner cruise, it was a milestone event for the region’s tech community.

+

Join us in 2025 as we build on this momentum! Expect insightful talks, engaging Open Spaces, and hands-on learning opportunities on topics such as Cloud Native, Platform Engineering, AI in DevOps, and more.

+

Who attends?

+

DevOpsDays Halifax attracts a diverse mix of professionals, from senior technical leaders and executives to software engineers, platform teams, site reliability engineers, security specialists, and students. Whether you're shaping DevOps strategy at an enterprise level or just starting out in the field, this event is your chance to connect, learn, and grow with the best in the industry.

+

Set against the stunning backdrop of Halifax’s waterfront, DevOpsDays Halifax also offers the opportunity to connect over fresh seafood, scenic views, and the warmth of the Atlantic Canadian tech community.

+

Spots will fill fast—follow us on LinkedIn to be the first to know when registration opens!

+

By attending this event, you agree to the DevOpsDays Halifax Code of Conduct.

+
+
+
+ + + +
+
+ +{{< event_twitter >}} diff --git a/content/events/2025-halifax/workshop.md b/content/events/2025-halifax/workshop.md new file mode 100644 index 00000000000..e23f19332fe --- /dev/null +++ b/content/events/2025-halifax/workshop.md @@ -0,0 +1,9 @@ ++++ +Title = "Preconference Workshop - DevOpsDays Halifax 2025" +Type = "workshop" +Description = "TBD" ++++ + +## This part of the conference is TBD + +{{< event_twitter >}} diff --git a/data/events/2025/atlanta/main.yml b/data/events/2025/atlanta/main.yml index 959f7d2a2e6..76ba9abfb3f 100644 --- a/data/events/2025/atlanta/main.yml +++ b/data/events/2025/atlanta/main.yml @@ -77,6 +77,8 @@ organizer_email: "atlanta@devopsdays.org" # Put your organizer email address her sponsors: - id: arresteddevops level: community + - id: spacelift + level: gold sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link diff --git a/data/events/2025/chicago/main.yml b/data/events/2025/chicago/main.yml index 401f58881c8..85579d436f3 100644 --- a/data/events/2025/chicago/main.yml +++ b/data/events/2025/chicago/main.yml @@ -193,6 +193,8 @@ sponsors: level: gold - id: castai level: gold + - id: komodor + level: gold - id: fairwinds level: bronze - id: lightrun diff --git a/data/events/2025/halifax/main.yml b/data/events/2025/halifax/main.yml new file mode 100644 index 00000000000..26f9617cc1b --- /dev/null +++ b/data/events/2025/halifax/main.yml @@ -0,0 +1,119 @@ +name: "2025-halifax" # The name of the event. Four digit year with the city name in lower-case, with no spaces. +year: "2025" # The year of the event. Make sure it is in quotes. +city: "Halifax" # The displayed city name of the event. Capitalize it. +event_twitter: "DevOpsDaysHali" # Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp +description: "The premier DevOps conference for Atlantic Canada" # 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" + +masthead_background: "halifax-background.png" +sharing_image: "halifax-sharing.png" + +# All dates are in unquoted 2025-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 2025-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: 2025-08-26T07:00:00-03:00 +enddate: 2025-08-27T21:00:00-03:00 + +# Leave CFP dates blank if you don't know yet, or set all three at once. +cfp_date_start: 2025-02-15 # start accepting talk proposals. +cfp_date_end: 2025-03-31 # close your call for proposals. +cfp_date_announce: 2025-04-30 # inform proposers of status + +cfp_link: "https://talks.devopsdays.org/devopsdays-halifax-2025/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. + +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: "" +location: "" +location_address: "" +# +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! + +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: "Dewan Ahmed" + image: "dewan-ahmed.jpg" + bio: "Dewan Ahmed serves as a Principal Developer Advocate at Harness, leveraging his decade-long experience tackling DevOps challenges across startups, corporates, and governments. With past roles at IBM, Red Hat, and Aiven, he is a seasoned developer relations professional. A tech speaker since 2016, he champions open-source and values community engagement." + role: "Principal Developer Advocate" + employer: "Harness" + github: "dewan-ahmed" + twitter: "DewanAhmed" + linkedin: "https://www.linkedin.com/in/diahmed/" + - name: "Nahrin Jalal" + image: "nahrin-jalal.jpeg" + bio: "Nahrin Jalal has led Developer Relations teams in startup environments and contributed to the growth of a publicly-traded enterprise. She is deeply passionate about building inclusive communities, inspiring developers to address real-world needs with pragmatic software solutions, and creating technical content that is accessible to all skill levels." + role: "Developer Relations and Outreach Strategy" + github: "NJalal7" + twitter: "NahrinJalal" + linkedin: "https://www.linkedin.com/in/nahrin-jalal/" + - name: "Seif Elbayomi" + image: "seif-elbayomi.jpg" + bio: "Seif Elbayomi is a Software Developer at VTScada who is passionate about building solutions that matter and continuously learning. He is dedicated to driving digital transformation in Atlantic Canada." + role: "Software Developer" + employer: "VTScada" + github: "SeifElbayomi" + linkedin: "https://www.linkedin.com/in/seifelbayomi/" + +organizer_email: "halifax@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. + +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: platinum + label: Platinum + max: 5 + - id: gold + label: Gold + max: 6 + - id: silver + label: Silver + max: 6 + #max: 0 # This is the same as omitting the max limit. + - id: closedcaptioning + label: Closed Captioning + max: 1 + - id: lanyard + label: Lanyard + max: 1 + - id: breakfast + label: Breakfast + max: 2 + - id: lunch + label: Lunch + max: 2 + - id: break + label: Break + max: 4 + - id: community + label: Community + max: 3 diff --git a/static/_redirects b/static/_redirects index a22739d0f85..d2d98560874 100644 --- a/static/_redirects +++ b/static/_redirects @@ -52,7 +52,7 @@ /hartford/* /events/2019-hartford/:splat 302 /helsinki/* /events/2014-helsinki/:splat 302 /houston/* /events/2024-houston/:splat 302 -/halifax/* /events/2024-halifax/:splat 302 +/halifax/* /events/2025-halifax/:splat 302 /indianapolis/* /events/2023-indianapolis/:splat 302 /istanbul/* /events/2024-istanbul/:splat 302 /jakarta/* /events/2022-jakarta/:splat 302 diff --git a/themes/devopsdays-theme/layouts/partials/events/cta.html b/themes/devopsdays-theme/layouts/partials/events/cta.html index e5865ea9cd2..01cf09fa8ca 100644 --- a/themes/devopsdays-theme/layouts/partials/events/cta.html +++ b/themes/devopsdays-theme/layouts/partials/events/cta.html @@ -2,6 +2,17 @@
+ + {{- if $e.startdate -}} + {{- if $e.cfp_date_start -}} + {{- if and (ge now (time $e.cfp_date_start)) (le now (time $e.cfp_date_end)) -}} +
+ Propose +
+ {{- end -}} + {{- end -}} + {{- end -}} + {{- if $e.registration_open -}} {{- if eq $e.registration_open "true" -}} @@ -46,26 +57,11 @@ {{- end -}} {{- end -}} - - - - {{- if $e.startdate -}} - {{- if $e.cfp_date_start -}} - {{- if and (ge now (time $e.cfp_date_start)) (le now (time $e.cfp_date_end)) -}} -
- Propose -
- {{- end -}} - {{- end -}} - {{- end -}} - - - - - {{- if $e.event_twitter -}} - {{- if ne $e.event.twitter "" -}} + + {{- if $e.organizer_email -}} + {{- if ne $e.organizer_email "" -}}
- Follow + Contact
{{- end -}} {{- end -}} @@ -120,4 +116,4 @@
- + \ No newline at end of file diff --git a/themes/devopsdays-theme/layouts/shortcodes/event_social_bsky.html b/themes/devopsdays-theme/layouts/shortcodes/event_social_bsky.html new file mode 100644 index 00000000000..daf6d67865c --- /dev/null +++ b/themes/devopsdays-theme/layouts/shortcodes/event_social_bsky.html @@ -0,0 +1,7 @@ +{{- $e := partial "functions/get-event-data" . -}} + +{{- if $e.event_social_bsky -}} + +{{- else -}} + +{{- end -}} \ No newline at end of file diff --git a/themes/devopsdays-theme/layouts/shortcodes/event_social_linkedin.html b/themes/devopsdays-theme/layouts/shortcodes/event_social_linkedin.html new file mode 100644 index 00000000000..2e0ffeb7a9a --- /dev/null +++ b/themes/devopsdays-theme/layouts/shortcodes/event_social_linkedin.html @@ -0,0 +1,7 @@ +{{- $e := partial "functions/get-event-data" . -}} + +{{- if $e.event_social_linkedin -}} + +{{- else -}} + +{{- end -}} \ No newline at end of file diff --git a/themes/devopsdays-theme/layouts/shortcodes/event_social_listserv.html b/themes/devopsdays-theme/layouts/shortcodes/event_social_listserv.html new file mode 100644 index 00000000000..3dc449b9652 --- /dev/null +++ b/themes/devopsdays-theme/layouts/shortcodes/event_social_listserv.html @@ -0,0 +1,7 @@ +{{- $e := partial "functions/get-event-data" . -}} + +{{- if $e.event_social_listserv -}} + +{{- else -}} + +{{- end -}} \ No newline at end of file diff --git a/themes/devopsdays-theme/layouts/shortcodes/event_social_mastodon.html b/themes/devopsdays-theme/layouts/shortcodes/event_social_mastodon.html new file mode 100644 index 00000000000..3f7e967cbb9 --- /dev/null +++ b/themes/devopsdays-theme/layouts/shortcodes/event_social_mastodon.html @@ -0,0 +1,7 @@ +{{- $e := partial "functions/get-event-data" . -}} + +{{- if $e.event_social_mastodon -}} + +{{- else -}} + +{{- end -}} \ No newline at end of file diff --git a/themes/devopsdays-theme/layouts/shortcodes/event_social_slack.html b/themes/devopsdays-theme/layouts/shortcodes/event_social_slack.html new file mode 100644 index 00000000000..b0fb292ac22 --- /dev/null +++ b/themes/devopsdays-theme/layouts/shortcodes/event_social_slack.html @@ -0,0 +1,7 @@ +{{- $e := partial "functions/get-event-data" . -}} + +{{- if $e.event_social_slack -}} + +{{- else -}} + +{{- end -}} \ No newline at end of file diff --git a/themes/devopsdays-theme/layouts/shortcodes/event_social_twitter.html b/themes/devopsdays-theme/layouts/shortcodes/event_social_twitter.html new file mode 100644 index 00000000000..e6db0d91fbd --- /dev/null +++ b/themes/devopsdays-theme/layouts/shortcodes/event_social_twitter.html @@ -0,0 +1,7 @@ +{{- $e := partial "functions/get-event-data" . -}} + +{{- if $e.event_social_twitter -}} + +{{- else -}} + +{{- end -}} \ No newline at end of file diff --git a/themes/devopsdays-theme/layouts/shortcodes/event_social_youtube.html b/themes/devopsdays-theme/layouts/shortcodes/event_social_youtube.html new file mode 100644 index 00000000000..b98ebb75c14 --- /dev/null +++ b/themes/devopsdays-theme/layouts/shortcodes/event_social_youtube.html @@ -0,0 +1,7 @@ +{{- $e := partial "functions/get-event-data" . -}} + +{{- if $e.event_social_youtube -}} + +{{- else -}} + +{{- end -}} \ No newline at end of file diff --git a/themes/devopsdays-theme/reference.md b/themes/devopsdays-theme/reference.md index 3db2fc4f8ff..2592c40acd4 100644 --- a/themes/devopsdays-theme/reference.md +++ b/themes/devopsdays-theme/reference.md @@ -47,18 +47,17 @@ The `/data/events/YYYY/CITY.main.yml` file is the main configuration file for yo ### General Fields -| Field Name | Type | Required | Description | Example | -|------------------|--------|----------|-------------------------------------------------------------------------------------------------------|-----------------------------------------------| -| `name` | String | Yes | The name of the event. Four digit year with the city name in lower-case, with no spaces. | "2017-chicago" | -| `year` | String | Yes | The year of the event. Make sure it is in quotes. | "2017" | -| `city` | String | Yes | The displayed city name of the event. Capitalize it. | "Salt Lake City" | -| `event_twitter` | String | Yes | The twitter handle for your event such as "devopsdayschi" or "devopsdaysmsp". Exclude the "@" symbol. | "devopsdayschi" | -| `description` | String | No | Overall description of your event. Quotation marks need to be escaped. | "It's time for more DevOpsDays at Ponyville!" | -| `ga_tracking_id` | String | No | If you have your own Google Analytics tracking ID, enter it here. | "UA-74738648-1" | -| `gtm_tracking_id` | String | No | If you have your own Google Analytics v4 tracking ID, enter it here. | "G-NCBC4PBEMK" | -| `event_group` | String | No | If you'd like to group different events together (ie, "australia"), set them to the same "event_group" | "ponyville" | -| `speakers_verbose` | String | No | Set this to "true" if you want verbose speaker attributes (URLs visible). | "true" | -| `cancel` | String | No | If your event must be cancelled, add this field with the value of "true" (case-sensitive). This will keep it from being listed in the "upcoming events" views. | "true" | | +| Field Name | Type | Required | Description | Example | +|--------------------|--------|----------|-------------------------------------------------------------------------------------------------------|-----------------------------------------------| +| `name` | String | Yes | The name of the event. Four digit year with the city name in lower-case, with no spaces. | "2017-chicago" | +| `year` | String | Yes | The year of the event. Make sure it is in quotes. | "2017" | +| `city` | String | Yes | The displayed city name of the event. Capitalize it. | "Salt Lake City" | +| `description` | String | No | Overall description of your event. Quotation marks need to be escaped. | "It's time for more DevOpsDays at Ponyville!" | +| `ga_tracking_id` | String | No | If you have your own Google Analytics tracking ID, enter it here. | "UA-74738648-1" | +| `gtm_tracking_id` | String | No | If you have your own Google Analytics v4 tracking ID, enter it here. | "G-NCBC4PBEMK" | +| `event_group` | String | No | If you'd like to group different events together (ie, "australia"), set them to the same "event_group"| "ponyville" | +| `speakers_verbose` | String | No | Set this to "true" if you want verbose speaker attributes (URLs visible). | "true" | +| `cancel` | String | No | If your event must be cancelled, add this field with the value of "true" (case-sensitive). This will keep it from being listed in the "upcoming events" views. | "true" | ### Date-related Fields All dates are in unquoted YYYY-MM-DD, like this: `variable: 2016-01-05`, or like `variable: 2016-01-05T23:59:00-06:00` @@ -80,6 +79,18 @@ All dates are in unquoted YYYY-MM-DD, like this: `variable: 2016-01-05`, or like | `registration_link` | String | No | If you have a custom registration link, enter it here. This will control the Registration menu item as well as the "Register" button. | "https://myurlhere" reference it like {{< event_link url-key="registration_link" text="Register to attend the conference!" >}} | | | `sponsor_link` | String | No | If you have a custom sponsorship link, enter it here. This will control the "Become an X Sponsor!" links. It does NOT change the "Sponsor" button. | "https://myurlhere" | | +### Social Fields +| Field Name | Type | Required | Description | Example | +|-------------------------|--------|----------|-------------------------------------------------------------------------------------------------------|------------------------------------------------------| +| `event_social_twitter` | String | No | The twitter handle for your event such as "devopsdayschi" or "devopsdaysmsp". Exclude the "@" symbol. | "devopsdaysrox" | +| `event_social_linkedin` | String | No | The direct URL to your linkedin event or group/company page. | "https://www.linkedin.com/company/devopsdaysrox" | +| `event_social_youtube` | String | No | The Youtube handle for your event such as "devopsdaysrox" or "devopsdayschi". Exclude the "@" symbol. | "devopsdaysrox" | +| `event_social_bsky` | String | No | The BlueSky direct URL for your event/group profile. Can link to a custom server. | "https://bsky.app/profile/dodrox.bsky.social" | +| `event_social_mastodon` | String | No | The Mastodon direct URL for your event/group profile. Can link to a custom server. | "https://mastodon.social/@dodrox" | +| `event_social_slack` | String | No | The invite URL to your slack workspace. | "https://join.slack.com/t/dodrox/shared_invite/xyz" | +| `event_social_listserv` | String | No | The URL to subscribe to your group mailing list. | "https://lists.devopsdays.org/subscription?f=xyz". | +| `event_twitter` | String | No | Legacy field for the twitter handle. Exclude the "@" symbol. Kept for backward support. | "devopsdayschi" | + ### Branding Fields | Field Name | Type | Required | Description | Example | diff --git a/themes/devopsdays-theme/static/css/site.css b/themes/devopsdays-theme/static/css/site.css index 444a002d5d0..e9c783bff23 100644 --- a/themes/devopsdays-theme/static/css/site.css +++ b/themes/devopsdays-theme/static/css/site.css @@ -10346,4 +10346,90 @@ article .article__body nav#toc .toc li > ol { font-size: 13px; } } + +/* social badges */ +.social-bsky { + color: black; + height: 50px; + padding: 12px; + font-size: 30px; + text-decoration: none; + display: inline-block; +} +.social-bksy:hover { + color: rgb(17, 134, 243); + text-decoration: none; +} +.social-li { + color: black; + height: 50px; + padding: 12px; + font-size: 30px; + text-decoration: none; + display: inline-block; +} +.social-li:hover { + color: rgb(29, 96, 196); + text-decoration: none; +} +.social-envelope { + color: black; + height: 50px; + padding: 12px; + font-size: 30px; + text-decoration: none; + display: inline-block; +} +.social-envelope:hover { + color: rgb(46, 124, 43); + text-decoration: none; +} +.social-mstd { + color: black; + height: 50px; + padding: 12px; + font-size: 30px; + text-decoration: none; + display: inline-block; +} +.social-mstd:hover { + color: rgb(110, 99, 218); + text-decoration: none; +} +.social-slack { + color: black; + height: 50px; + padding: 12px; + font-size: 30px; + text-decoration: none; + display: inline-block; +} +.social-slack:hover { + color: rgb(223, 180, 42); + text-decoration: none; +} +.social-x { + color: black; + height: 50px; + padding: 12px; + font-size: 30px; + text-decoration: none; + display: inline-block; +} +.social-x:hover { + color: rgb(95, 92, 92); + text-decoration: none; +} +.social-yt { + color: black; + height: 50px; + padding: 12px; + font-size: 30px; + text-decoration: none; + display: inline-block; +} +.social-yt:hover { + color: rgb(224, 52, 52); + text-decoration: none; +} /*# sourceMappingURL=site.css.map */ diff --git a/utilities/examples/data/events/main.yml b/utilities/examples/data/events/main.yml index 6fccebbec60..feb6848ddb6 100644 --- a/utilities/examples/data/events/main.yml +++ b/utilities/examples/data/events/main.yml @@ -34,6 +34,18 @@ location: "yourlocation" # 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/devopsdayscityabbr" # Change this to the url to your Linkedin group, company, or page. +event_social_slack: "https://join.slack.com/t/devopsdayscityabbr/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: "devopsdayscityabbr" # Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp +event_social_mastadon: "https://mastodon.social/@devopsdayscityabbr" # Change this to url to your mastadon page +event_social_bsky: "https://bsky.app/profile/devopsdayscityabbr.bsky.social" # Change this to url to your bluesky page +event_social_youtube: "devopsdayscityabbr" # Change this to the youtube channel handle for your event such as devopsdaysrox +# legacy +event_twitter: "devopsdayscityabbr" # 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