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.
No, there is no way to roll back a Site Studio package import.
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.
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.
This is because you have the page title block in the content region.
Yes, you can personalize content within Site Studio using the context module.
If you're removing styling from a base style, those styles still apply until you have saved the base style.
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.
Base styles are CSS styles for HTML elements.
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.
Copyright © 2020 Acquia, Inc. All Rights Reserved. Drupal is a registered trademark of Dries Buytaert.