Commit 4c48eca7 authored by Eric Poirier's avatar Eric Poirier
Browse files

Add organization to agenda examples page


Signed-off-by: Eric Poirier's avatarEric Poirier <eric.poirier@eclipse-foundation.org>
parent 1ebecaed
Pipeline #5502 passed with stage
...@@ -4,7 +4,7 @@ container: "container-fluid" ...@@ -4,7 +4,7 @@ container: "container-fluid"
hide_sidebar: true hide_sidebar: true
--- ---
Agendas can be added to the site through an `agenda.yaml` data file added in a subfolder of the data folder for the target locale (for localization, for default, create/use the "en" folder). An example of this path is as follows, `data/en/agenda.yaml`. The data should be similar to the following format: Agendas can be added to the site through an `agenda.yaml` data file added in a subfolder of the data folder for the target locale (for localization, for default, create/use the "en" folder). An example of this path is as follows, `data/en/agenda.yaml`. The data should be similar to the following format:
``` ```
...@@ -14,7 +14,7 @@ types: ...@@ -14,7 +14,7 @@ types:
id: 1 id: 1
color: "#e44" color: "#e44"
- name: Keynote - name: Keynote
id: b2 id: b2
color: "#a0a" color: "#a0a"
items: items:
...@@ -39,7 +39,7 @@ items: ...@@ -39,7 +39,7 @@ items:
type: break type: break
``` ```
Types represent the different types of sessions being held at the event. Normally creating the CSS for these types will be created automatically on render based on the `color` passed in the data file. If no color is set, no CSS would be generated for the type. Additionally, a new CSS rule may be added via custom code. This rule should resemble the following, replacing `<id>` with the `id` value set in the type and `<color>` with a hex color code: Types represent the different types of sessions being held at the event. Normally creating the CSS for these types will be created automatically on render based on the `color` passed in the data file. If no color is set, no CSS would be generated for the type. Additionally, a new CSS rule may be added via custom code. This rule should resemble the following, replacing `<id>` with the `id` value set in the type and `<color>` with a hex color code:
``` ```
.eclipsefdn-agenda-legend-icon-<id>::after { .eclipsefdn-agenda-legend-icon-<id>::after {
...@@ -47,43 +47,43 @@ Types represent the different types of sessions being held at the event. Normall ...@@ -47,43 +47,43 @@ Types represent the different types of sessions being held at the event. Normall
} }
``` ```
Items in these data files represent the actual sessions to be represented in the agenda. Items in these data files represent the actual sessions to be represented in the agenda.
**Note:** a modal is required on the page if an abstract has been defined within the agenda: **Note:** a modal is required on the page if an abstract has been defined within the agenda:
{{&lt; bootstrap/modal id="eclipsefdn-modal-event-session" &gt;}} {{&lt; bootstrap/modal id="eclipsefdn-modal-event-session" &gt;}}
--- ---
## Basic ## Basic
Targets ./data/en/default/agenda.yaml: Targets ./data/en/default/agenda.yaml:
{{< events/agenda >}} {{< events/agenda >}}
--- ---
## Different file name ## Different file name
Targets ./data/en/default/day_2.yaml: Targets ./data/en/default/day_2.yaml:
{{< events/agenda src="day_2">}} {{< events/agenda src="day_2">}}
--- ---
## Custom Title ## Custom Title
Targets ./data/en/default/day_2.yaml: Targets ./data/en/default/day_2.yaml:
{{< events/agenda title="Day 2 Agenda" src="day_2">}} {{< events/agenda title="Day 2 Agenda" src="day_2">}}
--- ---
## Sub-site version ## Sub-site version
Targets ./data/en/sample/agenda.yaml: Targets ./data/en/sample/agenda.yaml:
...@@ -92,7 +92,7 @@ Targets ./data/en/sample/agenda.yaml: ...@@ -92,7 +92,7 @@ Targets ./data/en/sample/agenda.yaml:
--- ---
## No session types ## No session types
Targets ./data/en/no_types/agenda.yaml: Targets ./data/en/no_types/agenda.yaml:
...@@ -113,13 +113,13 @@ Adding a "times" list into the items in agenda.yaml above will show multiple tim ...@@ -113,13 +113,13 @@ Adding a "times" list into the items in agenda.yaml above will show multiple tim
## Dynamic time based on user's timezone ## Dynamic time based on user's timezone
Targets ./data/en/active/agenda_dynamic_time.yaml: Targets ./data/en/active/agenda_dynamic_time.yaml:
Set "dynamicTime" property to true to enable dynamic time. Set "dynamicTime" property to true to enable dynamic time.
If "timezone" is not set, it will take "GMT-04" as the default value. If the timezone for input time is different, please add it and set the value in this format: GMT-[xx] or GMT+[xx]. If "timezone" is not set, it will take "GMT-04" as the default value. If the timezone for input time is different, please add it and set the value in this format: GMT-[xx] or GMT+[xx].
The output timezone will always be the user's timezone. The output timezone will always be the user's timezone.
{{< events/agenda event="active" src="agenda_dynamic_time">}} {{< events/agenda event="active" src="agenda_dynamic_time">}}
...@@ -154,3 +154,14 @@ Targets ./data/en/multistream/agenda.yaml: ...@@ -154,3 +154,14 @@ Targets ./data/en/multistream/agenda.yaml:
{{< bootstrap/modal id="eclipsefdn-modal-event-session" >}} {{< bootstrap/modal id="eclipsefdn-modal-event-session" >}}
---
## Agenda w/ Organization field
Targets ./data/en/organization/agenda.yaml:
{{< events/agenda event="organization">}}
{{< bootstrap/modal id="eclipsefdn-modal-event-session" >}}
complete: true
types:
- name: Demo
id: 1
color: "#e44"
- name: Keynote
id: b2
color: "#a0a"
- name: Cloud
id: 3
color: "#66e"
items:
- name: Open-source software
presenter: Ken K.
abstract: "<p>Sample abstract <a href='#'>Sample link</a></p>"
organization: test 1
type: 1
vod: "#1"
- name: How to 'how to'
presenter: Jim Bob
type: b2
vod: "#2"
organization: test 2
- name: Industry Keynote
presenter: Eclipse Foundation, .etc
type: b2
vod: "#3"
- name: Best practices for Interneting your Things
presenter: Adam A.
type: 3
vod: "#4"
organization: test 3
- name: Lunch Break
type: break
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment