Do component content entities have view modes?
No. Component content entities do not have view modes.
Acquia Cohesion renames to Site Studio from version 6.2. Tell me more.
No. Component content entities do not have view modes.
Yes, you can use Drupal fields in certain parts of Site Studio.
You can create more than one template to provide layout and style alternatives with the use of the template selector.
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.
It depends on the use case. For fields and their field formatters use a 'Field' element, for data without field formatters, use a token.
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.
No, the entity browser does not work for component defaults as the entities are content, not config.
Running the composer update command will update any composer packages that have newer versions available.
Google maps may not be showing if you have not set a Google maps API key.
HTML is escaped when using Drupal tokens in Site studio as a security measure, this follows Drupal core.
You can use Elements to create content but we don't recommend doing so for multiple reasons.
Not yet. The Style builder does not have the option to add an animation name or key frames. This is planned functionality on our road map.
Copyright © 2020 Acquia, Inc. All Rights Reserved. Drupal is a registered trademark of Dries Buytaert.