diff --git a/assets/events/2026-almaty/logo-square.png b/assets/events/2026-almaty/logo-square.png new file mode 100644 index 0000000000..8efd41e3fc Binary files /dev/null and b/assets/events/2026-almaty/logo-square.png differ diff --git a/assets/events/2026-almaty/logo.png b/assets/events/2026-almaty/logo.png new file mode 100644 index 0000000000..1f65cf75b9 Binary files /dev/null and b/assets/events/2026-almaty/logo.png differ diff --git a/content/events/2026-almaty/conduct.md b/content/events/2026-almaty/conduct.md new file mode 100644 index 0000000000..c4b6d74e4c --- /dev/null +++ b/content/events/2026-almaty/conduct.md @@ -0,0 +1,28 @@ ++++ +Title = "Conduct" +Type = "event" +Description = "Code of conduct for devopsdays Almaty 2026" ++++ + + +All attendees, speakers, sponsors, and volunteers at devopsdays Almaty 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 Almaty 2026 Code of Conduct is based on [confcodeofconduct.com](https://confcodeofconduct.com)._ diff --git a/content/events/2026-almaty/contact.md b/content/events/2026-almaty/contact.md new file mode 100644 index 0000000000..fd442eaf46 --- /dev/null +++ b/content/events/2026-almaty/contact.md @@ -0,0 +1,14 @@ ++++ +Title = "Contact" +Type = "event" +Description = "Contact information for devopsdays Almaty 2026" ++++ + +If you'd like to contact us by email: {{< email_organizers >}} + +**Our local team** + +{{< list_organizers >}} + + +{{< list_core >}} diff --git a/content/events/2026-almaty/propose.md b/content/events/2026-almaty/propose.md new file mode 100644 index 0000000000..ec567ff6a8 --- /dev/null +++ b/content/events/2026-almaty/propose.md @@ -0,0 +1,35 @@ ++++ +Title = "Propose" +Type = "event" +Description = "Propose a talk for devopsdays Almaty 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-almaty/registration.md b/content/events/2026-almaty/registration.md new file mode 100644 index 0000000000..7b11d9c66d --- /dev/null +++ b/content/events/2026-almaty/registration.md @@ -0,0 +1,11 @@ ++++ +Title = "Registration" +Type = "event" +Description = "Registration for devopsdays Almaty 2026" ++++ + +
+ +Embed registration iframe/link/etc. +
+ diff --git a/content/events/2026-almaty/welcome.md b/content/events/2026-almaty/welcome.md new file mode 100644 index 0000000000..1649da1d86 --- /dev/null +++ b/content/events/2026-almaty/welcome.md @@ -0,0 +1,51 @@ ++++ +Title = "devopsdays Almaty 2026" +Type = "welcome" +aliases = ["/events/2026-almaty/"] +Description = "devopsdays Almaty 2026" ++++ + +
+ {{< event_logo >}} +
+ +
+
+ Dates +
+
+ {{< event_start >}} - {{< event_end >}} +
+
+ +
+
+ Register +
+
+ {{< event_link url-key="registration_link" text="Register to attend the conference!" >}} +
+
+ +
+
+ Propose +
+
+ {{< event_link url-key="cfp_link" text="Propose a talk!" >}} +
+
+ +
+
+ Contact +
+
+ {{< event_link page="contact" text="Get in touch with the organizers" >}} +
+
+ + + diff --git a/data/events/2026/almaty/main.yml b/data/events/2026/almaty/main.yml new file mode 100644 index 0000000000..37d93a5663 --- /dev/null +++ b/data/events/2026/almaty/main.yml @@ -0,0 +1,88 @@ +name: "2026-almaty" # 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: "Almaty" # The displayed city name of the event. Capitalize it. +event_twitter: "devopsdays" # Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp +description: "https://devopsdays.kz" # 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-10-16T09:00:00+06:00 # The start date of your event. Leave blank if you don't have a venue reserved yet. +enddate: 2026-10-16T18:00:00+06:00 # The end date of your event. Leave blank if you don't have a venue reserved yet. + +# Leave CFP dates blank if you don't know yet, or set all three at once. +cfp_date_start: 2026-05-01T09:00:00+06:00 # start accepting talk proposals. +cfp_date_end: 2026-10-01T18:00:00+06:00 # close your call for proposals. +cfp_date_announce: # inform proposers of status + +cfp_link: "https://forms.gle/QUoSuAdyWyu7b3qJ9" #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: 2026-06-23T00:00:00+06:00 # start accepting registration. Leave blank if registration is not open yet. This will make the "Register" button appear on your "Welcome" page. +registration_date_end: 2026-10-16T18:00:00+06:00 # 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: "https://tickets.devopsdays.kz/" # 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: "Forum Event Space" # Defaults to city, but you can make it the venue name. +# +location_address: "Forum Almaty, Seyfullin Avenue 617, Almaty, Kazakhstan" # 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/devopsdays-almaty" # Change this to the url to your Linkedin group, company, or page. +event_social_youtube: "devopsdaysalmaty5046" # Change this to the youtube channel handle for your event such as devopsdaysrox + +nav_elements: # List of pages you want to show up in the navigation of your page. + - name: propose + url: https://docs.google.com/forms/d/e/1FAIpQLSeTHFWEgYkcv6O5c9g8oSiMOgpxO7UHuDkSmgOJDPW9Le4LaQ/viewform + # - 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: "Tamerlan Abu" + linkedin: "https://www.linkedin.com/in/tamerlan-abu-8442191b1/" + - name: "Rustem Uspanov" + linkedin: "https://www.linkedin.com/in/ruspanov/" + - name: "Nurbek Sadykov" + linkedin: "https://www.linkedin.com/in/nurbeksadykov/" + - name: "Viktor Khomenko" + linkedin: "https://www.linkedin.com/company/devopsdays-almaty" + +organizer_email: "almaty@devopsdays.org" # Put your organizer email address here + +# List all of your sponsors here along with what level of sponsorship they have. +# Check data/sponsors/ to use sponsors already added by others. +sponsors: [] + +sponsors_accepted : "no" # 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 + - id: silver + label: Silver + # - id: bronze + # label: Bronze + - id: community + label: Community diff --git a/static/_redirects b/static/_redirects index c329411879..fa8ac1c103 100644 --- a/static/_redirects +++ b/static/_redirects @@ -174,7 +174,7 @@ /lima/* /events/2026-lima/:splat 302 /rosario/* /events/2020-rosario/:splat 302 /aarhus/* /events/2025-aarhus/:splat 302 -/almaty/* /events/2025-almaty/:splat 302 +/almaty/* /events/2026-almaty/:splat 302 /organizer-summit/* /events/2024-organiser-summit/:splat 302 /organiser-summit/cfp https://talks.devopsdays.org/organiser-summit-2024/cfp 302 /belo-horizonte/* /events/2026-belo-horizonte/:splat 302