Skip to content
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

Add an "About Knative" page #4791

Open
Tracked by #4779
snneji opened this issue Mar 1, 2022 · 4 comments
Open
Tracked by #4779

Add an "About Knative" page #4791

snneji opened this issue Mar 1, 2022 · 4 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.

Comments

@snneji
Copy link
Contributor

snneji commented Mar 1, 2022

Task

  1. Add a README.md page to the "About" section that includes the following conceptual info:
    • high level info about Knative Serving + Eventing
    • architecture info
    • diagrams
  2. The page should be similar to Istio: https://istio.io/latest/about/service-mesh/
  3. The page should be the first page in the "About" section as it will be like an overview page.
  4. Page must have links to Serving, Eventing, Install
  5. Replace the link for the "Explore Knative" button on the homepage with a link to this page.

Questions to answer as follow up from #4668

  1. What is Knative?

Knative is a system that works on top of Kubernetes. It helps development teams manage, monitor, and operate Kubernetes in a way that requires less technical knowledge and time. Knative is open-source, finding support and growth through a combination of individual contributors and industry-leading companies.

  1. What's the difference between Knative Serving and Knative Eventing?

Knative has two main elements named Knative Serving and Knative Eventing. While they manage different tasks and outcomes and can operate independently, together, they help make Knative a powerful tool for dev teams and IT professionals.
Knative Serving runs serverless containers on Kubernetes with ease. Knative takes care of the details of networking, autoscaling (even to zero), and revision tracking. You have to focus on your core logic. Knative Eventing allows for universal subscription, delivery, and management of events. Teams can build modern apps by attaching compute to a data stream with declarative event connectivity and a developer-friendly object model.

  1. Do I need to use Istio?
  2. What foundation is it under (CNCF, LF, etc)?
  3. Does Knative support serverless functions?
  4. Link to spin off section about users / adopters / case studies

Additional info

Spin off section about users / adopters / case studies
(TODO: decide on name for this)

  • Testimonials
  • Case Studies
    • deepc
    • outfit7
    • puppet
    • NYT (future)
    • Optum (future)
  • Is there a managed cloud version of Knative?
  • Who are the contributors or companies backing the project?
  • Who is using Knative ? -> Link to Adopters
@github-actions
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 21, 2022
@abrennan89
Copy link
Contributor

As far as I'm concerned, this page could also cover all the requests proposed on #4668 and we can close that one?

@abrennan89 abrennan89 added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. and removed priority/high lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jun 22, 2022
@abrennan89
Copy link
Contributor

Removed FAQ from the list because I think these are sort of a nonsense thing and shouldn't be required if our info is laid out properly so that it's easy to find.

@abrennan89
Copy link
Contributor

I'd say case studies and testimonals should also be a separate page, not part of "About Knative" since they're not really explaining anything conceptual.

@abrennan89 abrennan89 self-assigned this Jul 28, 2022
@snneji snneji moved this to In design in Docs WG Roadmap Aug 30, 2022
@abrennan89 abrennan89 removed their assignment Sep 26, 2022
@abrennan89 abrennan89 moved this from In design to Icebox in Docs WG Roadmap Sep 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.
Projects
Status: Icebox
Development

No branches or pull requests

2 participants