Local MCP Feedback

Let us know how we can improve the Local MCP

Cloud MCP Feedback

Suggestions to improve the Cloud MCP including bugs.

Add a user role permission to control access to standard site API key

Categories - Admin UI support for weighting

Categories have a weighting field and it appears in CSV export/import, but it’s not currently possible to edit in the Admin UI. Let’s add support for it.

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

Users list view & CRUD forms for Front-End Admin use-cases

Siteglide Github Backup - Site copies initial commit

Site copies on Siteglide get a tracked git history of changes like any site, but they do not seem to get an “initial commit” of the state of the site when the copy finishes. This would potentially make the backup more useful.

Site Search - One set of fields for pages and webapps

Currently site search results need different fields to output say meta_desc for webapps then they do for pages. Let’s give an alternative mapping which means same syntax for both types of results for newer sites, also preserving the backwards compatible existing fields.

Datasource to Form ID

New Siteglide field type datasource single to include option to datasource to a form. Should give client dynamic dropdown with name of form as label and store the form ID as the value.

WebApp - Include the Add New Option after saving a WebApp Item

You can Add New if you do Add New, save once then Add New again but if you open a WebApp Item to edit then Save, you have to come out of the item to add new.

WYSIWYG Editor

When pressing backspace or cut and pasting, content is either deleted or ends up in the wrong place

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.

AI Assistant Website Module

I wanted to ask whether Siteglide has considered, or could potentially offer, an AI conversational assistant that could be embedded directly into client websites. The idea would be to allow website visitors to “talk to the website” rather than simply navigate through menus and pages. For example, a visitor could ask questions such as: “Which product would be best for my needs?” “Where can I find the technical documentation for this product?” “What are the requirements to apply?” “Can you explain the difference between these two services?” “I need to dig a 20-metre trench — which equipment should I hire?” The AI assistant would use the website’s own content as its knowledge base, including: website pages; blog posts; FAQs; products and catalogues; WebApps; PDF documents; brochures; technical datasheets; other approved documentation. Ideally, it would work as a RAG-based AI assistant, meaning that answers would be grounded in the client’s own content rather than relying on generic AI knowledge. From an agency perspective, some particularly useful features would be: easy deployment across multiple Siteglide websites; automatic indexing and updating when website content changes; the ability to include or exclude specific content from the knowledge base; links or references back to the relevant website pages or documents; custom branding for each client; conversation analytics; visibility into the questions visitors are asking; identification of questions the assistant could not answer; lead capture and enquiry generation; potentially, the ability to trigger actions such as forms, bookings, CRM entries or other workflows. I see this as something beyond a traditional chatbot. It could become a genuine AI interface for navigating and interacting with a Siteglide website. For agencies like ours, it could also create significant value because the questions asked by visitors would provide valuable insights into missing content, customer needs, SEO/GEO opportunities and conversion improvements.

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.

eCommerce - default payment gateway toggle

Previously you would only have one payment gateway “enabled” at a time, but now you can have more than one payment gateway enabled at once, so long as you add an ID parameter within the form layout to the eCommerce field include. But it can be tricky to migrate a setup which has only one payment gateway enabled to 2 in order to set up a test mode for developers while the site is live. When two payment gateways are enabled at once, before ID parameter is passed in, it’s not easy to tell which will be used be default. Adding a true default option to payment gateways could solve this, to use the production one by default in most cases, but allow devs to test with sandbox when needed.

Create and Delete Sites programatically

Ability to create and delete sites programatically. Example use case as part of a CI/CD flow for automated testing.

File Manager Improvements

The File manager could use an update to be in line with the modern experience of similar tools customers are touching every day. This is important, because whether using Core Siteglide or Studio, you’re asking the customer to interact with File Manager. Suggested improvements: 1) Progress indicator - you can’t currently see anything other than the spinner, and it would be good to be able to see how far along an upload is. 2) Clear labeling of limits - if I can’t upload a certain size, let me know 3) Studio picker - let me define the folder that I should see once I click the picker, vs making the customer navigate to it 4) Navigation - Once I upload a file, it’s in there, but I have to search for it to find it and select it. That’s cumbersome. NICE TO HAVES Ability to move folders in or out of folders Grid video

Redactor Page Selector for Links

Add URL lookup like we have for fields inside the redactor plugin for Webapps/Modules

Siteglide CLI - Syncing a file with empty metadata object, causes sync to silently fail

--- metadata: --- Syncing a file like this appears to work, but checking GraphQL the sync is not successful and the update has not been applied. E.g. if previously there was metadata and you intended to delete it, the change would not be applied. We should check yml validation and check a) that this is allowed b) that a validation error throws a sync error properly.

When mapping fields - add better handling for disabled or unpublished items.

Disabled items appear in the list of options for mapping database fields to Section fields, but then don’t work correctly. We should either allow this properly for if you are building a page in advance of a release (with a secret URL) or properly show these items as disabled in the dropdown and don’t allow them to be selected. (Most likely the 2nd one is most consistent - when draft mode is built, the first option could be allowed for draft mode.)

Better Error Handling for failed Module Installs / Updates

Currently Module installs often terminate without properly informing the user with an error message. Could we add better error handling, or even better, automatic retries?

Allow use of Tailwind Variables without Tailwind Colours

Tailwind Themes can only use "variables" tab if they also use at least one colour. Remove that requirement using an “else”.

Webapps - Default Edit Form Layout

Webapps have been updated so that they can be setup to allow any user to edit. It would be good to autocreate the default edit form in layouts. Maybe change the default form to insert.liquid (or input.liquid) and the new layout to edit.liquid or keep the default and have separate folders. This new form should appear in the toolbox as "WebApp edit form"

Menu Builder v2

We would like to create a new version of Menu Builder, which overhauls both the existing UI as well as behind the scenes structure… no small update! We are excited to get your input and feedback to help shape its future. Below we will outline our current plan for the future based on any older feature requests relating to Menu Builder along with any feedback we have collected to date. If you have any questions, ideas or input on what you would like to see in Menu Builder next, please let us know by commenting on this feature request. Discussion is also welcome! — Structure Remove the use of database items on Menu - json instead for structure Simplify the menu layout structure Update the default layout to cater to drop downs Add either a optional text field to add a logo, or ideally custom fields (at a minimum: Link Title (text), Link Icon (file), Onclick (text)) Add the ability to enable/disable menu items UI / UX Keep existing drag & drop functionality Data from across the site needs to be accessible, including search and filter functionality Ability to add a blank empty new menu item Ability to add items directly into a specific location in the menu, rather than adding a new item at the top level and then needing to move it to the desired location. Ability to split menu into columns or groups and access those from the layout Data that needs to be accessible to the user when adding menu items: Pages WebApp items Module items Category pages

Detect installed modules on front-end

Currently an admin_tables query can be used to detect most modules, but not all e.g. Secure Zones. The method doesn't work because Secure Zones' yml config is in the private folder for obvious reasons. Please could you provide a simple method e.g. context.exports for checking the presence of an installed module so we can use this information to decide whether to show a feature?

List views - Quick enable/disable

Would it be possible to add a quick enable/disable feature so you do not need to open the webapp item or page you are attempting to change the status of. Ideally could we make the cross/tick icon shown in the screenshot attached a button to toggle this?

eCommerce - Advanced Shipping Options (Custom Fields)

The ability to add custom fields to Shipping Options.

Image Fields - pre-fill image alt fields on type

By default it would be useful to prefill the image alt fields with the image file name. 9 times out of ten it will be the same data and will avoid a lot of data double entry.

Categories - Enable/Disable

At the moment if you want to turn one off you have to delete it.

Datasource for Users & Related User functionality

It would be great to be able to multi-datasource to the users table & to be able to view and edit the related user (Item Owner) in the events module

Studio Detail Pages - Category detail page support

Copy library to store original library name in addition to new name (Studio Libraries)

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.

Studio Support for Field Tooltips / Helpers

Just as Siteglide Admin has the option to add either/or a helper or tooltip to each field, allow the same in Studio. This allows theme-creators to explain the purpose of fields, or explain what kind of values are supported.

Show a "new" label to show on newly added sections in a theme (Section Library)

Store a date section was created, and show the new label for (30 days) after that date in the marketplace section library.

Studio in WebApps

We all love webApps because we can define required fields we want the client to use, where I see studio being super powerful is having the ability to have a ‘Studio field’ in a webapp entry. Imagine you have a webApp for a Blog, the client fills in the required fields (title, subtitle, main image, categories etc etc) but in the content area, the ability to compose the structure of the entry with Studio features would be awesome. I.e you could have structures for a video with a caption, a gallery of images pulling dynamically from another source, a list of team members (pulled in dynamically or manually), a pull quote, testimonial (dynamically from another webapp), a image to the left and text to the right, etc etc. This would give the client so much flexibility in how they can build out webApp items rather than trying to deal with a wysiwyg editor.

eCommerce - Product Attribute combinations

For Attribute inventory to be effective we would like the system to auto-generate combinations based on Attributes against a Product. Then we can store inventory values against each combination.

Improve Turnstile Error Messaging for Missing or Invalid Keys

When Turnstile keys are missing or incorrectly configured, the form currently displays an unclear code error/console log upon submission. Update the error handling to display a clear message explaining that the Turnstile keys are missing or invalid.

Switch order of menu for tailwind vars and custom css

I think it is more logical to put variables before custom CSS in the tab menu when present. Variables would normally be defined first. Also please add tooltips (when Tailwind only) for explaining some best practice for custom CSS and variants. E.g. for custom CSS link to the cascade layers docs.

Support seo_searchable: false on HTML version of auto sitemap

Currently supported on XML not HTML. Expected behaviour skips pages with seo_searchable set to false.

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

Add image/screenshot option (Section Builder AI Improvements)

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

Boolean Global Fields throw error r.e. missing options