Skip to content

Commit b809f09

Browse files
committed
feat: add initial information for the 2026 event
1 parent c790645 commit b809f09

File tree

18 files changed

+105
-0
lines changed

18 files changed

+105
-0
lines changed
391 KB
Loading
34.9 KB
Loading
47.5 KB
Loading
58.8 KB
Loading
15.4 KB
Loading
3.57 KB
Loading
63.2 KB
Loading
14.8 KB
Loading
78.5 KB
Loading

data/events/2026/curitiba/main.yml

Lines changed: 105 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,105 @@
1+
name: "2026-curitiba" # The name of the event. Four digit year with the city name in lower-case, with no spaces.
2+
year: "2026" # The year of the event. Make sure it is in quotes.
3+
city: "Curitiba" # The displayed city name of the event. Capitalize it.
4+
event_twitter: "devopsdays" # Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp
5+
description: "Devopsdays acontece novamente em Curitiba! 2026!" # Edit this to suit your preferences
6+
ga_tracking_id: "" # If you have your own Google Analytics tracking ID, enter it here. Example: "UA-74738648-1"
7+
8+
# All dates are in unquoted 2024-MM-DDTHH:MM:SS+TZ:TZ, like this:
9+
# variable: 2019-01-04T00:00:00+02:00
10+
# variable: 2019-01-05T23:59:59+02:00
11+
# Note: we allow 2024-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+
13+
startdate: 2026-08-29
14+
enddate: 2026-08-29 # The end date of your event. Leave blank if you don't have a venue reserved yet.
15+
16+
# Leave CFP dates blank if you don't know yet, or set all three at once.
17+
cfp_date_start: 2026-05-04
18+
cfp_date_end: 2026-06-04 # close your call for proposals.
19+
cfp_date_announce: 2026-07-01 # inform proposers of status
20+
21+
cfp_link: "https://docs.google.com/forms/d/e/1FAIpQLSddRAG5k1SHRkjVjKRmC-zLdSzd0TMJhdVGFute9C7tYFU4jA/viewform" #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+
23+
registration_date_start: 2026-07-27 # 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: 2026-08-29 # close registration. Leave blank if registration is not open yet. If you set "registration_date_start" you need a value here.
25+
26+
registration_closed: "" #set this to true if you need to manually close registration before your registration end date
27+
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.
28+
29+
# Location
30+
#
31+
# coordinates: "" # No longer used
32+
33+
location: "Curitiba" # Defaults to city, but you can make it the venue name.
34+
#
35+
location_address: "A definir - Curitiba/PR" #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+
37+
nav_elements: # List of pages you want to show up in the navigation of your page.
38+
- name: propose
39+
- name: location
40+
- name: registration
41+
- name: program
42+
- name: speakers
43+
- name: sponsor
44+
- name: contact
45+
- name: conduct
46+
# - name: example
47+
# icon: "map-o" # This is a font-awesome icon that will display on small screens. Choose at http://fontawesome.io/icons/
48+
# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site
49+
50+
51+
# These are the same people you have on the mailing list and Slack channel.
52+
team_members: # Name is the only required field for team members.
53+
- name: "Alex Mazur"
54+
employer: "ThoughtWorks"
55+
linkedin: "https://www.linkedin.com/in/alex-mazur"
56+
image: "alex.jpeg"
57+
- name: "Daniel Lenharo de Souza"
58+
employer: "CELEPAR"
59+
linkedin: "https://www.linkedin.com/in/daniel-lenharo-de-souza-101197148/"
60+
image: "daniel.jpeg"
61+
- name: "Emerson Sachio Saito"
62+
employer: "SERPRO"
63+
linkedin: "https://www.linkedin.com/in/emerson-sachio-saito"
64+
image: "emerson.png"
65+
github: "esaito"
66+
- name: "Fabiano Sardenberg Kuss"
67+
employer: "SERPRO"
68+
linkedin: "https://www.linkedin.com/in/fabiano-kuss-37742956/"
69+
image: "fabiano.jpeg"
70+
- name: "Marcelo Baptista"
71+
employer: "C6 Bank"
72+
linkedin: "https://www.linkedin.com/in/marcelocbaptista"
73+
image: "marcelo.jpeg"
74+
- name: "Rui Valim Júnior"
75+
employer: "NT Consult"
76+
linkedin: "https://www.linkedin.com/in/rui-valim"
77+
image: "rui.jpeg"
78+
79+
organizer_email: "[email protected]" # Put your organizer email address here
80+
81+
# List all of your sponsors here along with what level of sponsorship they have.
82+
# Check data/sponsors/ to use sponsors already added by others.
83+
sponsors:
84+
- id: NimbleEvolution
85+
level: Silver
86+
url: https://br.nimbleevolution.com
87+
88+
sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link
89+
90+
# In this section, list the level of sponsorships and the label to use.
91+
# You may optionally include a "max" attribute to limit the number of sponsors per level. For
92+
# unlimited sponsors, omit the max attribute or set it to 0. If you want to prevent all
93+
# sponsorship for a specific level, it is best to remove the level.
94+
sponsor_levels:
95+
- id: gold
96+
label: Gold
97+
max: 4
98+
- id: silver
99+
label: Silver
100+
max: 6 # This is the same as omitting the max limit.
101+
- id: bronze
102+
label: Bronze
103+
max: 10
104+
- id: community
105+
label: Community

0 commit comments

Comments
 (0)