Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[v2-2] Add Kubecon page for KubeCon Paris 2024 #1835

Merged
merged 1 commit into from
Mar 1, 2024
Merged

Conversation

fluxcdbot
Copy link
Member

Automated backport to v2-2, triggered by a label in #1804.

Copy link
Member

@kingdonb kingdonb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 🏆 LGTM

@kingdonb
Copy link
Member

kingdonb commented Mar 1, 2024

Looks like I may need to fix my github user so backports get the correct signoff

I can add it manually which will (hopefully) not break anything?

There is no permalink on the fluxcd.io site for each content, we'll just
reuse /kubecon each time - for SEO purposes this is better.

(A permanent content archive will be hosted @ fluxcd/community repo,
where we can archive `KUBECON.md` as `attic/KUBECON24EU.md` for example)

* set KUBECON.md as external source
* try adding css rules to some classes
* Make more kubecon page formatting classes

I've added "clearfix" after reading w3schools about css float
https://www.w3schools.com/css/css_float.asp

* More CSS things

Signed-off-by: Kingdon Barrett <[email protected]>
Signed-off-by: Kingdon P Barrett <[email protected]>
(cherry picked from commit 78c7e10)
@kingdonb kingdonb force-pushed the backport-1804-to-v2-2 branch from 3879797 to 528acf1 Compare March 1, 2024 20:25
@kingdonb kingdonb merged commit 57ae8fa into v2-2 Mar 1, 2024
5 checks passed
@kingdonb kingdonb deleted the backport-1804-to-v2-2 branch March 1, 2024 20:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants