Skip to content

Establish feedback loops in our documentation on a per page basis #3950

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

Closed
Tracked by #5018
ghuntley opened this issue Sep 8, 2022 · 1 comment
Closed
Tracked by #5018

Establish feedback loops in our documentation on a per page basis #3950

ghuntley opened this issue Sep 8, 2022 · 1 comment
Assignees
Labels
docs Area: coder.com/docs

Comments

@ghuntley
Copy link
Contributor

ghuntley commented Sep 8, 2022

observations

Asking folks to make and edit changes to documentation assumes people know what edit should be done.

CleanShot 2022-09-08 at 13 25 12@2x

suggestion

Implement documentation feedback pattern similar to https://docs.microsoft.com/en-us/dotnet/csharp/fundamentals/functional/pattern-matching

CleanShot 2022-09-08 at 13 26 07@2x

Related #3972

@ghuntley ghuntley added the docs Area: coder.com/docs label Sep 8, 2022
@github-actions
Copy link

github-actions bot commented Nov 9, 2022

This issue is becoming stale. In order to keep the tracker readable and actionable, I'm going close to this issue in 7 days if there isn't more activity.

@github-actions github-actions bot added the stale This issue is like stale bread. label Nov 9, 2022
@bpmct bpmct self-assigned this Nov 10, 2022
@bpmct bpmct mentioned this issue Nov 10, 2022
6 tasks
@ghuntley ghuntley removed the stale This issue is like stale bread. label Nov 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Area: coder.com/docs
Projects
None yet
Development

No branches or pull requests

2 participants