public://as well as the user modules folder on the Drupal site (typically
composer installwithin the
grav_exportfolder to install dependencies.
drush en grav_export -yor the administration GUI.
drush grav_export_all, or its alias
drush gravea, to export all items. See other options below.
drush grav_export_users or
drush graveu will generate Grav user account files.
EXPORT/accounts folder to your
user directory (e.g. username.yaml files should be placed at
drush grav_export_roles or
drush graver will generate a Grav groups.yaml file.
Drupal user roles export as Grav groups in a
groups.yaml file at
config/groups.yaml. Some notes about the role exporting:
admin.superaccess along with
EXPORT/config folder to
drush grav_export_content_types or
drush gravect will generate Grav blueprints and html.twig files.
For every defined field type,
drush gravect will attempt to create compatible blueprint and matching html.twig file for each Drupal content type. The files will be exported to
Cardinality in many Grav fields only support one value. Only the first Drupal entry is exported.
Grav has no concept of an address field. Drupal field data is exported as an
array form type.
EXPORT/themes/drupal_export/templates folder to the active theme in Grav. The admin plugin should now provide extra options for each content type and related fields.
Note: While field content is added to Grav page headers, display of those fields is not exported from Drupal. The html.twig file will need to be modified in order to display any additional fields (besides main body content).
drush grav_export_nodes or
drush graven will generate Grav users and groups.
EXPORT/pages, based on Drupal's url alias and content type (i.e.
EXPORT/data/files/, following a Drupal-like storage model.
user/config/site.yamlfile under the taxonomy key.
EXPORT/pages folders to the `user directory in Grav.
Found errors? Think you can improve this documentation? Simply click the Edit link at the top of the page, and then the icon on Github to make your changes.