### Problem to solve <!-- What problem do we solve? --> ### Intended users * [Parker (Product Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#parker-product-manager) * [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer) * [Presley (Product Designer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#presley-product-designer) ### Further details <!-- Include use cases, benefits, and/or goals (contributes to our vision?) --> --- ### Proposal #### Paste a link and modifying the link to show the design thumbnail Builds on top of Support Design Links in markdown: https://gitlab.com/gitlab-org/gitlab/issues/12905 **1) Normal link *as implemented* in https://gitlab.com/gitlab-org/gitlab/issues/12905** `https://gitlab.com/gitlab-org/gitlab/issues/12905/designs/Screenshot%202019-08-06%2020.32.02.png` becomes with markdown [#12905 (design)]() --- **2) Add on optional var** `?thumbnail=small` Options for thumbnails are: * `true` (thumbnail sized) * `small` (thumbnail sized) * `medium` (issue width) * `large` (desktop width) * `original` becomes NEED DESIGN --- **3) Add on optional var** `?v=2` locks it to that version, otherwise it shows the latest version. NEED DESIGN --- **4) If design is deleted**, show the following in its place: NEED DESIGN --- ### Permissions and Security * Consider viewing of confidential issues and their designs ### Documentation TBD ### Proposal from @jareko * Sketch cloud specs: https://sketch.cloud/s/EJnk2/v/dlzEkm/ * See designs tab for final designs ### Availability & Testing <!-- This section needs to be retained and filled in during the workflow planning breakdown phase of this feature proposal, if not earlier. What risks does this change pose to our availability? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance. * Unit test changes * Integration test changes * End-to-end test change See the test engineering planning process and reach out to your counterpart Software Engineer in Test for assistance: https://about.gitlab.com/handbook/engineering/quality/test-engineering/#test-planning --> ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> ### Links / references