-
Notifications
You must be signed in to change notification settings - Fork 426
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
Write a Getting Started guide #1364
Comments
Hello! May I work on this issue? |
Certainly! |
@tomkerkhove I would like to work on this issue. But can you provide the directory where files needs to be added. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
is this issue still relevant ? |
Hey @shubhusion, I am working on it, submitted PR. Please find other issues from here to work on. |
Great, thanks for letting me know! |
Write a task-based, step-by-step workflow for new users. Start with the current KEDA Documentation section.
This issue tracks recommended changes resulting from an analysis of the KEDA documentation commissioned by CNCF. The analysis and supporting documents are here: https://github.com/cncf/techdocs/tree/main/assessments/0011-keda/
Use-Case
Assume the new user has no experience with KEDA and is fairly new to Kubernetes. The current documentation assumes that users know how to deploy and use Kubernetes Custom Resources, and that using KEDA is a matter of knowing the right configuration parameters and deploying the right resources. This might be true for veteran users, but new users want explicit, foolproof instructions.
Specification
The following outline has been annotated to emphasize the purpose of each section. Links are to existing pages that can be used as-is or provide a starting point. Pages with multiple procedures (for example, the "Deploying KEDA" page) should be split into multiple pages, one for each procedure.
The text was updated successfully, but these errors were encountered: