-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Issues: knative/docs
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Inconsistent Text Color and Contrast in Knative Components Section
kind/bug
Categorizes issue or PR as related to a bug.
#6071
opened Jul 23, 2024 by
pranay911
Text size of the button is not consistent in the pre-released version of the website
kind/bug
Categorizes issue or PR as related to a bug.
#6067
opened Jul 22, 2024 by
Leo6Leo
Elements are not center aligned in the pre-release version of the website
kind/bug
Categorizes issue or PR as related to a bug.
#6066
opened Jul 22, 2024 by
Leo6Leo
Proposal: IBM Case Study to Knative Website
kind/ux
Issues or PRs related to UX changes
#6057
opened Jul 16, 2024 by
nrrso
Bug: Inconsistent display of Marque in Windows
kind/bug
Categorizes issue or PR as related to a bug.
#5996
opened May 27, 2024 by
TenzDelek
KnativeServing CR overriding the queue-proxy registry which didn't work
kind/bug
Categorizes issue or PR as related to a bug.
#5985
opened May 22, 2024 by
xiezhao
Improve Site Performance with Lazy Loading and WEBP Images
#5981
opened May 20, 2024 by
shivamgupta2020
Provide more example usage for channel-configuration in the doc
kind/bug
Categorizes issue or PR as related to a bug.
#5956
opened May 2, 2024 by
Leo6Leo
Responsive Design Enhancements for knative.dev Home Page
kind/bug
Categorizes issue or PR as related to a bug.
#5876
opened Feb 22, 2024 by
prajjwalyd
Adding the explanation for which configuration takes preference over the other in Default Broker Config
#5856
opened Feb 9, 2024 by
Leo6Leo
Decide on a method for tracking design changes on GitHub
#5782
opened Nov 30, 2023 by
zainabhusain227
Re-think the current Serving structure
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
triage/accepted
Issues which should be fixed (post-triage)
#5703
opened Oct 3, 2023 by
ReToCode
Change the title in the website
kind/bug
Categorizes issue or PR as related to a bug.
#5634
opened Jul 20, 2023 by
aliok
Add more information about Broker Developer Configuration Options
good first issue
help wanted
#5526
opened Apr 4, 2023 by
creydr
List adopters on knative.dev website
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
#5388
opened Jan 23, 2023 by
zroubalik
Opting out cookies ...
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
#5349
opened Dec 7, 2022 by
resoli
Previous Next
ProTip!
Mix and match filters to narrow down what you’re looking for.