All decks

Digital sovereignty,
built in the open.

A reveal.js template for operational, open cloud infrastructure.

PROJECT YAOOK

SUMMIT 2026

FROM EUROPE · FOR EUROPE

Agenda

What we'll cover

Slide primitives Titles, sections, lists, columns and cards on one grid.
Numbers & evidence Stat blocks, tables and quotes that read from the back row.
Writing in Markdown Author slides as plain text — inline or from a .md file.
The brand palette Dark Blue as the field, Green as the typographic accent.

01 / 04

Slide primitives

A drop-in identity: Dark Blue ground, Green for type, one consistent grid.

Overview

Ready to use

Title, section & content layouts with a consistent grid.
Cards, stats and quotes for structure without clutter.
Code blocks with syntax highlighting for technical talks.
A light-slide variant when you need contrast in a long deck.

Two-column

Text beside detail

Split the canvas when a point needs support — a definition next to an example, or a claim next to its evidence.

The left column carries the argument; the right holds the artifact.


        apiVersion: yaook/v1
        kind: OpenStackDeployment
        metadata:
          name: sovereign-cloud
        spec:
          operational: true
          openSource: true

Projects

Three across

Orchestration

Krake

Schedules containerized and virtualized workloads across distributed, heterogeneous clouds.

Lifecycle

Yaook

Fully automated OpenStack lifecycle management — free and operational by default.

GitOps

Yake

GitOps-driven Gardener installation and upgrade tooling for simplified provisioning.

02 / 04

The numbers that matter

Big figures read fastest against the Dark Blue field.

By the numbers

Stat blocks

100%

Operational
infrastructure

100%

Open
source

Community
projects

Positioning

Talk is silver, development is gold. — ALASCA · community principle

Contrast

The light variant

Add class="light" to any <section> to flip the palette to paper. Useful for diagrams, dense tables, or resetting the eye mid-deck.

Same grid, inverted tones.
Green stays the accent throughout.

Layer	Tool	State
Compute	Yaook	Stable
Orchestration	Krake	Active
Cluster	Yake	Beta

Build up

Reveal one point at a time

First, name the problem.
Then, show the mechanism.
Finally, land the takeaway.

03 / 04

Write slides in Markdown

Plain text in, themed slides out — no build step, no extra tooling.

<!--
        SPDX-FileCopyrightText: 2026 ALASCA e.V. <hello@alasca.cloud>

SPDX-License-Identifier: Apache-2.0
        -->

<div class="index">Markdown</div>

## A slide written as prose

---

<p class="eyebrow">Markdown · inlined</p>

## `<slide src="…md">`

- The file is carried **into** the deck at build time, so it survives `file://`.
        - `---` on its own line starts the next slide, `--` goes one level down.
        - Slide and element classes work as they do anywhere else.

Note: Speaker notes live here and never reach the projector.

<p class="eyebrow">Markdown · inlined · detail</p>

## Still just a slide

Vertical slides, code and the theme all come along:

```yaml
        apiVersion: yaook/v1
        kind: OpenStackDeployment
        metadata:
          name: sovereign-cloud
        spec:
          operational: true
        ```

Nested · top

Overview slide

Keep the headline here and push supporting detail downward, so the audience only descends when they want the depth.

Nested · detail

Supporting detail

This slide sits below the previous one in the stack — ideal for appendix material or a deep dive on demand.

04 / 04

The brand palette

Dark Blue dominates. Green carries the typography. Secondary colours support.

Primary

Green & Dark Blue

Green#51E064 · Pantone 360 C

Dark Blue#243746 · Pantone 7546 C

Black#000000

White#FFFFFF

Dark Blue always dominates in proportion over Green. Green is reserved for typographic elements — headings, highlights, numbers and rules.

Secondary

Support, never dominate

Sand#E1E173

Yellow#F5E604

Orange#EC7629

Red#E1646E

Light Blue#7BCAEF

Blue#0E85A6

Dark Blue 2#08162A

Use these for infographics, diagrams and tables only. Lime #A7F320 is reserved for the ALASCA Summit and must not appear elsewhere.

Background image

The whole picture

Background image

Top third

Background image

Middle third

Background image

Bottom third

Diagrams · mermaid

A diagram, written as text

            flowchart LR
              A[Write a slide] --> B{validate}
              B -- passes --> C[build.py]
              B -- fails --> A
              C --> D[(public/)]
              D --> E[Pages]
              D --> F[PDF]

Mermaid is vendored, so the diagram is drawn on the machine presenting it — nothing is fetched. Colours come from the theme, not from the slide.

<!--
        SPDX-FileCopyrightText: 2026 ALASCA e.V. <hello@alasca.cloud>

SPDX-License-Identifier: Apache-2.0
        -->

<p class="eyebrow">Diagrams · mermaid · Markdown</p>

## A fenced block is a diagram

```mermaid
        sequenceDiagram
            autonumber
            participant O as Operator
            participant C as CI
            participant P as Pages
            O->>C: git push
            C->>C: validate.py
            C->>P: build.py
            P-->>O: preview URL
            Note over C,P: never leaves the repo
        ```

Note: A fence in Markdown is the way to write a diagram containing `<` or `>` — in an HTML slide those would be read as tags.

---

<p class="eyebrow">Diagrams · mermaid · light</p>

## The same diagram, on paper

```mermaid
        flowchart TD
            subgraph cloud [Sovereign cloud]
              A[OpenStack] --> B[Kubernetes]
              B --> C[Workloads]
            end
            A --> D[(Ceph)]
        ```

A diagram inherits the slide it sits on — `class="light"` restates the `--mm-*`
        tokens, and the renderer reads them off the element.

Pictures

An image, from the deck's own folder

templates/template/img/example.svg

Drop the file in img/ beside deck.html and point at it. The folder travels with the deck when it is published, so the picture is there over file:// too.

Add class="framed" to give a screenshot an edge.
An image is capped at --img-height; raise it on the section when a picture is the point of the slide.

Slot machine

Three reels, one answer

Cloud · Server · Gear — the three that had to line up. The line only appears once the last reel has stopped, so the room reads the pictures first.

Slot machine · tuned

Same machine, different dial

🛠️ 📦 🧊 🔭 🧪

🧊 🔭 🧪 📦 🛠️

🧪 🛠️ 📦 🧊 🔭

Click the machine to spin it again. Nothing here is fetched: the reels are CSS transforms, the deceleration is one transition, and the result is whatever the slide marked class="win".

The set

Four across

Compute

The machines the workloads actually land on.

Network

Everything between them, and the way out.

Storage

What survives a machine going away.

Observability

Whether any of it is on fire, and where.

The set

Six in two rows

Runs it

Orchestration

Where a workload runs, and what happens when that stops being true.

Lifecycle

Install, upgrade, replace — without a maintenance window each time.

Keeps it running

GitOps

The cluster is whatever the repository says it is.

Monitoring

One answer to “is it healthy”, for every layer below.

Underneath

Peering

How the traffic reaches the rest of the internet.

Bare metal

The floor of the stack: racks, boot, and the network under them.

The set

Eight in two rows

Compute

The machines underneath.

Network

Everything between them.

Storage

What outlives a node.

Registry

Where the images come from.

Monitoring

Health, on every layer.

Backup

Yesterday, still available.

Identity

Who may ask for what.

Isolation

Tenants that cannot see each other.

Project

Yaook

Fully automated OpenStack lifecycle management — an operator per service that installs it, watches it, upgrades it and repairs it.

Maintained by

A. PersonTech lead
B. PersonRelease
C. PersonDocs

Written in

Python Go Helm

License

Apache-2.0

Where it lives

Code gitlab.com/yaook/operator
Docs docs.yaook.cloud

yaook.cloud

Context

OpenStack
Kubernetes
Lifecycle Management
Automation

Thank you. Stay in touch.

Web

Website alasca.cloud
Summit 2026 alasca.cloud/alasca-summit-2026
Tech-Talks alasca.cloud/alasca-tech-talks
Podcast alasca.cloud/alasca-opensnac-der-podcast
GitLab gitlab.com/alasca.cloud

Community

Mastodon mastodon.social/@alasca
LinkedIn linkedin.com/company/alasca-cloud
Mailing lists lists.alasca.cloud
Matrix #ALASCA:matrix.org
YouTube youtube.com/@alasca_e.V.

Digital sovereignty,built in the open.

What we'll cover

Slide primitives

Ready to use

Text beside detail

Three across

Krake

Yaook

Yake

The numbers that matter

Stat blocks

The light variant

Reveal one point at a time

Write slides in Markdown

Overview slide

Supporting detail

The brand palette

Green & Dark Blue

Support, never dominate

The whole picture

Top third

Middle third

Bottom third

A diagram, written as text

An image, from the deck's own folder

Three reels, one answer

Same machine, different dial

Four across

Compute

Network

Storage

Observability

Six in two rows

Orchestration

Lifecycle

GitOps

Monitoring

Peering

Bare metal

Eight in two rows

Compute

Network

Storage

Registry

Monitoring

Backup

Identity

Isolation

Yaook

Thank you. Stay in touch.

Web

Community

Digital sovereignty,
built in the open.