Can I roll back a Site Studio package import?
No, there is no way to roll back a Site Studio package import.
No, there is no way to roll back a Site Studio package import.
You can create more than one template to provide layout and style alternatives with the use of the template selector.
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.
Yes, you can render react components.
You can integrate social metadata as you would on a traditional Drupal setup. Information within the layout canvas can not be used as social metadata.
Yes. You can create AMP pages that use the Layout canvas for content but there are a number of considerations.
Yes. You can create AMP pages that use the Layout canvas for content but there are a number of considerations.
You can only add combinators to child selectors. Add a child selector and combinator will appear in the Style tree.
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.
Running the composer update command will update any composer packages that have newer versions available.
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.
You don't. You apply a Descendant selector. These use a (Space).
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.