Rich Text Field - Add quick-win buttons
Add as many buttons (e.g. lists, blockquote) as can be added quickly, leaving more challenging ones for a future task.
Matt Jones 20 days ago
Studio
Rich Text Field - Add quick-win buttons
Add as many buttons (e.g. lists, blockquote) as can be added quickly, leaving more challenging ones for a future task.
Matt Jones 20 days ago
Studio
Allow option in include webapp/modules tag to skip total_entries
For better performance, when it’s not required to know the total_entries for features. E.g. in a form with a datasource field, it’s not required to count the number of options and would be faster to skip that calculation.
Matt Jones About 9 hours ago
Improvement
Allow option in include webapp/modules tag to skip total_entries
For better performance, when it’s not required to know the total_entries for features. E.g. in a form with a datasource field, it’s not required to count the number of options and would be faster to skip that calculation.
Matt Jones About 9 hours ago
Improvement
Rich Text UX - Need to toggle HTML mode off before preview updates
Currently if adding HTML in the rich text field, you need to toggle HTML mode off again before you can see your changes in preview and before the save button will properly register the change. Is it possible to make it so that preview updates happen more regularly that that, maybe when you press enter key? It might be necessary to check all HTML tags have been properly closed before the preview is updated.
Matt Jones 9 days ago
Studio
Rich Text UX - Need to toggle HTML mode off before preview updates
Currently if adding HTML in the rich text field, you need to toggle HTML mode off again before you can see your changes in preview and before the save button will properly register the change. Is it possible to make it so that preview updates happen more regularly that that, maybe when you press enter key? It might be necessary to check all HTML tags have been properly closed before the preview is updated.
Matt Jones 9 days ago
Studio
Studio List datasource item limit
Ability to control the number of items that are shown if you pick a datasource on a Studio List. You can use categories or select specific items but cannot control how many items to show (it’ll show all).
Luke Wakefield 10 days ago
Studio
Studio List datasource item limit
Ability to control the number of items that are shown if you pick a datasource on a Studio List. You can use categories or select specific items but cannot control how many items to show (it’ll show all).
Luke Wakefield 10 days ago
Studio
Auto-Sitemap, support for Subscription Products
The auto Sitemap currently supports eCommerce product detail pages, but not yet eCommerce subscription product detail pages.
Matt Jones 21 days ago
Improvement
Auto-Sitemap, support for Subscription Products
The auto Sitemap currently supports eCommerce product detail pages, but not yet eCommerce subscription product detail pages.
Matt Jones 21 days ago
Improvement
Auto-Sitemap - add layout option to include custom content which is not yet supported by the auto-sitemap itself
While you can edit the page that the custom sitemap is included on, since the sitemap generates the XML boilerplate, any custom content is difficult to hoist inside of that- and ends up outside the root of the XML document. We should add an option for inserting custom links into the end of the sitemap after the auto-generated content.
Matt Jones 21 days ago
Improvement
Auto-Sitemap - add layout option to include custom content which is not yet supported by the auto-sitemap itself
While you can edit the page that the custom sitemap is included on, since the sitemap generates the XML boilerplate, any custom content is difficult to hoist inside of that- and ends up outside the root of the XML document. We should add an option for inserting custom links into the end of the sitemap after the auto-generated content.
Matt Jones 21 days ago
Improvement
Planned
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?
Matt Jones About 2 months ago
Bug
Planned
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?
Matt Jones About 2 months ago
Bug
Studio - Image image fields at a specific folder in File Manager
When in studio layouts we have a field for images. It would be very helpful to be able to create a setting for all image picker fields that lets us define what folder is opened in File Manager when it launches. This would allow us to improve image management when content is being edited by clients and even our team. It would be best to be able to define this for each image picker field, because in some cases we might be picking a BG image, in others we might be choosing a profile image and those might be housed in separate folders. A simple way to implement this might be to give us a setting tied to the image field that’s just a text field where we have to define the path, something like “/assets/images/backgrounds”. This would get the job done and potentially not cause a lot of additional UI impact within Studio.
Devon Reehl 27 days ago
Studio
Studio - Image image fields at a specific folder in File Manager
When in studio layouts we have a field for images. It would be very helpful to be able to create a setting for all image picker fields that lets us define what folder is opened in File Manager when it launches. This would allow us to improve image management when content is being edited by clients and even our team. It would be best to be able to define this for each image picker field, because in some cases we might be picking a BG image, in others we might be choosing a profile image and those might be housed in separate folders. A simple way to implement this might be to give us a setting tied to the image field that’s just a text field where we have to define the path, something like “/assets/images/backgrounds”. This would get the job done and potentially not cause a lot of additional UI impact within Studio.
Devon Reehl 27 days ago
Studio
Studio - Add image_array and custom array- type fields to sections
Somewhere in-between a field and a list, the main use of this is for mapping datasource fields of type image array. It should allow the user to add as many images as they like in the normal field UI, and store them as an array of image paths. Like single image fields, it should allow the image-picker component. We should also support custom_arrays, mainly to help people map an array of image alt tags to complement their image array. In the normal UI, this should allow free-text of strings to be added.
Matt Jones 27 days ago
Studio
Studio - Add image_array and custom array- type fields to sections
Somewhere in-between a field and a list, the main use of this is for mapping datasource fields of type image array. It should allow the user to add as many images as they like in the normal field UI, and store them as an array of image paths. Like single image fields, it should allow the image-picker component. We should also support custom_arrays, mainly to help people map an array of image alt tags to complement their image array. In the normal UI, this should allow free-text of strings to be added.
Matt Jones 27 days ago
Studio
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 29 days ago
Feature
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 29 days 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 29 days 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 29 days ago
Feature
In Progress
Web App Content Bug (Specific Site)
Here’s what I’m seeing - different UI and different behavior on two sites running the same version of Studio: https://www.loom.com/share/2c444596b448418696d87d49de2f5086
Devon Reehl About 1 month ago
Studio
In Progress
Web App Content Bug (Specific Site)
Here’s what I’m seeing - different UI and different behavior on two sites running the same version of Studio: https://www.loom.com/share/2c444596b448418696d87d49de2f5086
Devon Reehl About 1 month ago
Studio
User Roles - Allow assigning an array of user-roles to Studio sections
Section library - if a user-role is assigned to a section, it shouldn’t appear in section library unless you have that user role. But there should be a user-role setting that overrides that and allows the user to see all sections.
Matt Jones About 1 month ago
Studio
User Roles - Allow assigning an array of user-roles to Studio sections
Section library - if a user-role is assigned to a section, it shouldn’t appear in section library unless you have that user role. But there should be a user-role setting that overrides that and allows the user to see all sections.
Matt Jones About 1 month ago
Studio
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 About 1 month 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 About 1 month ago
Feature