Skip to content

Commit 1c8fbfc

Browse files
a-vassea-vasse
committed
tokyo 2026
2 parents e8920a0 + 4e1d2ec commit 1c8fbfc

File tree

8 files changed

+133
-235
lines changed

8 files changed

+133
-235
lines changed

‎content/events/2026-tokyo/conduct.md‎

Lines changed: 28 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -1,28 +1,28 @@
1-
+++
2-
Title = "Conduct"
3-
Type = "event"
4-
Description = "Code of conduct for devopsdays Tokyo 2026"
5-
+++
6-
7-
8-
All attendees, speakers, sponsors, and volunteers at devopsdays Tokyo 2026 are required to agree with the following code of conduct. Organizers will enforce this code throughout the event. We are expecting cooperation from all participants to help ensure a safe environment for everybody.
9-
10-
### The Quick Version
11-
12-
Our conference is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion (or lack thereof), or technology choices. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks, workshops, parties, Twitter, and other online media. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
13-
14-
### The Less Quick Version
15-
16-
Harassment includes offensive verbal comments related to gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion, technology choices, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
17-
18-
Sponsors are also subject to the anti-harassment policy. In particular, sponsors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
19-
20-
If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
21-
22-
If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
23-
24-
Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
25-
26-
We expect participants to follow these rules at conference and workshop venues and conference-related social events.
27-
28-
_The devopsdays Tokyo 2026 Code of Conduct is based on [confcodeofconduct.com](https://confcodeofconduct.com)._
1+
+++
2+
Title = "Conduct"
3+
Type = "event"
4+
Description = "Code of conduct for devopsdays Tokyo 2026"
5+
+++
6+
7+
8+
All attendees, speakers, sponsors, and volunteers at devopsdays Tokyo 2026 are required to agree with the following code of conduct. Organizers will enforce this code throughout the event. We are expecting cooperation from all participants to help ensure a safe environment for everybody.
9+
10+
### The Quick Version
11+
12+
Our conference is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion (or lack thereof), or technology choices. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not appropriate for any conference venue, including talks, workshops, parties, Twitter, and other online media. Conference participants violating these rules may be sanctioned or expelled from the conference without a refund at the discretion of the conference organizers.
13+
14+
### The Less Quick Version
15+
16+
Harassment includes offensive verbal comments related to gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion, technology choices, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
17+
18+
Sponsors are also subject to the anti-harassment policy. In particular, sponsors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
19+
20+
If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
21+
22+
If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff immediately.
23+
24+
Conference staff can be identified by distinct staff badges. Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.
25+
26+
We expect participants to follow these rules at conference and workshop venues and conference-related social events.
27+
28+
_The devopsdays Tokyo 2026 Code of Conduct is based on [confcodeofconduct.com](https://confcodeofconduct.com)._

‎content/events/2026-tokyo/contact.md‎

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
1-
+++
2-
Title = "Contact"
3-
Type = "event"
4-
Description = "Contact information for devopsdays Tokyo 2026"
5-
+++
6-
7-
If you'd like to contact us by email: {{< email_organizers >}}
8-
9-
**Our local team**
10-
11-
{{< list_organizers >}}
12-
13-
14-
{{< list_core >}}
1+
+++
2+
Title = "Contact"
3+
Type = "event"
4+
Description = "Contact information for devopsdays Tokyo 2026"
5+
+++
6+
7+
If you'd like to contact us by email: {{< email_organizers >}}
8+
9+
**Our local team**
10+
11+
{{< list_organizers >}}
12+
13+
14+
{{< list_core >}}

‎content/events/2026-tokyo/location.md‎

Lines changed: 3 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -4,14 +4,7 @@ Type = "event"
44
Description = "Location for devopsdays Tokyo 2026"
55
+++
66

7-
Watch this space for information about the venue including address, map/direction, parking/transit, and any hotel details.
7+
[大崎ブライトコアホール (Osaki Bright Core Hall)](http://osaki-hall.jp/)
8+
東京都品川区北品川5丁目5-15
89

9-
<!-- Uncomment this only if you have set the coordinates for your location in the config yaml. Get Latitude and Longitude of a Point: http://itouchmap.com/latlong.html -->
10-
<!-- {{< event_map >}} -->
11-
12-
<!-- Edit and uncomment to let people know what accessibility features you have available -->
13-
<!--
14-
Example from Minneapolis 2020
15-
16-
We offer wheelchair-designated spaces, chairs, and standing options (with tall tables) in the mainstage session room; a quiet room; bathrooms labeled according to the facilities they contain; professional live captioning of mainstage sessions; ingredient labeling (based on data provided when registering); and private space (upon request) for those nursing. We'd also be happy to accommodate any other accessibility needs upon request: {{< email_organizers >}}
17-
-->
10+
<iframe src="https://www.google.com/maps/embed?pb=!1m14!1m8!1m3!1d3243.2193467560746!2d139.7294709!3d35.6223187!3m2!1i1024!2i768!4f13.1!3m3!1m2!1s0x0%3A0x7c3ee69c2c2142e6!2z5aSn5bSO44OW44Op44Kk44OI44Kz44Ki!5e0!3m2!1sen!2sjp!4v1486141716893" width="600" height="450" frameborder="0" style="border:0" allowfullscreen></iframe>

‎content/events/2026-tokyo/welcome.md‎

Lines changed: 87 additions & 87 deletions
Original file line numberDiff line numberDiff line change
@@ -1,87 +1,87 @@
1-
+++
2-
Title = "devopsdays Tokyo 2026"
3-
Type = "welcome"
4-
aliases = ["/events/2026-tokyo/"]
5-
Description = "devopsdays Tokyo 2026"
6-
+++
7-
8-
<!-- <div style="text-align:center;">
9-
{{< event_logo >}}
10-
</div> -->
11-
12-
<div class = "row">
13-
<div class = "col-md-2">
14-
<strong>Dates</strong>
15-
</div>
16-
<div class = "col-md-8">
17-
{{< event_start >}} - {{< event_end >}}
18-
</div>
19-
</div>
20-
21-
<!-- <div class = "row">
22-
<div class = "col-md-2">
23-
<strong>Location</strong>
24-
</div>
25-
<div class = "col-md-8">
26-
{{< event_location >}}
27-
</div>
28-
</div> -->
29-
30-
<!-- <div class = "row">
31-
<div class = "col-md-2">
32-
<strong>Register</strong>
33-
</div>
34-
<div class = "col-md-8">
35-
{{< event_link page="registration" text="Register to attend the conference!" >}}
36-
</div>
37-
</div> -->
38-
39-
<!-- <div class = "row">
40-
<div class = "col-md-2">
41-
<strong>Propose</strong>
42-
</div>
43-
<div class = "col-md-8">
44-
{{< event_link page="propose" text="Propose a talk!" >}}
45-
</div>
46-
</div> -->
47-
48-
<!-- <div class = "row">
49-
<div class = "col-md-2">
50-
<strong>Program</strong>
51-
</div>
52-
<div class = "col-md-8">
53-
View the {{< event_link page="program" text="program." >}}
54-
</div>
55-
</div> -->
56-
57-
<!-- <div class = "row">
58-
<div class = "col-md-2">
59-
<strong>Speakers</strong>
60-
</div>
61-
<div class = "col-md-8">
62-
Check out the {{< event_link page="speakers" text="speakers!" >}}
63-
</div>
64-
</div> -->
65-
66-
<div class = "row">
67-
<div class = "col-md-2">
68-
<strong>Sponsors</strong>
69-
</div>
70-
<div class = "col-md-8">
71-
{{< event_link page="sponsor" text="Sponsor the conference!" >}}
72-
</div>
73-
</div>
74-
75-
<div class = "row">
76-
<div class = "col-md-2">
77-
<strong>Contact</strong>
78-
</div>
79-
<div class = "col-md-8">
80-
{{< event_link page="contact" text="Get in touch with the organizers" >}}
81-
</div>
82-
</div>
83-
84-
<!-- Uncomment if you added your city twitter name -->
85-
<!--
86-
{{< event_twitter >}}
87-
-->
1+
+++
2+
Title = "devopsdays Tokyo 2026"
3+
Type = "welcome"
4+
aliases = ["/events/2026-tokyo/"]
5+
Description = "devopsdays Tokyo 2026"
6+
+++
7+
8+
<!-- <div style="text-align:center;">
9+
{{< event_logo >}}
10+
</div> -->
11+
12+
<div class = "row">
13+
<div class = "col-md-2">
14+
<strong>Dates</strong>
15+
</div>
16+
<div class = "col-md-8">
17+
{{< event_start >}} - {{< event_end >}}
18+
</div>
19+
</div>
20+
21+
<div class = "row">
22+
<div class = "col-md-2">
23+
<strong>Location</strong>
24+
</div>
25+
<div class = "col-md-8">
26+
{{< event_location >}}
27+
</div>
28+
</div>
29+
30+
<div class = "row">
31+
<div class = "col-md-2">
32+
<strong>Register</strong>
33+
</div>
34+
<div class = "col-md-8">
35+
<a href="https://pretix.eu/devopsdaystokyo/2026/">Register to attend the conference!</a>
36+
</div>
37+
</div>
38+
39+
<div class = "row">
40+
<div class = "col-md-2">
41+
<strong>Propose</strong>
42+
</div>
43+
<div class = "col-md-8">
44+
<a href="https://confengine.com/conferences/devopsdays-tokyo-2026">Propose a talk!</a>
45+
</div>
46+
</div>
47+
48+
<div class = "row">
49+
<div class = "col-md-2">
50+
<strong>Program</strong>
51+
</div>
52+
<div class = "col-md-8">
53+
View the {{< event_link page="program" text="program." >}}
54+
</div>
55+
</div>
56+
57+
<div class = "row">
58+
<div class = "col-md-2">
59+
<strong>Speakers</strong>
60+
</div>
61+
<div class = "col-md-8">
62+
Check out the {{< event_link page="speakers" text="speakers!" >}}
63+
</div>
64+
</div>
65+
66+
<div class = "row">
67+
<div class = "col-md-2">
68+
<strong>Sponsors</strong>
69+
</div>
70+
<div class = "col-md-8">
71+
<a href="https://www.devopsdaystokyo.org/call-for-sponsor">Sponsor the conference!</a>
72+
</div>
73+
</div>
74+
75+
<div class = "row">
76+
<div class = "col-md-2">
77+
<strong>Contact</strong>
78+
</div>
79+
<div class = "col-md-8">
80+
{{< event_link page="contact" text="Get in touch with the organizers" >}}
81+
</div>
82+
</div>
83+
84+
<!-- Uncomment if you added your city twitter name -->
85+
86+
{{< event_twitter >}}
87+

‎data/events/2026/tokyo/main.yml‎

Lines changed: 0 additions & 95 deletions
Original file line numberDiff line numberDiff line change
@@ -1,95 +0,0 @@
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-

‎static/_redirects‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -118,7 +118,7 @@
118118
/tampa/* /events/2024-tampa/:splat 302
119119
/tel-aviv/* /events/2025-tel-aviv/:splat 302
120120
/texas/* /events/2021-texas/:splat 302
121-
/tokyo/* /events/2025-tokyo/:splat 302
121+
/tokyo/* /events/2026-tokyo/:splat 302
122122
/toronto/* /events/2020-toronto/:splat 302
123123
/ukraine/* /events/2025-kyiv/:splat 302
124124
/vancouver/* /events/2024-vancouver/:splat 302

‎static/events/2026-tokyo/logo-square.jpg‎

117 KB
Loading

‎static/events/2026-tokyo/logo.png‎

64.5 KB
Loading

0 commit comments

Comments
 (0)