Roadmap
Changelog

Help us improve

Tell us how we could make the product more useful to you.

Forms - Conditionally hide / show fields based on the state of other fields.

A client-side JS framework, configured by CMS/forms config in Admin, this would allow you to write logical rules like: If in dropdown a, option one is selected, hide field b, as it won’t be needed. Or if checkbox for “billing address is same as shipping address” is selected, hide the entire section of the form for billing address.

Matt Jones About 14 hours ago

🚀

Feature

Forms - Advanced Validation

Currently Siteglide handles both server-side and client-side validation, but only for required: true/false. We could add further validation options, possibly following the same options pOS provides for forms: https://documentation.platformos.com/developer-guide/forms/validation#example One of the useful parts of that is that some fields can be conditionally validated, so if field a is filled in, field b becomes required etc. It would be useful if validation could also have an “exceptions” box where validation is disabled per form layout, in case there is an “admin” form layout where less rules apply. Though this may be tricky to design security for. This helps handle cases where the validation is too strict for the flexibility with which forms need to be used sometimes, including across different layouts.

Matt Jones About 14 hours ago

🚀

Feature

eCommerce - Faster / Easier bulk attribute management

Currently you can import attributes for a product with CSV, but it’s a slow process. You need to know product IDs already to create the attributes. And you need to create the attributes first in order to have IDs to give to the options. Option 1: Create an attribute template e.g. for “size” for a clothing website, which can be defined in eCommerce settings and then used to create new attributes for products, either for all products, or those products already assigned to a selected category. This UI should create attributes on the products which are functional. In this example you could create a template for Men’s top sizes and a template for Women’s top sizes and then create attributes for all products in that category. Option 2: Improve CSV export / import for attributes so that it’s a one import process and attributes are automatically mapped to products (using external IDs) without needing to do it in phases to generate ids first. These ideas probably need development to make sure it’s suitable for editing attributes as well as adding them, and keeping track of which attributes were created via template and updating them when the template needs to change.

Matt Jones 5 days ago

1
🚀

Feature

eCommerce - Flexible Attributes (customisation preferences)

Some products may allow the customer to customise the product, e.g. by adding a custom message to be engraved on the product, or having the product cut to custom dimensions with no limits (as a traditional attribute might have). Could we create a flexible attribute which could be added to a product where the user defines a custom value when it is added, and this value is carried into the cart / order etc. This flexible attribute would have no traditional options, but may have validation rules or field type e.g. string with max-length 50 characters or number with min and max values between 10 - 60. This validation could possibly not need to be defined in Siteglide, but could simply be defined in Cart HTML- that’s a decision to be made which is best / easiest. Currently the custom code workaround for this is to dynamically create the attributes needed if they do not yet exist using custom API calls, but a more developer-friendly option would be useful. A further use-case for this might be when purchasing courses, to be able to select a date value for a flexible attribute, so in the same basket you could have 1 course for date a and two courses for date b, without having to define those options beforehand. Naturally, it will not be possible to store inventory for these kinds of attributes, certainly not at first. They could have a price e.g. pen costs £10 but engraved pen costs £5 extra, whatever the message.

Matt Jones 6 days ago

🚀

Feature

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.

Matt Jones 7 days ago

❗

Bug

Sections: When mapping webapp fields to a section, add the ability to map nothing to a field

By default, it currently maps the name, which is fine as a default, but if the section has logic to hide things if blank, field mapping should allow to map no value to the field so it remains blank if nothing fits. E.g. if a blogs section expects an author, but the webapp mapping to it has no author (or this date is not directly in the table), allow the user to set that mapping to empty and the section should recieve null data.

Matt Jones 8 days ago

🎨

Studio

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.)

Matt Jones 12 days ago

🎨

Studio