diff --git a/data/events/2024/denver/main.yml b/data/events/2024/denver/main.yml index 24c0a0711e1..10bae4ca720 100644 --- a/data/events/2024/denver/main.yml +++ b/data/events/2024/denver/main.yml @@ -13,6 +13,8 @@ ga_tracking_id: "G-9SR9GD94E0" # If you have your own Google Analytics tracking startdate: 2024-09-16 # The start date of your event. Leave blank if you don't have a venue reserved yet. enddate: 2024-09-17 # The end date of your event. Leave blank if you don't have a venue reserved yet. +timeoffset: "-0600" + # Leave CFP dates blank if you don't know yet, or set all three at once. cfp_date_start: 2023-10-31T23:59:59-06:00 # start accepting talk proposals. cfp_date_end: 2024-05-04T23:59:59-06:00 # close your call for proposals. diff --git a/data/events/2024/london/main.yml b/data/events/2024/london/main.yml index edbf295ed44..51096e09ccf 100644 --- a/data/events/2024/london/main.yml +++ b/data/events/2024/london/main.yml @@ -15,6 +15,8 @@ masthead_background: "background.png" startdate: 2024-09-26T00:00:00+01:00 # The start date of your event. Leave blank if you don't have a venue reserved yet. enddate: 2024-09-27T00:00:00+01:00 # The end date of your event. Leave blank if you don't have a venue reserved yet. +timezone: "Europe/London" + # Leave CFP dates blank if you don't know yet, or set all three at once. cfp_date_start: 2023-09-22T00:00:00+01:00 # start accepting talk proposals. cfp_date_end: 2024-05-24T23:59:59+01:00 # close your call for proposals. diff --git a/data/events/2024/rio-de-janeiro/main.yml b/data/events/2024/rio-de-janeiro/main.yml index 486aacebb1d..d4212b9fba9 100644 --- a/data/events/2024/rio-de-janeiro/main.yml +++ b/data/events/2024/rio-de-janeiro/main.yml @@ -13,6 +13,9 @@ ga_tracking_id: "" # If you have your own Google Analytics tracking ID, enter it startdate: 2024-08-24T09:00:00-03:00 # The start date of your event. Leave blank if you don't have a venue reserved yet. enddate: 2024-08-24T18:00:00-03:00 # The end date of your event. Leave blank if you don't have a venue reserved yet. +timezone: "America/Sao_Paulo" +timeoffset: "-0300" + # Leave CFP dates blank if you don't know yet, or set all three at once. cfp_date_start: 2024-04-22T00:00:00-03:00 # start accepting talk proposals. cfp_date_end: 2024-05-26T00:00:00-03:00 # close your call for proposals. @@ -326,4 +329,4 @@ program: type: custom date: 2024-08-24 start_time: "19:00" - end_time: "20:00" \ No newline at end of file + end_time: "20:00" diff --git a/themes/devopsdays-theme/layouts/program/single.html b/themes/devopsdays-theme/layouts/program/single.html index e30b68bd47d..37a58174c5d 100644 --- a/themes/devopsdays-theme/layouts/program/single.html +++ b/themes/devopsdays-theme/layouts/program/single.html @@ -95,6 +95,22 @@

Program

{{- end -}} {{- end -}} + + {{- if or $e.timeoffset $e.timezone -}} + + {{- end -}} + {{- if $e.timezone -}} + + {{- end -}} +
@@ -125,6 +141,33 @@
{{ .start_time }} - {{ .end_time }} + {{- if $e.timezone -}} +   + {{- end -}} + {{- if or $e.timeoffset $e.timezone -}} +
+ {{- if $e.timeoffset -}} + + {{- end -}} + {{- if not $e.timeoffset -}} + + {{- end -}} + + {{- end -}}
{{- if eq .type "custom" -}} diff --git a/themes/devopsdays-theme/reference.md b/themes/devopsdays-theme/reference.md index cba30a726c9..17a8f61a9b7 100644 --- a/themes/devopsdays-theme/reference.md +++ b/themes/devopsdays-theme/reference.md @@ -61,20 +61,22 @@ The `/data/events/YYYY/CITY.main.yml` file is the main configuration file for yo ### Date-related Fields All dates are in unquoted YYYY-MM-DD, like this: `variable: 2016-01-05`, or like `variable: 2016-01-05T23:59:00-06:00` -| Field Name | Type | Required | Description | Example | -|-------------------------|------------|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------| -| `startdate` | YYYY-MM-DD | No | The start date of your event. Leave blank if you don't have a venue reserved yet. | 2016-01-05 | -| `enddate` | YYYY-MM-DD | No | The end date of your event. Leave blank if you don't have a venue reserved yet. | 2016-01-05 | -| `cfp_date_start` | YYYY-MM-DD | No | The date you will start accepting talk proposals. Can be a blank value. | 2016-01-05 | -| `cfp_date_end` | YYYY-MM-DD | No | The date you will close your call for proposals. Can be a blank value. If you set the full datetime string with correct TZ, CFP will display as open until local close time. | 2016-01-05T23:59:00-06:00 | -| `cfp_date_announce` | YYYY-MM-DD | No | The date you will inform proposers of status. Can be a blank value. | 2016-01-05 | -| `cfp_open` | String | No | Either "true" or "false". Can be blank. This controls whether or not the "propose" button shows on your event page. *Deprecated field; if you have set `cfp_date_start` and `cfp_date_end` they will serve the same purpose.* | "true" | -| `cfp_link` | String | No | 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. | "https://myurlhere" - reference it like "{{< event_link url-key="cfp_link" text="Propose a talk!" >}}" | -| `registration_date_start` | YYYY-MM-DD | No | The date you will start accepting registration. If this is set, will make the "Register" button appear on the event's "Welcome" page. Can be a blank value. | 2016-01-05 | -| `registration_date_end` | YYYY-MM-DD | No | The date you will close registration. Controls the appearance of the "Register" button on the "Welcome" page. If you set `registration_date_start` you must set `registration_date_end`. Can be a blank value (unless `registration_date_start` has been set). | 2016-01-05 | -| `registration_closed` | String | No | Set this to "true" if you need to manually close registration before your registration end date. | "true" | -| `registration_link` | String | No | If you have a custom registration link, enter it here. This will control the Registration menu item as well as the "Register" button. | "https://myurlhere" reference it like {{< event_link url-key="registration_link" text="Register to attend the conference!" >}} | | -| `sponsor_link` | String | No | If you have a custom sponsorship link, enter it here. This will control the "Become an X Sponsor!" links. It does NOT change the "Sponsor" button. | "https://myurlhere" | | +| Field Name | Type | Required | Description | Example | +|------------------------------|------------|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------| +| `startdate` | YYYY-MM-DD | No | The start date of your event. Leave blank if you don't have a venue reserved yet. | 2016-01-05 | +| `enddate` | YYYY-MM-DD | No | The end date of your event. Leave blank if you don't have a venue reserved yet. | 2016-01-05 | +| `timeoffset` | +/-HHMM | No | The offset of the timezone of your event from UTC | "-0600" | +| `timezone` | String | No | The timezone of the event [https://en.wikipedia.org/wiki/List_of_tz_database_time_zones#List](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones#List) | "Europe/London" | +| `cfp_date_start` | YYYY-MM-DD | No | The date you will start accepting talk proposals. Can be a blank value. | 2016-01-05 | +| `cfp_date_end` | YYYY-MM-DD | No | The date you will close your call for proposals. Can be a blank value. If you set the full datetime string with correct TZ, CFP will display as open until local close time. | 2016-01-05T23:59:00-06:00 | +| `cfp_date_announce` | YYYY-MM-DD | No | The date you will inform proposers of status. Can be a blank value. | 2016-01-05 | +| `cfp_open` | String | No | Either "true" or "false". Can be blank. This controls whether or not the "propose" button shows on your event page. *Deprecated field; if you have set `cfp_date_start` and `cfp_date_end` they will serve the same purpose.* | "true" | +| `cfp_link` | String | No | 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. | "https://myurlhere" - reference it like "{{< event_link url-key="cfp_link" text="Propose a talk!" >}}" | +| `registration_date_start` | YYYY-MM-DD | No | The date you will start accepting registration. If this is set, will make the "Register" button appear on the event's "Welcome" page. Can be a blank value. | 2016-01-05 | +| `registration_date_end` | YYYY-MM-DD | No | The date you will close registration. Controls the appearance of the "Register" button on the "Welcome" page. If you set `registration_date_start` you must set `registration_date_end`. Can be a blank value (unless `registration_date_start` has been set). | 2016-01-05 | +| `registration_closed` | String | No | Set this to "true" if you need to manually close registration before your registration end date. | "true" | +| `registration_link` | String | No | If you have a custom registration link, enter it here. This will control the Registration menu item as well as the "Register" button. | "https://myurlhere" reference it like {{< event_link url-key="registration_link" text="Register to attend the conference!" >}} | | +| `sponsor_link` | String | No | If you have a custom sponsorship link, enter it here. This will control the "Become an X Sponsor!" links. It does NOT change the "Sponsor" button. | "https://myurlhere" | | ### Branding Fields