Docs: Improve the GitLab Duo onboarding experience - Getting Started (Setup, requirements, first use cases)
### Problem to solve Setting up GitLab Duo needs a unified user experience for customers. This includes 1. Pre-requisites (personal access tokens, etc.) 2. IDE extensions setup for Chat, Code Suggestions 3. Feature enablement/control/licenses 4. General Troubleshooting Currently, the setup is scattered across different documentation pages, and extension plugin marketplace docs. https://docs.gitlab.com/ee/user/gitlab_duo/ misses a Getting Started section. ### Further details As an example, I wanted to setup GitLab Duo Chat in IntelliJ. 1. Navigate to https://docs.gitlab.com/ee/user/gitlab_duo_chat/index.html 2. Open https://plugins.jetbrains.com/plugin/22325-gitlab-duo 3. Install the plugin, open IntelliJ 4. Open GitLab profile, create PAT. Check the plugin docs which scopes are required. 5. Continue the setup steps 6. Back to the browser tab with Duo Chat. Where is the chat icon. 7. How to troubleshoot the Duo plugin? 1. Plugin docs links to https://docs.gitlab.com/ee/editor_extensions/jetbrains_ide/ 2. No troubleshooting docs there 3. Starts generic google search for IntelliJ logs It is also important to always have the latest plugin versions installed. This hint is missing in the docs. ### Proposal Create a unified documentation tutorial which instructs users to setup Duo with different IDE setups. Add maintained recordings that highlight the steps in a visual way. Intentionally copy certain steps from the general IDE extensions docs, and tailor them to the GitLab Duo use case. This creates a more complete user/developer experience. Add troubleshooting documentation, and known tips into that section. Call it `GitLab Duo Onboarding` or `GitLab Duo Getting Started` to highlight it as the first entry point for users. Clean up the existing structure - the Code Suggestions troubleshooting section has some debugging tips for VS Code, but none for JetBrains. ### Who can address the issue @dnsmichi in review with product/technical writing teams. ### Other links/references - 2024-06-11 walkthrough with screenshots for VS Code / IntelliJ for a customer workshop. https://gitlab.com/gitlab-da/use-cases/ai/test-ai/ide-setup-duo-2024-06-walkthrough - Duo Chat on the right pane https://www.youtube.com/watch?v=foZpUvWPRJQ - Customer workshop: https://gitlab.com/gitlab-da/use-cases/ai/ai-workshops/gitlab-duo-use-case-python-2024-08-21 with exercises to incorporate. - Getting started MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/173482 #### Additional features Health check for self managed in 17.3 -- added to the troubleshooting docs https://docs.gitlab.com/ee/user/gitlab_duo/turn_on_off.html#troubleshooting > Hi team; wanted to share that beginning in 17.3, GitLab Duo Health Check will be available for SM instances. This will help customers verify and troubleshoot their AI setup and connectivity, reducing frustration and support headaches when trying to diagnose why something may not be working as expected.https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/135727/diffs /cc @sselhorn @tmccaslin
issue