|
| 1 | +name: "2026-tokyo" # 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: "Tokyo" # The displayed city name of the event. Capitalize it. |
| 4 | +description: "Devopsdays is coming to Tokyo!" # Edit this to suit your preferences |
| 5 | +ga_tracking_id: "" # If you have your own Google Analytics tracking ID, enter it here. Example: "UA-74738648-1" |
| 6 | + |
| 7 | +# All dates are in unquoted 2026-MM-DDTHH:MM:SS+TZ:TZ, like this: |
| 8 | +# variable: 2019-01-04T00:00:00+02:00 |
| 9 | +# variable: 2019-01-05T23:59:59+02:00 |
| 10 | +# 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) |
| 11 | + |
| 12 | +startdate: 2026-04-14T00:00:00+09:00 |
| 13 | +enddate: 2026-04-16T23:59:59+09:00 |
| 14 | + |
| 15 | +# Leave CFP dates blank if you don't know yet, or set all three at once. |
| 16 | +cfp_date_start: 2025-11-01T00:00:00+09:00 |
| 17 | +cfp_date_end: 2026-03-01T13:00:00+09:00 # close your call for proposals. |
| 18 | +cfp_date_announce: 2026-03-15T00:00:00+09:00 # inform proposers of status |
| 19 | + |
| 20 | +cfp_link: "https://www.devopsdaystokyo.org/" #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. |
| 21 | + |
| 22 | +registration_date_start: 2025-11-01T00:00:00+09:00 |
| 23 | +registration_date_end: 2026-04-16T23:59:59+09:00 |
| 24 | + |
| 25 | +registration_closed: "" #set this to true if you need to manually close registration before your registration end date |
| 26 | +registration_link: "https://pretix.eu/devopsdaystokyo/2026/" |
| 27 | + |
| 28 | +# Location |
| 29 | +# |
| 30 | +# coordinates: "" # No longer used |
| 31 | + |
| 32 | +location: "大崎ブライトコアホール" # Defaults to city, but you can make it the venue name. |
| 33 | +# |
| 34 | +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! |
| 35 | + |
| 36 | +# Optional - Social badges |
| 37 | +# These can be used in the body of any page via matching shortcodes. See sample: https://devopsdays.org/events/2025-denver/welcome/ |
| 38 | +event_social_linkedin: "https://linkedin.com/company/devopsdays" # Change this to the url to your Linkedin group, company, or page. |
| 39 | +event_social_slack: "https://join.slack.com/t/devopsdays/custom_shared_invite_url" # Change this to your slack invite link. |
| 40 | +event_social_listserv: "https://lists.devopsdays.org/subscription?custom_listserv_invite_url" # Change this to your mailing list subscription form url. |
| 41 | +event_social_twitter: "devopsdays" # Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp |
| 42 | +event_social_mastodon: "https://mastodon.social/@devopsdays" # Change this to url to your mastodon page |
| 43 | +event_social_bsky: "https://bsky.app/profile/devopsdays.bsky.social" # Change this to url to your bluesky page |
| 44 | +event_social_youtube: "devopsdays" # Change this to the youtube channel handle for your event such as devopsdaysrox |
| 45 | +# legacy |
| 46 | +event_twitter: "devopsdays" # This will create a traditional "Follow" twitter button. Change this to the twitter handle for your event such as devopsdayschi or devopsdaysmsp. |
| 47 | + |
| 48 | +nav_elements: # List of pages you want to show up in the navigation of your page. |
| 49 | + - name: devopsdaystokyo.org |
| 50 | + url: https://www.devopsdaystokyo.org/ |
| 51 | + - name: contact |
| 52 | + - name: conduct |
| 53 | + |
| 54 | +# These are the same people you have on the mailing list and Slack channel. |
| 55 | +team_members: # Name is the only required field for team members. |
| 56 | + - name: "Ippei Suzuki" |
| 57 | + employer: "Creationline" |
| 58 | + - name: "Alex Papadimoulis" |
| 59 | + employer: "Inedo" |
| 60 | + twitter: "apxld" |
| 61 | + - name: "Sho Sato" |
| 62 | + employer: "Inedo" |
| 63 | + - name: "Yasunobu Kawaguchi" |
| 64 | + employer: "Attractor" |
| 65 | + - name: "Hiro Arai" |
| 66 | + employer: "Creationline" |
| 67 | + - name: "Tadahiro Yasuda" |
| 68 | + employer: "Creationline" |
| 69 | + - name: "Kenta Sasa" |
| 70 | + employer: "Creationline" |
| 71 | + - name: "Muneyuki Okamoto" |
| 72 | + employer: "ITPreneurs Japan" |
| 73 | + - name: "Toshiya Enami" |
| 74 | + employer: "ITPreneurs Japan" |
| 75 | + |
| 76 | +organizer_email: "tokyo@devopsdays.org" # Put your organizer email address here |
| 77 | + |
| 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: |
| 81 | + |
| 82 | +sponsors_accepted : "yes" # Whether you want "Become a XXX Sponsor!" link |
| 83 | + |
| 84 | +# In this section, list the level of sponsorships and the label to use. |
| 85 | +# You may optionally include a "max" attribute to limit the number of sponsors per level. For |
| 86 | +# unlimited sponsors, omit the max attribute or set it to 0. If you want to prevent all |
| 87 | +# sponsorship for a specific level, it is best to remove the level. |
| 88 | +sponsor_levels: |
| 89 | + - id: gold |
| 90 | + label: Gold |
| 91 | + max: 8 |
| 92 | + - id: logo |
| 93 | + label: Logo |
| 94 | + max: 10 |
| 95 | + |
0 commit comments