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.

Sign up for GitHub

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

Jump to bottom

Change the title in the website #5634

Open
aliok opened this issue Jul 20, 2023 · 23 comments · Fixed by erharjotsingh/docs#3
Open

Change the title in the website #5634

aliok opened this issue Jul 20, 2023 · 23 comments · Fixed by erharjotsingh/docs#3
Assignees
@JonConstantine01
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@aliok
Copy link
Member

aliok commented Jul 20, 2023

Spin-off from #5407

Current title of Knative in the website is:

"Knative is an Open-Source Enterprise-level solution to build Serverless and Event Driven Applications"

Based on the the discussion in the related issue, #5407 (comment),

I suggest we change it to

"Knative is an Open-Source Enterprise-level solution to build, deploy, and scale event-driven applications."

cc @knative/steering-committee
@aliok aliok added the kind/bug Categorizes issue or PR as related to a bug. label Jul 20, 2023
@aliok aliok mentioned this issue Jul 20, 2023
Closed
@aliok
Copy link
Member Author

aliok commented Jul 20, 2023

Related: knative/eventing#7030
We want to change the title/tagline in Eventing as well.

@erharjotsingh
Copy link
Contributor

/assign erharjotsingh

erharjotsingh added a commit to erharjotsingh/docs that referenced this issue Jul 24, 2023
@erharjotsingh
Fixing knative#5634: Update home.html
56029c7
@erharjotsingh erharjotsingh mentioned this issue Jul 24, 2023
Merged
erharjotsingh added a commit to erharjotsingh/docs that referenced this issue Jul 24, 2023
@erharjotsingh
Merge pull request #3 from erharjotsingh/erharjotsingh-patch-3
fe6885c 
Fixing knative#5634: Update home.html to fix title issue with knative
@erharjotsingh
Copy link
Contributor

Hello @aliok
I am working on this. I am waiting for PR approval for my other issue, once that is done I will merge these changes. Thanks!

@aliok
Copy link
Member Author

aliok commented Jul 24, 2023

/assign erharjotsingh

Thanks!

The members of @knative/steering-committee need to decide on what title to use though. (https://github.com/knative/community/blob/main/STEERING-COMMITTEE.md)

@erharjotsingh
Copy link
Contributor

Sure, waiting for a feedback from @knative/steering-committee
Thanks!

@erharjotsingh erharjotsingh removed their assignment Jul 24, 2023
knative-prow bot pushed a commit that referenced this issue Jul 31, 2023
@erharjotsingh
Fixing #5537: Adding mandatory target annotation and their units. (#5629
9c9f95e 
)

* Issue# #5537: Update autoscaling-metrics.md to add the mandatory target values

As per issue  #5537,  creating this PR for adding mandatory target annotation.

* Fixing #5537: Implementing PR comments

* Fixing #5634: Update home.html

* Reverting the commit for other issue

Reverting the commit for other issue so that I can fork one branch per issue

* Fixing #5537: Adding review comments

* Fixing#5537: Updating note formatting

* Update autoscaling-metrics.md

* Update autoscaling-metrics.md

* Update autoscaling-metrics.md

* Update autoscaling-metrics.md
@shaaoni
Copy link

shaaoni commented Oct 6, 2023

Hey @aliok Is there anything is this project still undone? I would like to contribute to it then.

@JonConstantine01
Copy link

/assign JonConstantine01

@vinfinity7 vinfinity7 mentioned this issue Oct 10, 2023
Closed
@ReToCode
Copy link
Member

/assign vinfinity7

@knative-prow
Copy link

knative-prow bot commented Oct 10, 2023

@ReToCode: GitHub didn't allow me to assign the following users: vinfinity7.

Note that only knative members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign vinfinity7

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@vinfinity7
Copy link
Contributor

@ReToCode Can you review again and tell me what shall be the new title

@ReToCode
Copy link
Member

The steering committee has to decide, which has not yet happened. So this issue is not really ready to work on.

@ReToCode
Copy link
Member

@aliok any updates from SC in this regard?

@aliok aliok moved this to 🆕 New in Steering Committee Backlog Dec 11, 2023
@aliok
Copy link
Member Author

aliok commented Dec 11, 2023

Thanks for the ping @ReToCode

I put this issue to SC's backlog now

@aliok
Copy link
Member Author

aliok commented Dec 19, 2023

Evan's comment: we might lose the SEO for serverless. Let's check the traffic analytics for this first.

@github-actions 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 Mar 19, 2024
@aliok
Copy link
Member Author

aliok commented Mar 26, 2024

@evankanderson I don't have access to Google Analytics to check this. Do you have access? If so, can you give all steering members access?

@nainaz nainaz moved this from 🆕 New to 📋 Backlog in Steering Committee Backlog Mar 26, 2024
@github-actions github-actions bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 27, 2024
@nainaz
Copy link
Contributor

nainaz commented Mar 27, 2024 via email

@DhairyaMajmudar
Copy link

Hi @aliok @ReToCode is this issue still up for take?

Would like to open a PR is so : )

@aliok
Copy link
Member Author

aliok commented May 27, 2024

hey @DhairyaMajmudar

We need to do some data analysis first. About, how much traffic we get when we have "Serverless" in the title.

@DhairyaMajmudar
Copy link

hey @DhairyaMajmudar

We need to do some data analysis first. About, how much traffic we get when we have "Serverless" in the title.

Correct point, I think Google analytics can help in this. Looking forward to help in data analysis

@github-actions 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 Aug 26, 2024
@skonto
Copy link
Contributor

skonto commented Sep 16, 2024

/remove-lifecycle stale

@knative-prow knative-prow bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 16, 2024
@skonto
Copy link
Contributor

skonto commented Sep 16, 2024

@aliok should we close or this is wip?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JonConstantine01 JonConstantine01

Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
Steering Committee Backlog
Status: 📋 Backlog
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fixing #5634: Update home.html erharjotsingh/docs
Heading Updated vinfinity7/docs
9 participants
@aliok @skonto @ReToCode @nainaz @JonConstantine01 @shaaoni @vinfinity7 @DhairyaMajmudar @erharjotsingh