-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Restructure "Eventing component" section #1923
Comments
I think the eventing only install section is covered now in the docs here https://knative.dev/docs/install/any-kubernetes-cluster/ ? @carieshmarie wdyt? Can we check off that item in the list? |
Issues go stale after 90 days of inactivity. Send feedback to Knative Productivity Slack channel or file an issue in knative/test-infra. /lifecycle stale |
Reopening for now but we need revisit this |
I think creating issues like this that are one big long list actually end up getting ignored a lot of the time because it's too much scope / too much like an epic rather than a single issue to track a docs change. Maybe try splitting the list up? |
Note to self: Conceptual info re producers / consumers in this PR can be added: #3476 |
Note to self: Related to knative/ux#39 |
For observability and debugging, these require engineering input/work that are already tracked as other issues:
|
Once you split out the tasks from this issue (I removed some of the original list items and made them their own issues), what's left is a pretty generic request for information. I think just adding info about "event producers and consumers" out of context doesn't really add any value, so I'd like for us to close this one for now and revisit this when we have bandwidth to flesh out some more conceptual topics about Knative as a whole. Probably makes more sense to do this after we've split docs into different "guides" for different personas as well, so that we know what type of info is required. |
Align content with the developer flow and arrange content into logical sections.
View proposed nav structure
The text was updated successfully, but these errors were encountered: