Do component content entities have view modes?
No. Component content entities do not have view modes.
No. Component content entities do not have view modes.
No, there is no way to roll back a Site Studio package import.
No, you cannot layout forms with Site Studio.
The 'Range' in the menu list item element sets which list items at the current level the settings should apply to.
Yes, you can build mega menus using Site Studio. Building mega menus requires advanced knowledge of jQuery in Site Studio and CSS.
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.
You can style tables or forms through the use of base or custom styles.
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.
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.
Yes, this is possible by creating a custom element.
Opacity is set using a decimal where 0 is transparent, 0.5 is 50% and 1 is solid.
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.