You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/events/2025-denver/propose.md
+7-8Lines changed: 7 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,13 +5,17 @@ Description = "Propose a talk for devopsdays Denver 2025"
5
5
+++
6
6
{{< cfp_dates >}}
7
7
8
+
<center>
9
+
<h2><ahref="https://talks.devopsdays.org/dodrox-2025/cfp"style="font-size: 1.5em; padding: 510px;text-decoration: none; border-radius: 5px;">>>> Submit your proposal here <<<</a></h2>
10
+
</center>
11
+
8
12
<hr>
9
13
10
14
There are three ways to propose a topic at devopsdays:
11
15
<ol>
12
16
<li><strong><em>A 30-minute talk</em></strong> presented during the conference, usually in the mornings.</li>
13
-
<li><strong><em>An Ignite talk</em></strong> presented during the <ahref="/pages/ignite-talks-format">Ignite sessions</a> (scheduling varies). These are 5 minutes slots with slides changing every 15 seconds (20 slides total).</li>
14
-
<li><strong><em>Open Space</em></strong>: If you'd like to lead a group discussion during the attendee-suggested <ahref="/pages/open-space-format">Open Space</a> 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 <ahref="../sponsor">sponsor the event</a> and demo it at your table.
17
+
<li><strong><em>An Ignite talk</em></strong> presented during the <ahref="/pages/ignite-talks-format">Ignite sessions</a> (scheduling varies). These are 5 minutes slots with slides auto-advancing every 15 seconds (20 slides total).</li>
18
+
<li><strong><em>Open Space</em></strong>: It is not necessary to submit a proposal ahead of time if you'd like to lead a group discussion during the attendee-suggested <ahref="/pages/open-space-format">Open Space</a> breakout sessions. Those topics are suggested in person at the conference. If you'd like to demo your product or service, you should <ahref="../sponsor">sponsor the event</a> and demo it at your table.
15
19
</ol>
16
20
17
21
<hr>
@@ -27,9 +31,4 @@ Choosing talks is part art, part science; here are some factors we consider when
27
31
28
32
<hr>
29
33
30
-
<strong>How to submit a proposal:</strong> Send an email to [{{< email_organizers >}}] with the following information
Copy file name to clipboardExpand all lines: content/events/2025-denver/sponsor.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ Type = "event"
4
4
Description = "Sponsor devopsdays Denver 2025"
5
5
+++
6
6
7
-
We greatly value sponsors for this open event. If you are interested in sponsoring, please drop us an email at [{{< email_organizers >}}].
7
+
We greatly value sponsors for this open event. If you are interested in sponsoring, please check out our <ahref="https://drive.google.com/file/d/1AUVmUEWK9QMUhirWA-U5rla4SHQam-gR/view?usp=drive_link">prospectus</a> and drop us an email at [{{< email_organizers >}}].
Copy file name to clipboardExpand all lines: data/events/2025/denver/main.yml
+23-33Lines changed: 23 additions & 33 deletions
Original file line number
Diff line number
Diff line change
@@ -1,43 +1,48 @@
1
1
name: "2025-denver"# The name of the event. Four digit year with the city name in lower-case, with no spaces.
2
2
year: "2025"# The year of the event. Make sure it is in quotes.
3
3
city: "Denver"# The displayed city name of the event. Capitalize it.
4
-
event_twitter: "DevOpsDaysRox"# Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp
5
-
description: "Devopsdays is coming to Denver!"# Edit this to suit your preferences
4
+
description: "Devopsdays is returning to Denver for "# Edit this to suit your preferences
6
5
ga_tracking_id: "G-9SR9GD94E0"# If you have your own Google Analytics tracking ID, enter it here. Example: "UA-74738648-1"
7
6
8
7
# All dates are in unquoted 2025-MM-DDTHH:MM:SS+TZ:TZ, like this:
9
8
# variable: 2019-01-04T00:00:00+02:00
10
9
# variable: 2019-01-05T23:59:59+02:00
11
10
# 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)
12
11
13
-
startdate: # The start date of your event. Leave blank if you don't have a venue reserved yet.
14
-
enddate: # The end date of your event. Leave blank if you don't have a venue reserved yet.
12
+
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.
13
+
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.
15
14
16
15
# Leave CFP dates blank if you don't know yet, or set all three at once.
cfp_date_end: 2025-05-25T23:59:59-06:00# close your call for proposals.
18
+
cfp_date_announce: 2025-06-15T08:00:59-06:00# inform proposers of status
20
19
21
20
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.
22
21
23
-
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.
24
-
registration_date_end: # close registration. Leave blank if registration is not open yet. If you set "registration_date_start" you need a value here.
22
+
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.
23
+
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.
25
24
26
25
registration_closed: ""#set this to true if you need to manually close registration before your registration end date
27
26
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: "Denver"# Defaults to city, but you can make it the venue name.
38
+
location: "Downtown Denver"# Defaults to city, but you can make it the venue name.
34
39
#
35
40
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!
36
41
37
42
nav_elements: # List of pages you want to show up in the navigation of your page.
38
-
# - name: propose
43
+
- name: propose
39
44
# - name: location
40
-
# - name: registration
45
+
- name: registration
41
46
# - name: program
42
47
# - name: speakers
43
48
- name: sponsor
@@ -50,13 +55,6 @@ nav_elements: # List of pages you want to show up in the navigation of your page
50
55
51
56
# These are the same people you have on the mailing list and Slack channel.
52
57
team_members: # Name is the only required field for team members.
53
-
- name: "Tavis Aitken"
54
-
twitter: "tavisto"
55
-
employer: "Splunk"
56
-
mastodon: "https://hachyderm.io/@tavisto"
57
-
- name: "Carla Murray"
58
-
employer: "Splunk"
59
-
twitter: "carlajmurray"
60
58
- name: "Keri Melich"
61
59
employer: "DuckDuckGo"
62
60
twitter: "themightymuppet"
@@ -66,21 +64,13 @@ team_members: # Name is the only required field for team members.
0 commit comments