Skip to content

Conversation

@skmahe1077
Copy link

Fixes #6303

This PR updates documentation page titles and navigation labels for consistency across the Knative Docs site based on the recommendations in issue.

@linux-foundation-easycla
Copy link

linux-foundation-easycla bot commented Oct 17, 2025

CLA Signed

The committers listed above are authorized under a signed CLA.

@netlify
Copy link

netlify bot commented Oct 17, 2025

Deploy Preview for knative ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit 06ae115
🔍 Latest deploy log https://app.netlify.com/projects/knative/deploys/68f93bcd5cde720007ddd985
😎 Deploy Preview https://deploy-preview-6457--knative.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@knative-prow
Copy link

knative-prow bot commented Oct 17, 2025

Welcome @skmahe1077! It looks like this is your first PR to knative/docs 🎉

@knative-prow knative-prow bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Oct 17, 2025
@skmahe1077 skmahe1077 force-pushed the fix_rename_pages_6303 branch 2 times, most recently from 2d0b95a to c096fee Compare October 18, 2025 15:54
@dprotaso
Copy link
Member

cc @dwelsch-esi @iRaindrop for review here

- Install Knative using quickstart: getting-started/quickstart-install.md
- Knative Functions:
- About Knative Functions: getting-started/about-knative-functions.md
- Knative Functions: getting-started/about-knative-functions.md
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't want to introduce stutter (eg. #6431)

Should we maybe title these sections Getting Started?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will change Knative Functions to "Getting Started"

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Modified Getting Started from Knative Functions

- Developer Tasks:
- Services:
- About Knative Services: serving/services/README.md
- Knative Services: serving/services/README.md
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't know the right title here

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I’ve removed “About” from the title for consistency with other sections. Happy to update it if there’s a preferred alternative

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It turns out that it doesn't matter in this case, because building the nav causes this README.md page to be organized under Services as a clickable link, and "About Knative Services" isn't shown at all.

Example: https://knative.dev/docs/serving/services/

Copy link
Member

@dprotaso dprotaso Oct 21, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh - that's confusing - what's the best way to represent that in the nav yaml file so it's clear?

Copy link
Member

@evankanderson evankanderson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One real comment on the top-level title for Knative Eventing (though I could be convinced that we need metadata rather than a longer title), and I agree with Dave that "Getting Started" or moving the files to clickable parent navigation are better for the tutorial concept sections for Functions and Eventing (apparently we never wrote one for serving!)

/approve

(Will wait on the other changes for /lgtm)

---

# Knative Eventing - The Event-driven application platform for Kubernetes
# Eventing
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note that because we have explicit .nav.yaml, the titles here aren't reflected in the side nav, so we can have longer titles here and shorter titles in the nav.

My $0.02 here would be to keep the longer name for SEO purposes.

- Traffic splitting: getting-started/first-traffic-split.md
- Knative Eventing:
- About Knative Eventing: getting-started/getting-started-eventing.md
- Knative Eventing: getting-started/getting-started-eventing.md
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should use the same pattern as line 15.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Modified Getting started from Knative Eventing

- Developer Tasks:
- Services:
- About Knative Services: serving/services/README.md
- Knative Services: serving/services/README.md
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It turns out that it doesn't matter in this case, because building the nav causes this README.md page to be organized under Services as a clickable link, and "About Knative Services" isn't shown at all.

Example: https://knative.dev/docs/serving/services/

- Channel based Broker: eventing/brokers/broker-types/channel-based-broker/README.md
- Apache Kafka:
- About Apache Kafka Broker: eventing/brokers/broker-types/kafka-broker/README.md
- Knative Broker for Apache Kafka: eventing/brokers/broker-types/kafka-broker/README.md
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This title change also doesn't matter, because the singleton with README.md gets parented to "Apache Kafka". I do think the longer name in the title makes sense -- it just won't show up in the nav either way.

@knative-prow
Copy link

knative-prow bot commented Oct 21, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: evankanderson, skmahe1077

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@knative-prow knative-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 21, 2025
@evankanderson
Copy link
Member

/assign

@skmahe1077 skmahe1077 force-pushed the fix_rename_pages_6303 branch from c096fee to b8dbd3d Compare October 22, 2025 20:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Rename pages

3 participants