Skip to content

Add a Help & Support Section to Teleport 4.3 #3531

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
benarent opened this issue Apr 6, 2020 · 0 comments · Fixed by gravitational/webapps#78
Closed

Add a Help & Support Section to Teleport 4.3 #3531

benarent opened this issue Apr 6, 2020 · 0 comments · Fixed by gravitational/webapps#78
Assignees

Comments

@benarent
Copy link
Contributor

benarent commented Apr 6, 2020

Feature Request

Teleport Hornet, currently lacks the Help / ? in the sidebar, we should provide more in-depth support for customers.

cluster_-_help___support

Support

Resources

Troubleshooting

  • Monitoring Teleport
  • Collecting Debug Data
  • Troubleshooting FAQ

Updates

Product Changelog - https://github.com/gravitational/teleport/blob/master/CHANGELOG.md
Gravitational Blog - https://gravitational.com/blog/

Adding Version Number.

To better serve our customers, we should send which teleport version is linking to docs, and load the relevant version for them.

?utm_source=teleport&utm_medium=oss_4.2.8

Motivation

Describe why we should work on this feature request.

Who's it for?

OSS User, Pro, Enterprise. Note different content for different versions.

@benarent benarent added the hornet label Apr 6, 2020
@benarent benarent added this to the 5.0 "Oceanside" milestone Apr 6, 2020
@benarent benarent changed the title Add a Help & Support Section to Teleport 5.0 Add a Help & Support Section to Teleport 4.3 Apr 15, 2020
@kimlisa kimlisa self-assigned this Apr 28, 2020
@kimlisa kimlisa closed this as completed Apr 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants