|
1 | | -name: "2026-ciudad-autonoma-de-buenos-aires" # 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: "Ciudad Autonoma de Buenos Aires" # The displayed city name of the event. Capitalize it. |
4 | | -event_twitter: "devopsdaysba" # Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp |
5 | | -description: "Devopsdays is coming to Ciudad Autonoma de Buenos Aires!" # 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 2026-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 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) |
12 | | - |
13 | | -startdate: 2026-04-09T08:00:00-03:00 |
14 | | -enddate: 2026-04-10T18:00:00-03:00 |
15 | | - |
16 | | -# Leave CFP dates blank if you don't know yet, or set all three at once. |
17 | | -cfp_date_start: # start accepting talk proposals. |
18 | | -cfp_date_end: # close your call for proposals. |
19 | | -cfp_date_announce: # inform proposers of status |
20 | | - |
21 | | -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 | | - |
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. |
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. |
| 1 | +name: "2026-ciudad-autonoma-de-buenos-aires" |
| 2 | +year: "2026" |
| 3 | +city: "Ciudad Autonoma de Buenos Aires" |
| 4 | +event_twitter: "devopsdaysba" |
| 5 | +description: "DevOpsDays Buenos Aires 2026 - La conferencia de DevOps mas importante de Argentina" |
| 6 | +ga_tracking_id: "" |
| 7 | + |
| 8 | +# All dates are in unquoted YYYY-MM-DDTHH:MM:SS+TZ:TZ format |
| 9 | +startdate: 2026-04-09T08:00:00-03:00 |
| 10 | +enddate: 2026-04-10T18:00:00-03:00 |
| 11 | + |
| 12 | +# CFP configuration |
| 13 | +cfp_date_start: 2025-10-01T00:00:00-03:00 |
| 14 | +cfp_date_end: 2026-02-28T23:59:59-03:00 |
| 15 | +cfp_date_announce: 2026-03-15T09:00:00-03:00 |
| 16 | +cfp_link: "https://devopsdaysba.com/#/cfp" |
| 17 | + |
| 18 | +# Registration |
| 19 | +registration_date_start: |
| 20 | +registration_date_end: |
| 21 | +registration_closed: "" |
| 22 | +registration_link: "https://devopsdaysba.com/#/registration" |
28 | 23 |
|
29 | 24 | # Location |
30 | | -# |
31 | | -# coordinates: "" # No longer used |
32 | | - |
33 | | -location: "Ciudad Autonoma de Buenos Aires" # Defaults to city, but you can make it the venue name. |
34 | | -# |
35 | | -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! |
| 25 | +location: "Ciudad Autonoma de Buenos Aires" |
| 26 | +location_address: "" |
36 | 27 |
|
37 | | -# Optional - Social badges |
38 | | -# These can be used in the body of any page via matching shortcodes. See sample: https://devopsdays.org/events/2025-denver/welcome/ |
39 | | -#event_social_linkedin: "https://linkedin.com/company/devopsdaysba" # Change this to the url to your Linkedin group, company, or page. |
40 | | -#event_social_slack: "https://join.slack.com/t/devopsdaysba/custom_shared_invite_url" # Change this to your slack invite link. |
41 | | -#event_social_listserv: "https://lists.devopsdays.org/subscription?custom_listserv_invite_url" # Change this to your mailing list subscription form url. |
42 | | -#event_social_twitter: "devopsdaysba" # Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp |
43 | | -#event_social_mastodon: "https://mastodon.social/@devopsdaysba" # Change this to url to your mastodon page |
44 | | -#event_social_bsky: "https://bsky.app/profile/devopsdaysba.bsky.social" # Change this to url to your bluesky page |
45 | | -#event_social_youtube: "devopsdaysba" # Change this to the youtube channel handle for your event such as devopsdaysrox |
46 | | -# legacy |
47 | | -#event_twitter: "devopsdaysba" # This will create a traditional "Follow" twitter button. Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp. |
| 28 | +# Social |
| 29 | +event_social_linkedin: "https://www.linkedin.com/company/devopsdaysba" |
| 30 | +event_social_twitter: "devopsdaysba" |
48 | 31 |
|
49 | | -nav_elements: # List of pages you want to show up in the navigation of your page. |
50 | | - # - name: propose |
51 | | - # - name: location |
52 | | - # - name: registration |
53 | | - # - name: program |
54 | | - # - name: speakers |
| 32 | +# Navigation |
| 33 | +nav_elements: |
| 34 | + - name: propose |
| 35 | + - name: location |
55 | 36 | - name: sponsor |
56 | 37 | - name: contact |
57 | 38 | - name: conduct |
58 | | -# - name: example |
59 | | -# icon: "map-o" # This is a font-awesome icon that will display on small screens. Choose at http://fontawesome.io/icons/ |
60 | | -# url: http://mycfp.com # The url setting is optional, and only if you want the navigation to link off-site |
| 39 | + - name: devopsdaysba.com |
| 40 | + url: https://devopsdaysba.com |
61 | 41 |
|
62 | | - |
63 | | -# These are the same people you have on the mailing list and Slack channel. |
64 | | -team_members: # Name is the only required field for team members. |
| 42 | +# Team members |
| 43 | +team_members: |
65 | 44 | - name: "Axel Labruna" |
| 45 | + role: "Solutions Architect" |
66 | 46 | linkedin: "https://www.linkedin.com/in/axelglabruna/" |
67 | | - - name: "Rossana Suarex" |
68 | | - - name: "Eduardo Spotti" |
69 | | - linkedin: "https://www.linkedin.com/in/eduardo-spotti/" |
| 47 | + image: "axel-labruna.jpg" |
| 48 | + bio: "DevOps Institute Ambassador. Transformando empresas tradicionales en organizaciones tech-first. +7 años de experiencia en DevOps, Cloud y arquitectura de soluciones." |
70 | 49 | - name: "Maika Esteves" |
| 50 | + role: "DevOps Engineer" |
| 51 | + linkedin: "https://www.linkedin.com/in/maikaesteves/" |
| 52 | + image: "maika-esteves.jpg" |
| 53 | + bio: "AWS Certified Cloud Practitioner. Especialista en DevSecOps, Cloud y contenedores." |
71 | 54 | - name: "Matias Armandola" |
| 55 | + role: "Cybersecurity & DevOps" |
| 56 | + linkedin: "https://www.linkedin.com/in/matiarmandola/" |
| 57 | + twitter: "matiarman" |
| 58 | + image: "matias-armandola.jpg" |
| 59 | + bio: "+10 años en tecnologia y ciberseguridad. Profesor de AWS y Cybersecurity en Coderhouse." |
72 | 60 | - name: "Martin Calderon" |
73 | | - linkedin: "www.linkedin.com/in/martin369" |
74 | | - |
| 61 | + role: "Chief AI Officer" |
| 62 | + linkedin: "https://www.linkedin.com/in/martin369/" |
| 63 | + image: "martin-calderon.jpg" |
| 64 | + bio: "Microsoft Certified DevOps Engineer Expert. Lider de equipos agiles multidisciplinarios." |
| 65 | + - name: "Rossana Suarez" |
| 66 | + role: "DevOps/DevSecOps Engineer" |
| 67 | + employer: "Naranja X" |
| 68 | + linkedin: "https://www.linkedin.com/in/roxsross/" |
| 69 | + image: "rossana-suarez.jpg" |
| 70 | + bio: "Tech Lead y DevSecOps Engineer con amplia experiencia en automatizacion y seguridad." |
| 71 | + - name: "Eduardo Spotti" |
| 72 | + role: "CEO" |
| 73 | + employer: "Crubyt" |
| 74 | + linkedin: "https://www.linkedin.com/in/eduardo-spotti/" |
| 75 | + image: "eduardo-spotti.jpg" |
| 76 | + bio: "AWS Certified Solutions Architect y Microsoft Certified Professional." |
75 | 77 |
|
76 | | -organizer_email: "buenos-aires@devopsdays.org" # Put your organizer email address here |
| 78 | +organizer_email: "buenos-aires@devopsdays.org" |
77 | 79 |
|
78 | | -# List all of your sponsors here along with what level of sponsorship they have. |
79 | | -# Check data/sponsors/ to use sponsors already added by others. |
| 80 | +# Sponsors |
80 | 81 | sponsors: |
81 | | - #- id: samplesponsorname |
82 | | - # level: gold |
83 | | - # url: http://mysponsor.com/?campaign=me # Use this if you need to over-ride a sponsor URL. |
84 | 82 | - id: arresteddevops |
85 | 83 | level: community |
86 | 84 |
|
87 | | -sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link |
| 85 | +sponsors_accepted: "yes" |
88 | 86 |
|
89 | | -# In this section, list the level of sponsorships and the label to use. |
90 | | -# You may optionally include a "max" attribute to limit the number of sponsors per level. For |
91 | | -# unlimited sponsors, omit the max attribute or set it to 0. If you want to prevent all |
92 | | -# sponsorship for a specific level, it is best to remove the level. |
93 | 87 | sponsor_levels: |
94 | 88 | - id: gold |
95 | 89 | label: Gold |
96 | | -# max: 10 |
97 | 90 | - id: silver |
98 | 91 | label: Silver |
99 | | - max: 0 # This is the same as omitting the max limit. |
100 | 92 | - id: bronze |
101 | 93 | label: Bronze |
102 | 94 | - id: community |
|
0 commit comments