search

kubernetes / contributor-site

Code for kubernetes.dev
https://www.kubernetes.dev
Apache License 2.0
66 stars 148 forks source link

Why do we have "Is this page helpful?" #379

Closed jberkus closed 5 months ago

jberkus commented 1 year ago

At the bottom of most pages on the site, we have "Is this page helpful? [Yes] [No]".

As far as I can tell, absolutely nothing happens whether you click yes or no. Nobody is looking at that data, and you don't get encouraged to improve pages if you click "no".

So ... why do we even have it?

@sftim @mrbobbytables

mrbobbytables commented 1 year ago

It would track it in google analytics

sftim commented 1 year ago

The Kubernetes website has these buttons and those do influence statistics in Google Analytics. I think that's where we got the idea from. Or maybe it was part of Docsy out of the box. I am not sure.

jberkus commented 1 year ago

Does anyone look at the data? I know I don't.

mrbobbytables commented 1 year ago

Not with ant sort of regularity, but I did check on it every once in awhile. They aren't critical by any means

mrgiles commented 1 year ago

So, if @mrbobbytables and @sftim have already answered the question that originated this issue opened by @jberkus, why is it still open after 60 days? What else needs to be done so that it can be closed?

abhijeetgauravm commented 1 year ago

I think the issue should be closed now?

ashutosh887 commented 11 months ago

Let's close the issue @mrbobbytables

satyampsoni commented 11 months ago

One thing we can do is add another text for "NO", when clicked for "yes" or "no" it shows the same output.

k8s-triage-robot commented 7 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 6 months ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 5 months ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot commented 5 months ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes/contributor-site/issues/379#issuecomment-2027195028): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.