shadcn.io is not affiliated with official shadcn/ui
Frame Thumbnails Setup Integration Block for Vue
An integration setup section for a design-docs tool connecting to Figma, in one framed window: paste a personal access token, tick greyscale wireframe thumbnails of the frames to link, name the link and watch its address follow, then finish with an honest result.
Installation
Overview
An integration setup section for Vue with Ark UI, written for Framenote, a fictional tool that keeps design docs in step with a Figma file, and its Figma connection. A centred header introduces three steps with the mark pair (Framenote's own tile and Figma's neutral lettermark tile) under it, and a framed window (a card in a card) holds the flow: the catalog's Steps across its top, with numbers only on a phone, then one step at a time. Step 1 takes a personal access token in a password field with a show and hide control, and lists the three read-only scopes to tick when Figma asks (file_content:read, file_comments:read and file_variables:read, the last for Enterprise plans only). Step 2 shows six greyscale wireframe thumbnails (Login, Dashboard, Settings, Checkout, Empty state, Mobile nav) as checkbox cards, two ticked to start, with a count. Step 3 names the link, and the address shown (framenote.example/f/ plus the name, as a lowercase slug) follows what is typed, beside the frames chosen. Continue waits for what each step needs and a line beside it says what is missing; the last step's Shine Button, Finish setup, ends on a result that says how many frames were linked "in this demo", with Start over. Every step sits in one grid cell with an unseen copy of them all, so the window keeps the tallest step's height. The page's rails and top rule come from the Guides spine, so it lines up with its neighbours in a stack. It's built from Guides, Frame, Steps, Password Input, Checkbox, Field, Input, Button and Shine Button, with CSS transitions for the entrance and your theme's tokens for every colour. Figma is named in text only: no Figma logo, colour or wordmark ships with the block, and the thumbnails are generic greyscale drawings. Nothing is stored or sent: the token stays in the page's state and is cleared when you start over.
FAQ
Does it check or send the token?
No. The block only requires something to be pasted, and it checks no format: the placeholder says "Paste your token" and never imitates a real token's look. The value lives in the component's state, is never shown after entry beyond the password field's own show and hide control, and is cleared on Start over. Wire the final step to your own server where the token is exchanged and stored safely, and never log it.
Are those the right Figma scopes?
They match Figma's scope names: file_content:read reads file contents such as nodes, file_comments:read reads comments on files and file_variables:read reads variables, which Figma offers on Enterprise plans only, as the step says. Figma's personal access tokens are created under Settings and the Security tab of the file browser, are shown once, and let you pick scopes. Change SCOPES to the ones your product really uses.
How do the thumbnail cards work?
Each card is a label around a checkbox, so the whole card is the target, with the checkbox named by the frame's name. The drawings are small greyscale wireframes made from CSS boxes, hidden from assistive technology; the name and the "2 of 6 selected" count carry the same information as text. Ticked cards take a foreground ring rather than the primary colour, which stays on the Shine Button. Replace a drawing component and its entry in FRAMES to show your own frames.
How is the address built?
The link name is turned into a slug (lower case, runs of other characters become one dash, dashes at the ends removed) and appended to framenote.example/f/. An empty name shows three dots in its place and blocks Finish setup, with a line that says why. The .example domain is reserved for examples, so the address never points at a real site.
Can I show Figma's logo?
The block names Figma in text and ships no Figma logo, colour or wordmark. Below the header, Framenote's own tile and Figma's neutral lettermark tile (Fg in a muted square, joined by a connector) sit in icon slots that a code comment marks: drop in the official mark only if you have the rights to use it, under the owner's brand guidelines, and never redraw it. The thumbnails are generic wireframes, not copies of Figma's interface.
How does it behave for keyboard and screen reader users?
Each step's heading takes focus when you move between steps with the buttons or the Steps header, never on load, and a polite status line announces the step ("Step 2 of 3: Choose frames"). Steps you haven't reached are disabled in the header. Continue is disabled until the step has what it needs, and a line beside it says what is missing. The Steps header moves with the arrow keys.
How does it fit on a phone and with reduced motion?
The step titles hide behind the numbers, the thumbnails sit two across and the buttons fill the width, with Back below Continue. The window takes the height of its tallest step, so nothing shifts as you move. The header fades up once on load with a CSS transition; with reduced motion it simply appears.
Related
- Hotspot Canvas Detail IntegrationWith a product drawing
- Token Collections Grid IntegrationSwitch and tick grids
- Grouped Comments List IntegrationGrouped and triaged
- Frame Wall Stats IntegrationRings and tallies
- Rollback Wizard ChangelogDeploys and rollouts
- Stepper Wizard Progression FeaturesTimelines and steps