Can I revision my templates, styles and components?
Yes. You should revision your Site Studio assets like other configuration using a service like Git.
Yes. You should revision your Site Studio assets like other configuration using a service like Git.
No. Helpers are coupled with the page once placed. Changes to the Helper layout will not affect existing instances.
No, there is no way to roll back a Site Studio package import.
With Site Studio Sync you can export Site Studio configuration in full or in part as a package that can be imported into a different website.
The style preview may not be updated because the refresh icon hasn't been toggled to the active state.
You can style tables or forms through the use of base or custom styles.
Yes, you can render react components.
A Site Studio Package file is a .yml file that contains Site Studio Configuration. The package file allows you to import and export between environments.
HTML is escaped when using Drupal tokens in Site studio as a security measure, this follows Drupal core.
Yes, the generated templates can be saved to the database.
Yes, this is possible by creating a custom element.
Cohesion layout revisions are created at the same time as node revisions, but not always deleted at the same time.
Use the "Node Revision Delete" contributed module to manage your node and associated cohesion_layout revisions.
Use the tools included in the "Entity Reference Revisions" contributed module.
If you want to add custom code to your website you can use Field formatters, Blocks and Custom Site Studio elements.
No site specific data is stored on the API.
Drupal content field data is NOT transmitted to the API. Only the underlying JSON schema and any information hard coded into templates and styles is transmitted.
Copyright © 2020 Acquia, Inc. All Rights Reserved. Drupal is a registered trademark of Dries Buytaert.