Built with Ship StudioSuggest the features you want, vote on the ones that matter, and watch them move from idea to shipped. We build what the studios ask for.
What if I could @ from a component library to create something new and then of course visually edit and manage them all.
The branches seem to update pretty slowly, especially with the agent spins up the branch. It would also be nice if the branch tab recognized branches made outside of ShipStudio, for a more accurate reflection of the codebase.
I want the ability to edit text inline when it is dynamic (eg. multilingual sites, components, etc)
Page slots that can be defined by AI and to be filled by AI generated components from a per project bases AI component library,
If I build an Astro Ship Studio project with components, could these be added automatically in a component library for fast sue on pages. And be placed in a page slot / component slot
Instead of having to right click and choose < Back, simply add them as buttons in the UI for the visual preview.
Make the structure of the page fully editable via the Element Tree left-hand panel, by allowing for click-and-drag arrangement of elements within it, as well as nesting-unnesting elements, adding new ones (with a list/dropdown/panel of available elements), as well as deletion/duplication/renaming.
I've found myself explaining to Claude that some buttons are off the design system we're using for other pages. If there was a way to visually set these rules, that'd be great. And if the user ever wants to change a global rule, they can go to the page and tweak. Or ask Claude to tweak and know the change is being propagated globally. Similar to a Relume or ClientFirst starter page.
Add local providers like LM Studio or Ollama. I'd love to use my local models like Qwen3.6 in Ship Studio :)
Since I have two different Claude Pro accounts, i'd want to switch between two accounts more seamlessly while working, instead of having to sign out & in again
Like Webflow and even Claude Design have - allow a view of the currently selected element and its parents, siblings etc. Would also be good to navigate between them with the keyboard arrows.
A more visual and direct way to see created pages. The dropdown is useful and gets the job done but navigating between multiple pages via dropdown while you're iterating feels clunky when you can't see them all at the same time and select. A sidebar that shows/hides like Webflow's could work: https://cleanshot.com/share/NvKRyTDd.
Instead of going to copy and then having to CMD + V in the chat UI, this would allow users to annotate and as soon as they are done with 1 page send all annotations, and on to the next page while the edits are made.
I'd like for the clients to be to pin agentation comments in the client editor and then I can go in the editor and see them.
A grid overlay in the preview window would be amazing. Could compound grids come in? With a system for setting them up, like the example url. As graphic (Art-director) designer a compound grid could give more elegant designs as you can really play with compositions.. Makes some wonderful designs, used also in print. (what all started it) In digital that got lost in translation. For years we worked on the 960 grid (bootstrap) Would be amazing as option. It does get use in Digital for high-end productions. For example: https://stuffandnonsense.co.uk/layoutlove/index.html A great book about this an Art Direction for the web: https://www.smashingmagazine.com/ebooks/art-direction-for-the-web-ebook/
It's get's further than it used to and allows us to select a workspace within the mono repo but it's still getting stuck on the import steps
Right now the Client Editor importing Projects from Github can only access the "Personal" repos and not all the repos that have been granted access in Github in other org's that you're apart of. (and right now there's also a duplicate "Personal" option that just shows and error instead of the list or repos.)
Add a light mode option, and ideally a customizable theme manager, so users can adjust the interface to suit their environment and personal preference. Problem The current dark-only interface works well indoors, but it becomes hard to read in bright conditions — for example, when working outside during the daytime. Dark backgrounds tend to reflect glare and wash out on screens in direct sunlight, which makes the app difficult to use in those situations. Not everyone prefers dark mode, and some users find light interfaces easier on the eyes in well-lit settings. Proposed Solution At minimum, add a built-in light mode that users can toggle in settings. A few ways to make this even better: Manual toggle between light and dark mode. Automatic switching based on time of day or the operating system's theme setting, so the app matches the user's environment without manual changes. A theme manager for users who want more control — letting them adjust accent colors, contrast, or choose from a set of preset themes (and possibly create and save their own). Benefits Improves readability and usability outdoors and in bright environments. Accommodates personal preference and accessibility needs. Brings the app in line with users' expectations, since light/dark options are now a standard feature in most modern apps.
Being able to search through previous chats to find information or workflows or just history of things you want to reference again.
Built with Ship Studio