-
Notifications
You must be signed in to change notification settings - Fork 14.7k
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
Discover the scope and requirements for implementing the Docsy Hugo template #15683
Comments
/assign |
/unassign |
Would be nice to have a collapsible left menu, as requested in issue #16120 |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In response to this:
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/test-infra repository. |
Start research in the Docsy template
Create a new GitHub issue describing the requirements and scope of work required to implement the template. (Make it easy for other stakeholders to understand the extent of the challenge and what's required to implement the template.)
Get stakeholder input, then implement a solution. (Get everyone on board, then fix the problem. The template should be uniformly applied across the site with expected results.)
/sig docs
/priority important-soon
Assign to @aimeeu
The text was updated successfully, but these errors were encountered: