diff --git a/content/events/2025-denver/propose.md b/content/events/2025-denver/propose.md index 898e515b642..5d41419f022 100644 --- a/content/events/2025-denver/propose.md +++ b/content/events/2025-denver/propose.md @@ -5,13 +5,17 @@ Description = "Propose a talk for devopsdays Denver 2025" +++ {{< cfp_dates >}} +
+

>>> Submit your proposal here <<<

+
+
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. +
  4. An Ignite talk presented during the Ignite sessions (scheduling varies). These are 5 minutes slots with slides auto-advancing every 15 seconds (20 slides total).
    5. +
  5. Open Space: It is not necessary to submit a proposal ahead of time if you'd like to lead a group discussion during the attendee-suggested Open Space breakout sessions. 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.
@@ -27,9 +31,4 @@ Choosing talks is part art, part science; here are some factors we consider when
-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. -
+Have a question about CFPs or need help? Send us an email at [{{< email_organizers >}}]. We're here to help! diff --git a/content/events/2025-denver/registration.md b/content/events/2025-denver/registration.md index ca6387da3cb..8b575feed24 100644 --- a/content/events/2025-denver/registration.md +++ b/content/events/2025-denver/registration.md @@ -6,6 +6,6 @@ Description = "Registration for devopsdays Denver 2025"
-Embed registration iframe/link/etc. +{{< tix city="denver" year="2025" info="show" >}}
diff --git a/content/events/2025-denver/sponsor.md b/content/events/2025-denver/sponsor.md index afec5b6224d..791a74fa974 100644 --- a/content/events/2025-denver/sponsor.md +++ b/content/events/2025-denver/sponsor.md @@ -4,7 +4,7 @@ Type = "event" Description = "Sponsor devopsdays Denver 2025" +++ -We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}]. +We greatly value sponsors for this open event. If you are interested in sponsoring, please check out our prospectus and drop us an email at [{{< email_organizers >}}].
diff --git a/content/events/2025-denver/welcome.md b/content/events/2025-denver/welcome.md index 2e12eb85195..6169b815639 100644 --- a/content/events/2025-denver/welcome.md +++ b/content/events/2025-denver/welcome.md @@ -5,89 +5,93 @@ aliases = ["/events/2025-denver/"] Description = "devopsdays Denver 2025" +++ -Stay tuned for more details on DevOpsDays Denver 2025! - -
+
- +
-
-{{< event_twitter >}} -
- -
-Join us on Slack! -
+DevOpsDays Rockies is returning to Denver in 2025!

+Here's what we know so far:
- +
- + - + - + - + - - -
+
+
+
+We're hard at work preparing for the big event and we're looking forward to seeing y'all there!
+In the meantime, follow us below to stay in the know: +
+{{< event_social_linkedin >}} +{{< event_social_listserv >}} +{{< event_social_slack >}} +{{< event_social_twitter >}} +{{< event_social_youtube >}} +
+

+ -
+ diff --git a/data/events/2025/denver/main.yml b/data/events/2025/denver/main.yml index 1f6e190bbc7..886718c3a22 100644 --- a/data/events/2025/denver/main.yml +++ b/data/events/2025/denver/main.yml @@ -1,8 +1,7 @@ name: "2025-denver" # 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: "Denver" # The displayed city name of the event. Capitalize it. -event_twitter: "DevOpsDaysRox" # Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp -description: "Devopsdays is coming to Denver!" # Edit this to suit your preferences +description: "Devopsdays is returning to Denver for " # Edit this to suit your preferences ga_tracking_id: "G-9SR9GD94E0" # If you have your own Google Analytics tracking ID, enter it here. Example: "UA-74738648-1" # All dates are in unquoted 2025-MM-DDTHH:MM:SS+TZ:TZ, like this: @@ -10,34 +9,40 @@ ga_tracking_id: "G-9SR9GD94E0" # If you have your own Google Analytics tracking # 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: # 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: 2025-09-15T08:00:59-06:00 # The start date of your event. Leave blank if you don't have a venue reserved yet. +enddate: 2025-09-16T23:59:59-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: # start accepting talk proposals. -cfp_date_end: # close your call for proposals. -cfp_date_announce: # inform proposers of status +cfp_date_start: 2025-02-22T08:00:59-06:00 # start accepting talk proposals. +cfp_date_end: 2025-05-25T23:59:59-06:00 # close your call for proposals. +cfp_date_announce: 2025-06-15T08:00:59-06:00 # 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_date_start: 2025-02-22T08:00:59-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: 2025-09-15T23:59:59-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: "" # If you have a custom registration link, enter it here. This will control the Registration menu item as well as the "Register" button. +event_social_linkedin: "https://www.linkedin.com/company/devopsdaysrox/" +event_social_slack: "https://join.slack.com/t/denverdevops/shared_invite/zt-1vh386cqp-Y_YUcLvFTeuOXA1~zIHUPQ" +event_social_listserv: "https://lists.devopsdays.org/subscription?f=nPvKqspePofE0XidlymcAeU1dXc7633G7Gu0OOZmi7rYef45qeLCpMqcaXD4kQpNJ1xP21UP58763qC0763Sx3763zWJbw" +event_social_twitter: "DevOpsDaysRox" +event_social_youtube: "devopsdaysrockies" + # Location # # coordinates: "" # No longer used -location: "Denver" # Defaults to city, but you can make it the venue name. +location: "Downtown Denver" # 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! 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: registration # - name: program # - name: speakers - name: sponsor @@ -50,13 +55,6 @@ nav_elements: # List of pages you want to show up in the navigation of your page # 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: "Tavis Aitken" - twitter: "tavisto" - employer: "Splunk" - mastodon: "https://hachyderm.io/@tavisto" - - name: "Carla Murray" - employer: "Splunk" - twitter: "carlajmurray" - name: "Keri Melich" employer: "DuckDuckGo" twitter: "themightymuppet" @@ -66,21 +64,13 @@ team_members: # Name is the only required field for team members. twitter: "peteroneilljr" - name: "Mike Nabhan" employer: "Akamai" - - name: "David Morse" - employer: "Parry Labs" - twitter: "ds_morse" - - name: "Matt Knox" - twitter: "mknox42" + - name: "Tavis Aitken" + twitter: "tavisto" employer: "Splunk" - - name: "Beau Christensen" - twitter: "beauchristensen" - mastodon: "https://hachyderm.io/@e30m3" - employer: "Rivian" - - name: "Nick Huanca" - twitter: "NickHuanca" - - name: "Leigh Capili" - employer: "Flox" - twitter: "capileigh" + mastodon: "https://hachyderm.io/@tavisto" + - name: "Carla Murray" + employer: "Splunk" + twitter: "carlajmurray" organizer_email: "denver@devopsdays.org" # List all of your sponsors here along with what level of sponsorship they have.