diff --git a/README.md b/README.md index 538759e6..58b1fa30 100644 --- a/README.md +++ b/README.md @@ -61,3 +61,98 @@ More information is available in the [Debugging](https://www.11ty.dev/docs/debug ## Deployment [TBC] + +## Authoring pages + +### Page data + +At the beginning of all pages, there's a block of data wrapped with ---. This is called frontmatter and it will follow a specific schema relative to the page you are on. + +The frontmatter data is written in [YAML format](https://yaml.org/) using `key: value` pairs. + +### Markdown and HTML + +Pages can contain a mix of Markdown and HTML. This means we can intersperse basic content formatting with more bespoke HTML elements in the same file. + +``` +# Page title + +A paragraph of text, Markdown style. + +- Markdown list items +- Lists are great + +
+

Stick to HTML

+
+``` + +The **caveat** here is to ensure that there is always a clear break between Markdown and HTML elements. Mixing and matching the two in a single content block will not work. + +``` + +
+ ## Trying for a Markdown heading (and failing) +
+ + +
+ +## All good here + +
+``` + +To learn more about what's possible in Markdown, see [Markdown Guide](https://www.markdownguide.org). + +### Adding links + +Linking to pages throughout the site works in the same way as linking to pages in standard HTML sites. + +We'll most likely be using Markdown's link syntax to link to pages. The links we choose can be relative or absolute. + +Let's use a _blog-posts_ page (`/blog/yyyy/blog-post`) as an example. If we want to link to another blog post page it can be done in two ways: + +```md +[Relative link to blog post](../blog-post/) + +[Root relative link to blog post](/blog/yyyy/blog-post/) +``` + +If we need to link to another section/page within the site we can use either method shown above. The `../` prefix can be used to traverse further up the site tree: + +```md +[Relative link to my parent](../) +[Relative link to my grandparent](../../) +[Relative link to a sibling of mine](../sibling-page/) +``` + +Note: these don't need filename `.md`/`.html` extensions. + +Only use absolute URLs for links out of the site: + +```md +[Absolute link to Ceph.io](https://ceph.io/) +``` + +### Dynamic values + +We can interpolate these dynamic values throughout the Markdown. For example, we can save ourselves repeating the page's `title` property for our page title heading by using the `{{ }}` syntax: + +```md +--- +title: Don't repeat yourself +--- + +# Don't repeat yourself +``` + +becomes: + +```md +--- +title: Don't repeat yourself +--- + +# {{ title }} +``` diff --git a/src/_includes/layouts/event.njk b/src/_includes/layouts/event.njk index c9c2a5e4..300ebb70 100644 --- a/src/_includes/layouts/event.njk +++ b/src/_includes/layouts/event.njk @@ -11,10 +11,20 @@ layout: base
+ {% if links and not end | futureDate %} +
+ {% if links.videos %} + Watch the videos + {% endif %} + {% if links.slides %} + View presentation slides + {% endif %} +
+ {% endif %} {% if image %}
-
- +
+
{% endif %} @@ -23,41 +33,45 @@ layout: base
\ No newline at end of file diff --git a/src/css/component.agenda.css b/src/css/component.agenda.css new file mode 100644 index 00000000..409091b6 --- /dev/null +++ b/src/css/component.agenda.css @@ -0,0 +1,20 @@ +/* ---------- COMPONENT agenda ---------- */ + +.agenda { + font-size: var(--font-size-sm); + line-height: var(--size-5); + width: var(--size-full); +} + +.agenda__intermission { + color: hsla(var(--color-gunmetal-hsl), 0.4); +} + +.agenda td { + border-bottom: var(--size-px) solid var(--color-grey-500); + padding: var(--size-4) 0; +} + +.agenda td:first-child { + width: var(--size-20); +} diff --git a/src/css/main.css b/src/css/main.css index 8f5a98a1..d6da5543 100644 --- a/src/css/main.css +++ b/src/css/main.css @@ -26,6 +26,7 @@ @import "object.wrapper.css"; /* components */ +@import "component.agenda.css"; @import "component.button.css"; @import "component.hr.css"; @import "component.link-cover.css"; diff --git a/src/css/object.grid.css b/src/css/object.grid.css index 566d666b..a6838a94 100644 --- a/src/css/object.grid.css +++ b/src/css/object.grid.css @@ -32,6 +32,10 @@ --grid-gap: var(--size-0); } +.grid--gap-7 { + --grid-gap: var(--size-7); +} + /* columns */ .grid--cols-none { grid-template-columns: var(--size-none); @@ -123,6 +127,10 @@ } @media (--mq-md-to-lg) { + .md-to-lg\:grid--gap-7 { + --grid-gap: var(--size-7); + } + .md-to-lg\:grid--cols-2 { grid-template-columns: repeat(2, minmax(0, 1fr)); } diff --git a/src/css/utilities.colors.css b/src/css/utilities.colors.css index 7c83c8aa..78350864 100644 --- a/src/css/utilities.colors.css +++ b/src/css/utilities.colors.css @@ -1,6 +1,6 @@ /* ---------- UTILITIES colors ---------- */ -/* ---------- background negative ---------- */ +/* negative */ .bg-black { background-color: var(--color-black); } @@ -9,45 +9,40 @@ background-color: var(--color-white); } -/* ---------- background navy ---------- */ -.bg-navy { - background-color: var(--color-navy); +.border-black { + border-color: var(--color-black); } -/* ---------- background grey ---------- */ -.bg-grey-300 { - background-color: var(--color-grey-300); +.border-white { + border-color: var(--color-white); } -.bg-grey-500 { - background-color: var(--color-grey-500); +.color-black { + color: var(--color-black); } -/* ---------- background gunmetal ---------- */ -.bg-gunmetal { - background-color: var(--color-gunmetal); +.color-white { + color: var(--color-white); } -/* ---------- background red ---------- */ -.bg-red-500 { - background-color: var(--color-red-500); +/* navy */ +.bg-navy { + background-color: var(--color-navy); } -/* ---------- background royal ---------- */ -.bg-royal { - background-color: var(--color-royal); +.color-navy { + color: var(--color-navy); } -/* ---------- border negative ---------- */ -.border-black { - border-color: var(--color-black); +/* grey */ +.bg-grey-300 { + background-color: var(--color-grey-300); } -.border-white { - border-color: var(--color-white); +.bg-grey-500 { + background-color: var(--color-grey-500); } -/* ---------- border grey ---------- */ .border-grey-300 { border-color: var(--color-grey-300); } @@ -56,30 +51,37 @@ border-color: var(--color-grey-500); } -/* ---------- text negative ---------- */ -.color-black { - color: var(--color-black); +.color-grey-300 { + color: var(--color-grey-300); } -.color-white { - color: var(--color-white); +.color-grey-500 { + color: var(--color-grey-500); +} + +/* gunmetal */ +.bg-gunmetal { + background-color: var(--color-gunmetal); } /* red */ -.color-red-500 { - color: var(--color-red-500); +.bg-red-500 { + background-color: var(--color-red-500); } -/* ---------- text navy ---------- */ -.color-navy { - color: var(--color-navy); +.color-red-400 { + color: var(--color-red-400); } -/* ---------- text grey ---------- */ -.color-grey-300 { - color: var(--color-grey-300); +.color-red-500 { + color: var(--color-red-500); } -.color-grey-500 { - color: var(--color-grey-500); +/* royal */ +.bg-royal { + background-color: var(--color-royal); +} + +.color-royal { + color: var(--color-royal); } diff --git a/src/css/utilities.size.css b/src/css/utilities.size.css index ddb2e3fd..320e20c0 100644 --- a/src/css/utilities.size.css +++ b/src/css/utilities.size.css @@ -14,6 +14,10 @@ width: var(--size-36); } +.w-3-4 { + width: var(--size-3-4); +} + .w-full { width: var(--size-full); } diff --git a/src/css/utilities.space.css b/src/css/utilities.space.css index 3d255531..038dd6ec 100644 --- a/src/css/utilities.space.css +++ b/src/css/utilities.space.css @@ -3985,6 +3985,12 @@ } } +@media (--mq-to-lg) { + .to-lg\:mb-14 { + margin-bottom: var(--size-14); + } +} + @media (--mq-lg) { /* margin */ .lg\:m-0 { diff --git a/src/en-GB/community/events/2019/ceph-day-london/index.md b/src/en-GB/community/events/2019/ceph-day-london/index.md index e34df1e3..e252fa01 100644 --- a/src/en-GB/community/events/2019/ceph-day-london/index.md +++ b/src/en-GB/community/events/2019/ceph-day-london/index.md @@ -6,6 +6,10 @@ location: London, UK venue: Student Central, Malet Street, London map: "https://goo.gl/maps/6isXCefxCPw6V6wu7" register: "https://www.eventbrite.com/" +image: "/assets/placeholder-photo-1280x720.jpg" +links: + videos: "https://www.youtube.com/" + slides: "" sponsors: - label: Event sponsors list: @@ -16,7 +20,7 @@ sponsors: logo: "https://via.placeholder.com/50" website: "https://redhat.co" tags: - - "ceph days" + - ceph days --- ## Bringing Ceph to London @@ -38,3 +42,68 @@ The expert Ceph team, Ceph’s customers and partners, and the Ceph community jo ## CFP is now open! ### Agenda + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
8:30amRegistration & Breakfast
9:15amWelcome words
9:30amDeploying CloudStack and Ceph with flexible XLAN and BGp networking – Wido den Hollander
10:15amCeph with CloudStack – Andrija Panic
11:00amCoffee break
11:15amAchieving the ultimate performance with KVM
12:00pmLunch
1:00pmStorage based snapshots
1:45pmCloud management portal
2:30pmNew stuff in CloudStack
3:15pmCoffee
3:30pmOur journey with CloudStack
4:15pmRunning OpenShift clusters
5:00pmClosing words
5:15pmPub
diff --git a/src/en-GB/community/events/2019/ceph-day-vancouver/ceph-day-vancouver.json b/src/en-GB/community/events/2019/ceph-day-vancouver/ceph-day-vancouver.json deleted file mode 100644 index 70e2a4c9..00000000 --- a/src/en-GB/community/events/2019/ceph-day-vancouver/ceph-day-vancouver.json +++ /dev/null @@ -1,19 +0,0 @@ -{ - "sponsors": [ - { - "label": "Event sponsors", - "list": [ - { - "name": "SoftIron", - "logo": "https://via.placeholder.com/50", - "website": "https://softiron.com" - }, - { - "name": "RedHat", - "logo": "https://via.placeholder.com/50", - "website": "https://redhat.com" - } - ] - } - ] -} diff --git a/src/en-GB/community/events/2019/ceph-day-vancouver/index.md b/src/en-GB/community/events/2019/ceph-day-vancouver/index.md index 84ff931c..01c872a6 100644 --- a/src/en-GB/community/events/2019/ceph-day-vancouver/index.md +++ b/src/en-GB/community/events/2019/ceph-day-vancouver/index.md @@ -6,8 +6,21 @@ location: Vancouver, Canada venue: Student Central, Malet Street, Vancouver map: "https://goo.gl/maps/6isXCefxCPw6V6wu7" register: "https://www.eventbrite.com/" +image: "/assets/placeholder-photo-1280x720.jpg" +links: + videos: "https://www.youtube.com/" + slides: "" +sponsors: + - label: Event sponsors + list: + - name: SoftIron + logo: "https://via.placeholder.com/50" + website: "https://softiron.com" + - name: RedHat + logo: "https://via.placeholder.com/50" + website: "https://redhat.co" tags: - - "ceph days" + - ceph days --- ## Bringing Ceph to Vancouver @@ -27,3 +40,68 @@ Interested in sponsoring this Ceph Day? See our [brochure](https://ceph.io/wp-co ## CFP is now open! ### Agenda + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
8:30amRegistration & Breakfast
9:15amWelcome words
9:30amDeploying CloudStack and Ceph with flexible XLAN and BGp networking – Wido den Hollander
10:15amCeph with CloudStack – Andrija Panic
11:00amCoffee break
11:15amAchieving the ultimate performance with KVM
12:00pmLunch
1:00pmStorage based snapshots
1:45pmCloud management portal
2:30pmNew stuff in CloudStack
3:15pmCoffee
3:30pmOur journey with CloudStack
4:15pmRunning OpenShift clusters
5:00pmClosing words
5:15pmPub
diff --git a/src/en-GB/community/events/2020/ceph-day-london/index.md b/src/en-GB/community/events/2020/ceph-day-london/index.md index ac496bb6..a91b2c1d 100644 --- a/src/en-GB/community/events/2020/ceph-day-london/index.md +++ b/src/en-GB/community/events/2020/ceph-day-london/index.md @@ -6,8 +6,9 @@ location: London, UK venue: Student Central, Malet Street, London map: "https://goo.gl/maps/6isXCefxCPw6V6wu7" register: "https://www.eventbrite.com/" +image: "/assets/placeholder-photo-1280x720.jpg" links: - videos: "" + videos: "https://www.youtube.com/" slides: "" sponsors: - label: Platinum @@ -46,3 +47,68 @@ The expert Ceph team, Ceph’s customers and partners, and the Ceph community jo ## CFP is now open! ### Agenda + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
8:30amRegistration & Breakfast
9:15amWelcome words
9:30amDeploying CloudStack and Ceph with flexible XLAN and BGp networking – Wido den Hollander
10:15amCeph with CloudStack – Andrija Panic
11:00amCoffee break
11:15amAchieving the ultimate performance with KVM
12:00pmLunch
1:00pmStorage based snapshots
1:45pmCloud management portal
2:30pmNew stuff in CloudStack
3:15pmCoffee
3:30pmOur journey with CloudStack
4:15pmRunning OpenShift clusters
5:00pmClosing words
5:15pmPub
diff --git a/src/en-GB/community/events/2020/ceph-day-poland/ceph-day-poland.json b/src/en-GB/community/events/2020/ceph-day-poland/ceph-day-poland.json deleted file mode 100644 index a91574c2..00000000 --- a/src/en-GB/community/events/2020/ceph-day-poland/ceph-day-poland.json +++ /dev/null @@ -1,29 +0,0 @@ -{ - "sponsors": [ - { - "label": "Platinum sponsors", - "list": [ - { - "name": "SoftIron", - "logo": "https://via.placeholder.com/50", - "website": "https://softiron.com" - }, - { - "name": "RedHat", - "logo": "https://via.placeholder.com/50", - "website": "https://redhat.com" - } - ] - }, - { - "label": "Gold sponsors", - "list": [ - { - "name": "SUSE", - "logo": "https://via.placeholder.com/50", - "website": "https://suse.com" - } - ] - } - ] -} diff --git a/src/en-GB/community/events/2020/ceph-day-poland/index.md b/src/en-GB/community/events/2020/ceph-day-poland/index.md index 732db9c5..a21aec94 100644 --- a/src/en-GB/community/events/2020/ceph-day-poland/index.md +++ b/src/en-GB/community/events/2020/ceph-day-poland/index.md @@ -6,8 +6,26 @@ location: Wrocław, Poland venue: Hotel ibis Styles, Wrocław Centrum, Poland map: "https://goo.gl/maps/6isXCefxCPw6V6wu7" register: "https://www.eventbrite.com/" +image: "/assets/placeholder-photo-1280x720.jpg" +links: + videos: "https://www.youtube.com/" + slides: "" +sponsors: + - label: Platinum sponsors + list: + - name: SoftIron + logo: "https://via.placeholder.com/50" + website: "https://softiron.com" + - name: RedHat + logo: "https://via.placeholder.com/50" + website: "https://redhat.com" + - label: Gold sponsors + list: + - name: SUSE + logo: "https://via.placeholder.com/50" + website: "https://suse.com" tags: - - "ceph days" + - ceph days --- ## Bringing Ceph to Poland @@ -29,3 +47,68 @@ The expert Ceph team, Ceph’s customers and partners, and the Ceph community jo ## CFP is now open! ### Agenda + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
8:30amRegistration & Breakfast
9:15amWelcome words
9:30amDeploying CloudStack and Ceph with flexible XLAN and BGp networking – Wido den Hollander
10:15amCeph with CloudStack – Andrija Panic
11:00amCoffee break
11:15amAchieving the ultimate performance with KVM
12:00pmLunch
1:00pmStorage based snapshots
1:45pmCloud management portal
2:30pmNew stuff in CloudStack
3:15pmCoffee
3:30pmOur journey with CloudStack
4:15pmRunning OpenShift clusters
5:00pmClosing words
5:15pmPub
diff --git a/src/en-GB/community/events/2020/ceph-day-vancouver/ceph-day-vancouver.json b/src/en-GB/community/events/2020/ceph-day-vancouver/ceph-day-vancouver.json deleted file mode 100644 index a91574c2..00000000 --- a/src/en-GB/community/events/2020/ceph-day-vancouver/ceph-day-vancouver.json +++ /dev/null @@ -1,29 +0,0 @@ -{ - "sponsors": [ - { - "label": "Platinum sponsors", - "list": [ - { - "name": "SoftIron", - "logo": "https://via.placeholder.com/50", - "website": "https://softiron.com" - }, - { - "name": "RedHat", - "logo": "https://via.placeholder.com/50", - "website": "https://redhat.com" - } - ] - }, - { - "label": "Gold sponsors", - "list": [ - { - "name": "SUSE", - "logo": "https://via.placeholder.com/50", - "website": "https://suse.com" - } - ] - } - ] -} diff --git a/src/en-GB/community/events/2020/ceph-day-vancouver/index.md b/src/en-GB/community/events/2020/ceph-day-vancouver/index.md index ea6a56aa..5a85d7c4 100644 --- a/src/en-GB/community/events/2020/ceph-day-vancouver/index.md +++ b/src/en-GB/community/events/2020/ceph-day-vancouver/index.md @@ -6,8 +6,26 @@ location: Vancouver, Canada venue: Student Central, Malet Street, Vancouver map: "https://goo.gl/maps/6isXCefxCPw6V6wu7" register: "https://www.eventbrite.com/" +image: "/assets/placeholder-photo-1280x720.jpg" +links: + videos: "https://www.youtube.com/" + slides: "" +sponsors: + - label: Platinum sponsors + list: + - name: SoftIron + logo: "https://via.placeholder.com/50" + website: "https://softiron.com" + - name: RedHat + logo: "https://via.placeholder.com/50" + website: "https://redhat.com" + - label: Gold sponsors + list: + - name: SUSE + logo: "https://via.placeholder.com/50" + website: "https://suse.com" tags: - - "ceph days" + - ceph days --- ## Bringing Ceph to Vancouver @@ -27,3 +45,68 @@ Interested in sponsoring this Ceph Day? See our [brochure](https://ceph.io/wp-co ## CFP is now open! ### Agenda + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
8:30amRegistration & Breakfast
9:15amWelcome words
9:30amDeploying CloudStack and Ceph with flexible XLAN and BGp networking – Wido den Hollander
10:15amCeph with CloudStack – Andrija Panic
11:00amCoffee break
11:15amAchieving the ultimate performance with KVM
12:00pmLunch
1:00pmStorage based snapshots
1:45pmCloud management portal
2:30pmNew stuff in CloudStack
3:15pmCoffee
3:30pmOur journey with CloudStack
4:15pmRunning OpenShift clusters
5:00pmClosing words
5:15pmPub
diff --git a/src/en-GB/community/events/2021/ceph-day-poland/ceph-day-poland.json b/src/en-GB/community/events/2021/ceph-day-poland/ceph-day-poland.json deleted file mode 100644 index a91574c2..00000000 --- a/src/en-GB/community/events/2021/ceph-day-poland/ceph-day-poland.json +++ /dev/null @@ -1,29 +0,0 @@ -{ - "sponsors": [ - { - "label": "Platinum sponsors", - "list": [ - { - "name": "SoftIron", - "logo": "https://via.placeholder.com/50", - "website": "https://softiron.com" - }, - { - "name": "RedHat", - "logo": "https://via.placeholder.com/50", - "website": "https://redhat.com" - } - ] - }, - { - "label": "Gold sponsors", - "list": [ - { - "name": "SUSE", - "logo": "https://via.placeholder.com/50", - "website": "https://suse.com" - } - ] - } - ] -} diff --git a/src/en-GB/community/events/2021/ceph-day-poland/index.md b/src/en-GB/community/events/2021/ceph-day-poland/index.md index 9bb768c8..226fb03c 100644 --- a/src/en-GB/community/events/2021/ceph-day-poland/index.md +++ b/src/en-GB/community/events/2021/ceph-day-poland/index.md @@ -1,13 +1,31 @@ --- title: Ceph Day Poland -date: 2021-02-20 +date: 2021-02-16 end: 2021-03-01 location: Wrocław, Poland venue: Hotel ibis Styles, Wrocław Centrum, Poland map: "https://goo.gl/maps/6isXCefxCPw6V6wu7" register: "https://www.eventbrite.com/" +image: "/assets/placeholder-photo-1280x720.jpg" +links: + videos: "https://www.youtube.com/" + slides: "" +sponsors: + - label: Platinum sponsors + list: + - name: SoftIron + logo: "https://via.placeholder.com/50" + website: "https://softiron.com" + - name: RedHat + logo: "https://via.placeholder.com/50" + website: "https://redhat.com" + - label: Gold sponsors + list: + - name: SUSE + logo: "https://via.placeholder.com/50" + website: "https://suse.com" tags: - - "ceph days" + - ceph days --- ## Bringing Ceph to Poland @@ -30,34 +48,67 @@ The expert Ceph team, Ceph’s customers and partners, and the Ceph community jo ### Agenda - +
+ + + + - - + + - + + - + + + + + + - + + + + + + - - + + - + + - - + + + + + + - + + + + + + + + + + + + + +
8:30amRegistration & Breakfast
8:30 amRegistration and breakfast9:15amWelcome words
8:45 am9:30amDeploying CloudStack and Ceph with flexible XLAN and BGp networking – Wido den Hollander
9:00 am10:15amCeph with CloudStack – Andrija Panic
11:00amCoffee break
9:15 am11:15amAchieving the ultimate performance with KVM
12:00pmLunch
9:30 amCeph Introduction and Community Update — Mike Perez (Red Hat)1:00pmStorage based snapshots
9:45 am1:45pmCloud management portal
10:00 amSelf-healing Ceph at scale — Flilp Dorosz (OVH)2:30pmNew stuff in CloudStack
3:15pmCoffee
10:15 am3:30pmOur journey with CloudStack
4:15pmRunning OpenShift clusters
5:00pmClosing words
5:15pmPub
diff --git a/src/en-GB/community/events/README.md b/src/en-GB/community/events/README.md new file mode 100644 index 00000000..eafa0edb --- /dev/null +++ b/src/en-GB/community/events/README.md @@ -0,0 +1,76 @@ +

Ceph

+ +# Events + +## Frontmatter + +```yaml +--- +title: Event title +date: yyyy-mm-dd +end: yyyy-mm-dd +location: Event location +venue: Event venue +map: "https://www.google.com/maps" +register: "https://www.eventbrite.com/" +image: "/assets/image.jpg" +links: + videos: "https://www.youtube.com/" + slides: "https://ceph.io/event.pdf" +sponsors: + - label: Platinum sponsors + list: + - name: SoftIron + logo: "/assets/image.png" + website: "https://softiron.com" + - name: RedHat + logo: "/assets/image.png" + website: "https://redhat.com" + - label: Gold sponsors + list: + - name: SUSE + logo: "/assets/image.png" + website: "https://suse.com" +tags: + - taxonomy + - taxonomy +--- + +``` + +- `title` (String) — Determines the link text as it appears in the event navigation card. Also used as the `` for the page.\* +- `date` (Date) — Determines the start date of the event. +- `end` (Date) — Determines the end date of the event. +- `location` (String) — Determines the location of the event, city and country. +- `venue` (String) — Determines the venue of the event, building name and street. +- `map` (String) — Determines the map of the event with a google maps link.\* +- `register` (String) — Determines the website to register for the event. This is hidden once the end date of the event has pasted. +- `image` (String) — Determines the asset path for the image shown in the event navigation card and the hero image beneath the title on the event page. +- `links` (List) - These only appear when the end date of the event has pasted. + - `videos` (String) — Determines the website showing videos of the event with a youtube/vimeo link. + - `slides` (String) — Determines the website or PDF showing slides of the event. +- `sponsors` (Array) + - `label` (String) — Determines the type of sponsors for the event. + `list` + - `name` (String) — Determines the name of the sponsor. + `logo` (String) — Determines the asset path for the sponsor logo. + `website` (String) — Determines the URL of the sponsor website which is applied to the sponsor logo. +- `tags` (Array) - This is an array of values that determine the taxonomy of the event. + - (String) - Choose from a pre-defined selection of values that apply only to events. You can apply as many values as required. + +\* Careful with any strings that include a colon `:`, as YAML uses this as the key-value pair delimiter. A `URL` will always include a colon and possibly the other values will include them too. For example let's say the `title` needs to include colons, wrap the `title` string in double-quote marks `"` to ensure it renders as intended or if a URL contains. + +```yaml +title: "Storage or: How I Learned to Stop Worrying and Love Ceph" +map: "https://www.google.com/maps" +``` + +## Events structure + +The content of the events can be found in the `src/{locale}/community/events/yyyy/event` directories. Any folder/page created within these directories will generate a web page in the site. + +### Folders and file naming + +| Input File | Output URL | +| -------------------------------------------------- | ------------------------------------- | +| /src/{locale}/community/events/yyyy/event/index.md | /{locale}/community/events/yyyy/event | diff --git a/src/en-GB/news/blog/README.md b/src/en-GB/news/blog/README.md index 1180d3db..9226f83e 100644 --- a/src/en-GB/news/blog/README.md +++ b/src/en-GB/news/blog/README.md @@ -2,11 +2,7 @@ # Blog posts -## Page data - -At the beginning of all blog posts, there's a block of data wrapped with ---. This is called frontmatter, and defines data specific to that page in the site. - -The frontmatter data is written in [YAML format](https://yaml.org/) using `key: value` pairs. Frontmatter for the blog post pages follows a specific schema: +## Frontmatter ```yaml --- @@ -24,113 +20,23 @@ tags: - `title` (String) — Determines the link text as it appears in the blog post navigation card. Also used as the `<title>` for the page.\* - `date` (Date) — Determines the published date of the blog post. - `author` (String) — Determines the name of the blog post author. -- `image` (String) — Determines the image shown in the blog post navigation card and the hero image beneath the title on the blog post page. -- `tags` (Array) - This is an array of values that determine the taxonomy of the blog post page. - - (String) - Choose from a pre-defined selection of values that apply only to blog posts. You can apply as many values as required.\* +- `image` (String) — Determines the asset path for the image shown in the blog post navigation card and the hero image beneath the title on the blog post page.\* +- `tags` (Array) - This is an array of values that determine the taxonomy of the blog post. + - (String) - Choose from a pre-defined selection of values that apply only to blog posts. You can apply as many values as required. -\* Careful with any strings that include a colon `:`, as YAML uses this as the key-value pair delimiter. If the title needs to include colons, wrap the `title` string in double-quote marks `"` to ensure it renders as intended. E.g. +\* Careful with any strings that include a colon `:`, as YAML uses this as the key-value pair delimiter. A `URL` will always include a colon and possibly the other values will include them too. For example let's say the `title` needs to include colons, wrap the `title` string in double-quote marks `"` to ensure it renders as intended or if a URL contains. ```yaml title: "Storage or: How I Learned to Stop Worrying and Love Ceph" -``` - -## Authoring pages - -While the blog post pages are all composed in Markdown `.md` files, there are a few bonus features. - -### Markdown and HTML - -Pages can contain a mix of Markdown and HTML. This means we can intersperse basic content formatting with more bespoke HTML elements in the same file. - -``` -# Page title - -A paragraph of text, Markdown style. - -- Markdown list items -- Lists are great - -<article class="bespoke"> - <h2>Stick to HTML</h2> -</article> -``` - -The **caveat** here is to ensure that there is always a clear break between Markdown and HTML elements. Mixing and matching the two in a single content block will not work. - -``` -<!-- This won't work --> -<article> - ## Trying for a Markdown heading (and failing) -</article> - -<!-- This will --> -<article> - -## All good here - -</article> -``` - -To learn more about what's possible in Markdown, see [Markdown Guide](https://www.markdownguide.org). - -### Adding links - -Linking to pages throughout the site works in the same way as linking to pages in standard HTML sites. - -We'll most likely be using Markdown's link syntax to link to pages. The links we choose can be relative or absolute. - -If we were on a _blog-posts_ page (`/blog/yyyy/blog-post`), we could link to another blog post page in two ways: - -```md -[Relative link to blog post](../blog-post/) - -[Root relative link to blog post](/blog/yyyy/blog-post/) -``` - -If we need to link to another section/page within the site we can use either method shown above. The `../` prefix can be used to traverse further up the site tree: - -```md -[Relative link to my parent](../) -[Relative link to my grandparent](../../) -[Relative link to a sibling of mine](../sibling-page/) -``` - -Note: these don't need filename `.md`/`.html` extensions. - -Only use absolute URLs for links out of the site: - -```md -[Absolute link to Ceph.io](https://ceph.io/) -``` - -## Dynamic values - -We can interpolate these dynamic values throughout the Markdown. For example, we can save ourselves repeating the page's `title` property for our page title heading by using the `{{ }}` syntax: - -```md ---- -title: Don't repeat yourself ---- - -# Don't repeat yourself -``` - -becomes: - -```md ---- -title: Don't repeat yourself ---- - -# {{ title }} +image: "https://via.placeholder.com/50" ``` ## Blog post structure -The contents of the blog posts can all be found in the `src/locale/news/blog/yyyy/` directories. Any folder/page created within these directories will generate a web page in the site. +The content of the blog posts can be found in the `src/{locale}/news/blog/yyyy/blog-post` directories. Any folder/page created within these directories will generate a web page in the site. ### Folders and file naming -| Input File | Output URL | -| ----------------------------------- | -------------------------------- | -| /src/locale/news/blog/yyyy/index.md | /locale/news/blog/yyyy/blog-post | +| Input File | Output URL | +| ----------------------------------------------- | ---------------------------------- | +| /src/{locale}/news/blog/yyyy/blog-post/index.md | /{locale}/news/blog/yyyy/blog-post | diff --git a/src/en-GB/news/press-releases/README.md b/src/en-GB/news/press-releases/README.md index fa0ffa67..cccfe8ee 100644 --- a/src/en-GB/news/press-releases/README.md +++ b/src/en-GB/news/press-releases/README.md @@ -2,11 +2,7 @@ # Press releases -## Page data - -At the beginning of all press releases, there's a block of data wrapped with ---. This is called frontmatter, and defines data specific to that page in the site. - -The frontmatter data is written in [YAML format](https://yaml.org/) using `key: value` pairs. Frontmatter for the press release pages follows a specific schema: +## Frontmatter ```yaml --- @@ -24,113 +20,23 @@ tags: - `title` (String) — Determines the link text as it appears in the press release navigation card. Also used as the `<title>` for the page.\* - `date` (Date) — Determines the published date of the press release. - `author` (String) — Determines the name of the press release author. -- `image` (String) — Determines the image shown in the press release navigation card and the hero image beneath the title on the press release page. -- `tags` (Array) - This is an array of values that determine the taxonomy of the press release page. - - (String) - Choose from a pre-defined selection of values that apply only to press releases. You can apply as many values as required.\* +- `image` (String) — Determines the asset path for the image shown in the press release navigation card and the hero image beneath the title on the press release page.\* +- `tags` (Array) - This is an array of values that determine the taxonomy of the press release. + - (String) - Choose from a pre-defined selection of values that apply only to press releases. You can apply as many values as required. -\* Careful with any strings that include a colon `:`, as YAML uses this as the key-value pair delimiter. If the title needs to include colons, wrap the `title` string in double-quote marks `"` to ensure it renders as intended. E.g. +\* Careful with any strings that include a colon `:`, as YAML uses this as the key-value pair delimiter. A `URL` will always include a colon and possibly the other values will include them too. For example let's say the `title` needs to include colons, wrap the `title` string in double-quote marks `"` to ensure it renders as intended or if a URL contains. ```yaml title: "Storage or: How I Learned to Stop Worrying and Love Ceph" -``` - -## Authoring pages - -While the press release pages are all composed in Markdown `.md` files, there are a few bonus features. - -### Markdown and HTML - -Pages can contain a mix of Markdown and HTML. This means we can intersperse basic content formatting with more bespoke HTML elements in the same file. - -``` -# Page title - -A paragraph of text, Markdown style. - -- Markdown list items -- Lists are great - -<article class="bespoke"> - <h2>Stick to HTML</h2> -</article> -``` - -The **caveat** here is to ensure that there is always a clear break between Markdown and HTML elements. Mixing and matching the two in a single content block will not work. - -``` -<!-- This won't work --> -<article> - ## Trying for a Markdown heading (and failing) -</article> - -<!-- This will --> -<article> - -## All good here - -</article> -``` - -To learn more about what's possible in Markdown, see [Markdown Guide](https://www.markdownguide.org). - -### Adding links - -Linking to pages throughout the site works in the same way as linking to pages in standard HTML sites. - -We'll most likely be using Markdown's link syntax to link to pages. The links we choose can be relative or absolute. - -If we were on a _press-releases_ page (`/press-releases/yyyy/press-release`), we could link to another press release page in two ways: - -```md -[Relative link to press release](../press-release/) - -[Root relative link to press release](/press-releases/yyyy/press-release/) -``` - -If we need to link to another section/page within the site we can use either method shown above. The `../` prefix can be used to traverse further up the site tree: - -```md -[Relative link to my parent](../) -[Relative link to my grandparent](../../) -[Relative link to a sibling of mine](../sibling-page/) -``` - -Note: these don't need filename `.md`/`.html` extensions. - -Only use absolute URLs for links out of the site: - -```md -[Absolute link to Ceph.io](https://ceph.io/) -``` - -## Dynamic values - -We can interpolate these dynamic values throughout the Markdown. For example, we can save ourselves repeating the page's `title` property for our page title heading by using the `{{ }}` syntax: - -```md ---- -title: Don't repeat yourself ---- - -# Don't repeat yourself -``` - -becomes: - -```md ---- -title: Don't repeat yourself ---- - -# {{ title }} +image: "https://via.placeholder.com/50" ``` ## Press release structure -The contents of the press releases can all be found in the `src/locale/news/press-releases/yyyy/` directories. Any folder/page created within these directories will generate a web page in the site. +The content of the press releases can be found in the `src/{locale}/news/press-releases/yyyy/press-release` directories. Any folder/page created within these directories will generate a web page in the site. ### Folders and file naming -| Input File | Output URL | -| --------------------------------------------- | ---------------------------------------------- | -| /src/locale/news/press-releases/yyyy/index.md | /locale/news/press-releases/yyyy/press-release | +| Input File | Output URL | +| ------------------------------------------------------------- | ------------------------------------------------ | +| /src/{locale}/news/press-releases/yyyy/press-release/index.md | /{locale}/news/press-releases/yyyy/press-release | diff --git a/src/en-GB/solutions/case-studies/README.md b/src/en-GB/solutions/case-studies/README.md index 6da2f441..af0c9662 100644 --- a/src/en-GB/solutions/case-studies/README.md +++ b/src/en-GB/solutions/case-studies/README.md @@ -2,11 +2,7 @@ # Case studies -## Page data - -At the beginning of all case studies, there's a block of data wrapped with ---. This is called frontmatter, and defines data specific to that page in the site. - -The frontmatter data is written in [YAML format](https://yaml.org/) using `key: value` pairs. Frontmatter for the case study pages follows a specific schema: +## Frontmatter ```yaml --- @@ -24,117 +20,27 @@ tags: ``` - `title` (String) — Determines the link text as it appears in the case study navigation card. Also used as the `<title>` for the page.\* -- `image` (String) — Determines the image shown in the case study navigation card and the hero image beneath the title on the case study page. +- `image` (String) — Determines the asset path for the image shown in the case study navigation card and the hero image beneath the title on the case study page.\* - `sponsor` (Array) - This is an array of values that all contribute to the sponsor information on the case study page. - - `name` (String) - Determines the sponsor name as it appears in the case study page.\* - - `logo` (String) - Determines the sponsor logo shown in the case study page. - - `website` (String) - Determines the URL for the sponsor’s website. This is applied to the sponsor logo and button shown in the case study page. + - `name` (String) - Determines the name of the sponsor. + - `logo` (String) - Determines the asset path for the sponsor logo. + - `website` (String) - Determines the URL of the sponsor website which is applied to the sponsor logo and button shown on the case study page. - `tags` (Array) - This is an array of values that determine the taxonomy of the case study page. - - (String) - Choose from a pre-defined selection of values that apply only to case studies. You can apply as many values as required.\* + - (String) - Choose from a pre-defined selection of values that apply only to case studies. You can apply as many values as required. -\* Careful with any strings that include a colon `:`, as YAML uses this as the key-value pair delimiter. If the title needs to include colons, wrap the `title` string in double-quote marks `"` to ensure it renders as intended. E.g. +\* Careful with any strings that include a colon `:`, as YAML uses this as the key-value pair delimiter. A `URL` will always include a colon and possibly the other values will include them too. For example let's say the `title` needs to include colons, wrap the `title` string in double-quote marks `"` to ensure it renders as intended or if a URL contains. ```yaml title: "Storage or: How I Learned to Stop Worrying and Love Ceph" -``` - -## Authoring pages - -While the case study pages are all composed in Markdown `.md` files, there are a few bonus features. - -### Markdown and HTML - -Pages can contain a mix of Markdown and HTML. This means we can intersperse basic content formatting with more bespoke HTML elements in the same file. - -``` -# Page title - -A paragraph of text, Markdown style. - -- Markdown list items -- Lists are great - -<article class="bespoke"> - <h2>Stick to HTML</h2> -</article> -``` - -The **caveat** here is to ensure that there is always a clear break between Markdown and HTML elements. Mixing and matching the two in a single content block will not work. - -``` -<!-- This won't work --> -<article> - ## Trying for a Markdown heading (and failing) -</article> - -<!-- This will --> -<article> - -## All good here - -</article> -``` - -To learn more about what's possible in Markdown, see [Markdown Guide](https://www.markdownguide.org). - -### Adding links - -Linking to pages throughout the site works in the same way as linking to pages in standard HTML sites. - -We'll most likely be using Markdown's link syntax to link to pages. The links we choose can be relative or absolute. - -If we were on a _case-studies_ page (`/case-studies/case-study`), we could link to another case study page in two ways: - -```md -[Relative link to case study](../case-study/) - -[Root relative link to case study](/case-studies/case-study/) -``` - -If we need to link to another section/page within the site we can use either method shown above. The `../` prefix can be used to traverse further up the site tree: - -```md -[Relative link to my parent](../) -[Relative link to my grandparent](../../) -[Relative link to a sibling of mine](../sibling-page/) -``` - -Note: these don't need filename `.md`/`.html` extensions. - -Only use absolute URLs for links out of the site: - -```md -[Absolute link to Ceph.io](https://ceph.io/) -``` - -## Dynamic values - -We can interpolate these dynamic values throughout the Markdown. For example, we can save ourselves repeating the page's `title` property for our page title heading by using the `{{ }}` syntax: - -```md ---- -title: Don't repeat yourself ---- - -# Don't repeat yourself -``` - -becomes: - -```md ---- -title: Don't repeat yourself ---- - -# {{ title }} +image: "https://via.placeholder.com/50" ``` ## Case study structure -The contents of the case studies can all be found in the `src/locale/solutions/case-studies/` directory. Any folder/page created within this directory will generate a web page in the site. +The content of the case studies can be found in the `src/{locale}/solutions/case-studies/case-study` directories. Any folder/page created within these directories will generate a web page in the site. ### Folders and file naming -| Input File | Output URL | -| ------------------------------------------------------ | ------------------------------------------ | -| /src/locale/solutions/case-studies/case-study/index.md | /locale/solutions/case-studies/case-study/ | +| Input File | Output URL | +| -------------------------------------------------------- | ------------------------------------------- | +| /src/{locale}/solutions/case-studies/case-study/index.md | /{locale}/solutions/case-studies/case-study |