If I use a Drupal block in a component, can I expose the block settings in the component form?
No. You cannot expose block forms or settings in Site Studio component forms.
No. You cannot expose block forms or settings in Site Studio component forms.
Yes. You can add Drupal blocks to the layout canvas using the block element.
No. Drupal provides the list of blocks to the block element.
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.
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.
The Site Studio hidden region is a useful holder for blocks that you want to render using the Site Studio block element.
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 don't. You apply a Descendant selector. These use a (Space).
Copyright © 2020 Acquia, Inc. All Rights Reserved. Drupal is a registered trademark of Dries Buytaert.