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

Render partner pages using a content adapter #46425

Open
sftim opened this issue May 17, 2024 · 1 comment
Open

Render partner pages using a content adapter #46425

sftim opened this issue May 17, 2024 · 1 comment
Labels
area/web-development Issues or PRs related to the kubernetes.io's infrastructure, design, or build processes kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@sftim
Copy link
Contributor

sftim commented May 17, 2024

This is a Feature Request

What would you like to be added
[If we like the idea], use a Hugo content adapter to render a stub page for each partner in the CNCF landscape.

Why is this needed
Rather than embed a generic <iframe> we could, at least in theory, add a page to the site about each partner. We can also have a list page that helps you see all of the partners.

The page about each partner could be customized to look different depending on what kind of partner they are. For example, the first partner in the list at the time of writing is 3-shake, a KCSP. The generated partner page https://k8s.io/partners/3-shake could have a prominent KCSP badge, the 3-shake logo and a hyperlink to https://3-shake.com/
If there's additional data in the landscape, we could consume that too.

I would not localize the partner pages if we did that (I'd have them as English only)

Comments
/area web-development

We'd also need to use Hugo v0.126 or later.

@sftim sftim added the kind/feature Categorizes issue or PR as related to a new feature. label May 17, 2024
@k8s-ci-robot k8s-ci-robot added area/web-development Issues or PRs related to the kubernetes.io's infrastructure, design, or build processes needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 17, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/web-development Issues or PRs related to the kubernetes.io's infrastructure, design, or build processes kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

2 participants