<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=386829) </details> <!--IssueSummary end--> <!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Problem The old Web IDE provides two tabs for the Markdown file type: `Edit` and `Preview Markdown`.  The new Web IDE based on VS Code makes it harder to find the Markdown preview. Either you know how to access the command palette action, or the keyboard shortcuts, or the small button in the IDE.   Following @Rwarcards762 from https://gitlab.com/gitlab-org/gitlab/-/issues/385787#note_1223072402 >>> the Markdown Previewer built in to VSCode, just like in the Desktop version, can be opened with CTRL + SHIFT + V / CTRL + K, V as well for a quick shortcut to preview the current file. :rocket: The Preview button does exist, up at the top right, if you know where to look for it. HOWEVER -- that does not make it ANYWHERE near as ***obvious*** as the original GitLab Web IDE, and for those less code-savvy, this is a clear *feature regression* (IMO.) If there's an issue open to track making the ability to preview Markdown more obvious, I'd love to track -- if someone could link it. I think that these small QoL improvements will be a core component to letting VSCode drop in-place of the current Web IDE without requiring teaching everyone how to use VSCode. >>> cc @ericschurter @mvanremmerden ### Proposal 1. Make it more obvious how to preview Markdown file types (i.e. by guided introductions for the UI inspired by https://gitlab.com/gitlab-org/gitlab/-/issues/365666) 2. Consider opening a Markdown preview pane automatically when opening a Markdown file. - Make this configurable since not every user has the window space to have 2 panes open.  <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. --> <!-- Label reminders Use the following resources to find the appropriate labels: - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->