Demo 260803

This work makes copy and paste behavior similar across both main and edit canvases:

• Copy everywhere with ⌘C / ⌘⇧C plus buttons on cards, drawers, editor header, and Version History row.
• Copy supports workflow, comments, nodes, nodes with children.
• Workflow copy updated to be the version you are viewing. No version prompts; each copy takes the version on screen and names it in the toast.
• Pasting ⌘V on main canvas give a cursor prompt to choose location, putting user in control of its landing zone on main canvas. This mirrors paste on edit where you must choose the landing point in the workflow.
• Canvas fixes found along the way. Zoom-to-fit now covers negative coordinates; stale position rows from archived flows no longer push pastes off the corner; selecting a comment no longer recolors it.
• Revised comment drag UX to match workflow. Select first then drag.
• Documented copy and paste behavior in SPEC-copy-paste.md to help when using LLM to review the prototype.

Before this update, there was no way to tell a sub-menu item from a insert node button in the pie menu. To fix this, we removed the background color for menu items.

We’ve also combined the back and close button into one consistent action and location.

Draft for new dashboard page for app.voxie.com.

Goal is to give corporate customers a dashboard into their franchise.

This demo pulls data from omni dashboards and uses Voxie interface components to render that data. This gives full control over how data is shown, allowing us to fix shortcomings of Omni interface, match Voxie brand, and extend charts with more features.

This allows us to have Voxie side interface (like message hub, campaign analytics), mixed in with omni backed data.

This method allow data team to retain control of queries and data, but returns control of the interface to the UI and Engineering teams.

One new ability is for the end user to have the ability to reorder, resize, and toggle visibility of a given chart.

This will be more sustainable in the long run allowing each team to own and control the work they are best suited to do in the workflows that provide them the most control.

We’ve started a process to improve AI adherence to our design system so prompting designs produce higher quality output. As a part of that work, we realized our design system relied on a lot of rules that only existed in the design team’s heads. To fix this, we’ve been going through all the product work we’ve done over the years, finding patterns and solidifying them into our components and documentation. So far, we’ve captured commonly used surfaces like cards, glass, and backgrounds and then codified how buttons and color palettes fit into them. More to come.