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.

Sign up for GitHub

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

Jump to bottom

Enforce explicit "opt in" for Spin In Pods (Legacy) article in Spin v2 TOC #1439

Open
macolso opened this issue Dec 9, 2024 · 2 comments · May be fixed by #1449
Open

Enforce explicit "opt in" for Spin In Pods (Legacy) article in Spin v2 TOC #1439

macolso opened this issue Dec 9, 2024 · 2 comments · May be fixed by #1449
Assignees
@karthik2804

Comments

@macolso
Copy link
Contributor

macolso commented Dec 9, 2024

We'd like to avoid new users accidentally picking up legacy content while still serving existing users who may not be ready to migrate off of the older technology. To do this, we'll add additional gates that require user opt-in to view the tutorial for spin k8s content.

This will hopefully decrease frequency of users accidentally landing on legacy content.
@itowlson
Copy link
Contributor

itowlson commented Dec 9, 2024

Proposed approach:

On entering the page, the content is hidden, and it instead displays a message explaining the legacy status of the content and guiding readers to more current content. The message also contains a link to unhide the legacy content: when clicked, the entrance message disappears and the existing content re-appears.

The proposed wording is:

For the best user experience deploying Spin applications to Kubernetes, we recommend using SpinKube and Fermyon Platform for Kubernetes. (link to the k8s page)

If you are using the legacy experience and would like assistance in migrating, please reach out on Discord. To proceed to the unsupported "Spin in pods" solution, click here. (link which does the JS unhide thing)

This presumably affects both the v1/kubernetes and v2/spin-in-pods-legacy pages, but we may be able to skip v1 if it's difficult.

@itowlson
Copy link
Contributor

itowlson commented Dec 9, 2024

Is it also possible to tell search engines not to index these pages?

@karthik2804 karthik2804 linked a pull request Dec 20, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@karthik2804 karthik2804

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

add explicit opt in for spin-on-pods karthik2804/developer
3 participants
@itowlson @karthik2804 @macolso