* Add front matter to Build files (#833) * Update README.md * Adding front matter to builds.md * Update installing-build-component.md * Update README.md Revert changes so Richie can handle this with the index file * Update builder-contract.md * Update personas.md * Update auth.md * Update creating-builds.md * Update build-templates.md * sentence case * sentence case * sentence case * Adding frontmatter to /install/ (#834) * Adds front matter to Serving (#838) * Update accessing-logs.md * Update accessing-metrics.md * Update accessing-traces.md * Update cluster-local-route.md * Update debugging-application-issues.md * Update debugging-performance-issues.md * Update gke-assigning-static-ip-address.md * Update installing-logging-metrics-traces.md * Update outbound-network-access.md * Update setting-up-a-logging-plugin.md * Update using-a-custom-domain.md * Update using-an-ssl-cert.md * Update using-cert-manager-on-gcp.md * Update using-external-dns-on-gcp.md * site index for fluentd folder (#839) * add Hugo index files and frontmatter (#840) * hugo build files for autogen refdocs (#841) * move resources and readme (#843) * site: add blog (#837) * add blog folder * switch to sentence case * site: add community and contributing (#836) * add _index.md files and front matter * switch to sentance case caps * fix weights * Update community/samples/README.md Co-Authored-By: RichieEscarez <rescarez@google.com> * site: restructure content into a "docs" directory (#842) * move content into a 'docs' directory * inject additional 'docs' directory * site: add build files and front matter to serving samples (#850) * new _index.md files and front matter * serving samples + fix urls * remove file * add PR#851 - channels (#853) * Update README.md (#854) * Remove README.md from all links (#855) * Remove README.md from all links * mend * mend * mend * Update _index.md * Update _index.md * Update _index.md * Update _index.md * fix links in community (#857) * Update _index.md (#856) * Update _index.md * Update _index.md * Update _index.md * Update _index.md * Update _index.md * Update _index.md * Update _index.md * Update _index.md * Update _index.md * Update _index.md * Update _index.md * Update _index.md * Update _index.md * Update _index.md Adds missing pointer to README * Update _index.md * Update _index.md * Update _index.md * Update _index.md * Update _index.md * Update _index.md * Update _index.md * Update _index.md * Update _index.md * Update _index.md * Update _index.md * Update _index.md * Update _index.md * Update _index.md * Update _index.md * Update _index.md * Update _index.md * Update _index.md * Update _index.md * Update _index.md * revert * fix build links (#858) * site: fix eventing links (#859) * fix eventing links * Update README.md * fix install links (#860) * site: fix serving links (#861) * fix serving links * Update using-external-dns-on-gcp.md * remove hardcoded github link (#863) * Update README.md (#864) Fix links by removing md file extensions. * Fix links (#866) * Fix links * Update installing-build-component.md * Update builder-contract.md * add missing hello-world directory (#865) * Link fixes for Build (#867) * Fix links * Update installing-build-component.md * Update builder-contract.md * Update creating-builds.md * Update builder-contract.md * Update builds.md * Update creating-builds.md * Update installing-build-component.md * Update installing-build-component.md * Update creating-builds.md * Update creating-builds.md * Update builds.md * Update build-templates.md * convert to Hugo rel link * Manually run prettier.io (#880) * Manually run prettier.io Trying to fix the stuff that hits prettier.io bugs. * Fix prettier.io issues. * Revert manual link fixes (use new build script instead) (#927) * Revert "convert to Hugo rel link" This reverts commit |
||
---|---|---|
.. | ||
CODE-OF-CONDUCT.md | ||
CONTRIBUTING.md | ||
DOCS-CONTRIBUTING.md | ||
README.md | ||
REVIEWING.md | ||
ROLES.md | ||
SLACK-GUIDELINES.md | ||
STEERING-COMMITTEE.md | ||
TECH-OVERSIGHT-COMMITTEE.md | ||
VALUES.md | ||
WORKING-GROUP-PROCESSES.md | ||
WORKING-GROUPS.md | ||
_index.md |
README.md
Important. Before proceeding, please review the Knative community Code of Conduct.
If you any have questions or concerns, please contact the authors at knative-code-of-conduct@googlegroups.com.
Welcome!
Welcome to the Knative community!
This is the starting point for becoming a contributor - improving code, improving docs, giving talks, etc.
Other Documents
- Code of Conduct - all contributors must abide by the code of conduct
- Contributing to Knative - guidelines and advice on becoming a contributor
- Working Groups - describes our various working groups
- Working Group Processes - describes how working groups operate
- Technical Oversight Committee - describes our technical oversight committee
- Steering Committee - describes our steering committee
- Community Roles - describes the roles individuals can assume within the Knative community
- Reviewing and Merging Pull Requests - how we manage pull requests
Introduction
Knative is a Kubernetes-based platform to build, deploy, and manage modern serverless workloads. See Knative docs for in-depth information about using Knative.
Knative authors
Knative is an open source project with an active development community. The project was started by Google but has contributions from a growing number of industry-leading companies. For a current list of the authors, see Authors.
Authoring samples
Beyond the official documentation there are endless possibilities for combining tools, platforms, languages, and products. By submitting a tutorial you can share your experience and help others who are solving similar problems.
Community tutorials are stored in Markdown files under the community
folder
Community Samples. These documents
are contributed, reviewed, and maintained by the community.
Submit a Pull Request to the community sample directory under the Knative
component folder that aligns with your document. For example, Knative Serving
samples are under the serving
folder. A reviewer will be assigned to review your
submission. They'll work with you to ensure that your submission is clear, correct,
and meets the style guide, but it helps if you follow it
as you write your tutorial.
Meetings and work groups
Knative has public and recorded bi-weekly community meetings.
Each project has one or more working groups driving the project, and Knative as a single technical oversight community monitoring the overall project.
How can I help
If you're looking for something to do to get your feet wet working on Knative, look for GitHub issues marked with the Help Wanted label:
Even if there's not an issue opened for it, we can always use more testing throughout the platform. Similarly, we can always use more docs, richer docs, insightful docs. Or maybe a cool blog post? And if you're a web developer, we could use your help in spiffing up our public-facing web site.
Questions and issues
If you're a developer, operator, or contributor trying to use Knative, the following resources are available for you:
For contributors to Knative, we also have Knative Slack.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License.