Skip to content

docs: Add interactive checkpoints to top 11-20 highest-traffic install guides #62682

@rodgtr1

Description

@rodgtr1

Applies To

Improve user success and feedback data collection on high-impact install and configuration guides by introducing interactive checkpoints that:

  • Prompt users to confirm completion of key steps and signal whether they’re progressing successfully or encountering issues
  • Collect feedback via events and optional comments
  • Provide targeted troubleshooting tips when users get stuck

Details

This issue tracks the work to add interactive checkpoints to 10 of our highest-traffic installation guides, based on page views and access data from Google Analytics. Our top 10 have been addressed in another Issue. This particular enhancement will address the next 10 in succession (11-20).

Traffic data reference:
https://lookerstudio.google.com/u/0/reporting/f39d0536-d410-4752-ac0e-484e2917b6be/page/p_fpk3sdk0ed
(Using Looker Studio as not everyone has access to Google Analytics directly)

Each guide will receive its own pull request to keep changes scoped and easy to review.

  • /enroll-resources/desktop-access/active-directory/
  • /enroll-resources/application-access/protect-apps/connecting-apps/
  • /enroll-resources/server-access/getting-started/
  • /zero-trust-access/deploy-a-cluster/helm-deployments/kubernetes-cluster/
  • /connect-your-client/third-party/vscode/
  • /installation/helm/
  • /zero-trust-access/rbac-get-started/role-demo/
  • /machine-workload-identity/getting-started/
  • /machine-workload-identity/deployment/gitlab/
  • /enroll-resources/application-access/cloud-apis/aws-console/

Google sheet for tracking ownership of guide changes

How will we know this is resolved?

Checkpoints will be available in these guides.

Related Issues

#62258

Metadata

Metadata

Assignees

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions