main.yml

name: "2026-lima" # 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: "lima" # 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: "Devopsdays is coming to lima!" # 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"
event_logo: "logo-square.png"

# 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-08-27T00:10:00+05:00"  # The start date of your event. Leave blank if you don't have a venue reserved yet.
enddate: "2026-08-28T00:18:00+05: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:  "2025-03-06T12:00:00-05:00"
cfp_date_end:  "2025-05-30T12:00:00-05:00"
cfp_date_announce: "2025-06-15T12:00:00-05:00"

cfp_link: "https://talks.devopsdays.org/devopsdays-lima-2026/cfp" #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.

masthead_background: "lima-banner-masthead.png"

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_closed: "" #set this to true if you need to manually close registration before your registration end date
registration_link: "https://tickets.devopsdays.pe/" # 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: "Lima Convention Center - LCC" # Defaults to city, but you can make it the venue name.
#
location_address: "Av. de la Arqueología 206, San Borja 15021" #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://www.linkedin.com/company/devops-days-lima" # Change this to the url to your Linkedin group, company, or page.
event_social_youtube: "DevOpsDaysLima" # Change this to the youtube channel handle for your event such as devopsdaysrox
# Social Share Buttons
# Optional: Specify which social share buttons to display on event pages.
# If not specified, defaults to all: ["email", "twitter", "facebook", "linkedin"]
# Valid values: "email", "twitter", "facebook", "linkedin"
# Example: social_shares: ["email", "linkedin"]  # Only show email and LinkedIn share buttons
social_shares: # ["email", "twitter", "facebook", "linkedin"]

nav_elements: # List of pages you want to show up in the navigation of your page.
  - name: devopsdays.pe
    url: https://devopsdays.pe/
  - name: propose
  - 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: "Lenard Vega"
    email: "levegav@gmail.com"
    employer: "Credicorp"
    linkedin: "https://www.linkedin.com/in/lenardvega/"
    bio: "Corporate DevSecOps Lead"
    github: "lvega-root"
    image: "lenard-vega.jpg"
  - name: "Diana Uriol"
    email: "dianaeu.0925@gmail.com"
    employer: "Interbank"
    bio: "Agile Team Facilitator"
    linkedin: https://www.linkedin.com/in/diana-uriol-more-88a62848/
    image: "diana-uriol.jpg"
  - name: "Danilo Briceño"
    email: "danilobe@ekiscyber.com"
    employer: "EKIS Cyber"
    twitter: "dan_breu"
    linkedin: "https://www.linkedin.com/in/danbreu/"
    bio: "CXO"
    image: "danilo-briceno.jpg"
    github: "dan-breu"
  - name: "Gino Leon"
    email: "gleongo@gmail.com"
    employer: "Pacifico Seguros"
    linkedin: "https://www.linkedin.com/in/gino-leon-0217a23b/"
    bio: "Agile Chapter Lead"
    image: "gino-leon.jpg"
  - name: Fredy Hernandez
    email: "Ruggeri.hernandez@gmail.com"
    employer: "Tyba"
    linkedin: "https://www.linkedin.com/in/fredy-hernandez-huaricallo/"
    image: "fredy-hernandez.jpg"
    bio: "DevOps Engineer"
  - name: "Ronald Requena"
    email: "cronald@gmail.com"
    employer: "Rumbo"
    linkedin: "https://www.linkedin.com/in/rcronald"
    image: "ronald-requena.jpg"
    bio: "CTO"
  - name: "Jhonnatan Correa Maguiña"
    bio: "Application Cybersecurity Specialist"
    employer: "SOAINT"
    linkedin: "https://www.linkedin.com/in/jhonnatancorrea/"
    image: "jhonnatan-correa.jpeg"
    github: "https://github.com/jhoncorrea"
  - name: "Stefani Sánchez"
    email: "ssancheza227@gmail.com"
    employer: "Santander Consumer Bank"
    bio: "Software Engineer"
    linkedin: "https://www.linkedin.com/in/stefani-janet-s%C3%A1nchez-asto"
    image: "stefani-sanchez.jpg"

organizer_email: "lima@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:
 #  url: http://mysponsor.com/?campaign=me # Use this if you need to over-ride a sponsor URL.
#Platinum Sponsors
   - id: dynatrace
     level: platinum
     url: https://www.dynatrace.com/es-la/
   - id: cleverit
     level: platinum
     url: https://www.cleveritgroup.com/
   - id: nttdata
     level: platinum
     url: https://pe.nttdata.com/
   - id: port
     level: platinum
     url: https://www.port.io/
   - id: ibm
     level: platinum
     url: https://www.ibm.com
#Gold Sponsors
   - id: thoughtworks
     level: gold
     url: https://www.thoughtworks.com/
   - id: manage-engine
     level: gold
     url: https://manageengine.com/latam/
#Silver Sponsors
#Bronze Sponsors
   - id: orexe
     level: bronze
     url: https://orexe.pe/
#Community Sponsors
   - id: hackemate
     level: community
     url: https://www.youtube.com/@hackemate

sponsors_accepted : "yes" # 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: platinum
    label: Platinum
  - id: gold
    label: Gold
  - id: silver
    label: Silver
  - id: bronze
    label: Bronze
  - id: community
    label: Community