If I change a Helper layout, will it change where it's used?
No. Helpers are coupled with the page once placed. Changes to the Helper layout will not affect existing instances.
Acquia Cohesion renames to Site Studio from version 6.2. Tell me more.
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.
No, you cannot use SCSS variables in your codebase inside the Site Studio interface.
Yes, you can use Drupal fields in certain parts of Site Studio.
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.
It depends on the use case. For fields and their field formatters use a 'Field' element, for data without field formatters, use a token.
To use an SCSS variable, enter your chosen variable into the appropriate CSS property.
Yes, you can render react components.
No. Site Studio allows the site builder to select, either use of IMCE or Entity browser for browsing and selecting images.
Yes, the component link field supports both internal and external URLs.
No, the entity browser does not work for component defaults as the entities are content, not config.
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.
You can use Elements to create content but we don't recommend doing so for multiple reasons.
Yes, this is possible by creating a custom element.
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.