Help us improve
Components appear in wrong place on load
If set to only appear on fields or lists sometimes it appears in the one it shouldn’t but refresh solves it.
Components selecting fields tries to move the component (reorder)
The drag and drop reorder seems to take over editing the component item
Settings Mapping
Ability to map settings as well as fields/lists - Useful for working with Dynamic Sections
Agency Library Plugins to Extend Studio libraries like StudioKit
Currently agencies have the option to use our StudioKit library on Studio or create their own library. What many agencies could benefit from though is a solution designed so they can use an existing library like StudioKit and benefit from upgrades, but themselves add extra sections to extend it, still following the same framework guidelines so they are compatible.
Rich Text Editor Improvements
Update the Rich Text Editor to include better AI tools and Authoring tools.
Use Skill MD Files
AI reads each skill's short description and decides for itself whether it's actually relevant, instead of blindly applying every skill to every request. Skills are automatically attached to a new AI chat, no manual setup needed. Users can browse existing skills with a preview before choosing one. Users can upload your own skill file, either just for the current conversation or saved for everyone to use. Users can manage skills in Studio Libraries where you can create/edit/delete skills. [NEW] Uploaded skills are now kept separate per library/theme
Section Builder AI improvements 1/4 - Edit section
It only edits rather than rebuilds the whole section (this would make a huge difference as currently it can make things worse)
Studio - Global fields - Completely customisable field metadata
Follow up to dependency @Image title and alt tags Phase 2: update global fields to allow adding additional metadata fields on top of the built-in ones like alt from previous task. Allow the agency to add a metadata field (of any reasonable type) to a specific image (or any other type) global field e.g. adding a caption field metadata field. When defining field metadata fields, you can add helper text to describe how they should be used. AI would be able to look at the global field definition to understand any metadata fields which were added. Metadata fields appear for client when adding data below the main field, and show helper text if defined.
Copy library to store original library name in addition to new name
When copying a library from marketplace, create a key in the library config which stores the original_marketplace_name or original_marketplace_ID of the library. This can be used to help AI identify if it is a StudioKit project or not.
Ensure it can get context from the whole library (Section Builder AI Improvements)
Added semantic search (with the use of embeddings in pOS) for more relevant AI-generated section suggestions (not visible to user). AI assistance now better incorporates theme, library, tags, collections, and global settings.
Different lists in the same section returning identical items
I just wanted to report a bug I noticed when mapping different datasources to different lists... In my video, I have two separate lists: Products and Areas, and I’m trying to map each one to its own webapp datasource but when I map both of them, it looks like they start sharing the same data. For example, once the Areas webapp is mapped, the Products list starts displaying the Areas data instead... the Products list works fine when only the Products datasource is mapped, but the issue happens when both datasources are connected Just wanted to flag this in case it’s something that needs looking into... thanks!
Studio Redactor URL Selector
Add URL lookup like we have for fields inside the redactor plugin for Webapps/Modules
Absolute URLs for images in Rich Text fields
Need to store as relative URLs so that staging to production doesn’t store the staging URL
Ability to reference an existing section from a list (Section Builder AI)
Posts (10) - Featurebase Added a section picker for finding and referencing existing sections in AI conversations. AI responses can now include clarifying questions and reference plans to improve edit accuracy. Referenced sections are included as context when requesting changes.