Like any Drupal site, you can surf to /core/install.php and go through the steps.
If you end up on this screen, drop all the tables in the database and afterwards, go back to the install page.
By default, we use English. Even if you're building a single language site
in Dutch, it is best to set everything up in English and add Dutch as an
additional language. This prevents several bugs with multilingual + makes it easier on your non-dutch-speaking coworkers.
If you don't want to use English as a language, you can disable the English language after your site development is finished, using the disable_language module, WITHOUT CHANGING ITS DEFAULT STATUS.
To reiterate: NEVER SWITCH THE DEFAULT LANGUAGE IN DRUPAL LANGUAGE CONFIGURATION!
There are two profiles to choose from, one that sets up a demo site and one that installs a site ready to develop/site build. Choose "Dropsolid Rocketship Profile" when starting a new project.
Fix any errors or warnings that come up
You normally won't land on this screen.
you can follow the progress of Drupal going through the installation.
Fill in the form where needed:
- replace with the client's email address if you already have one
Important note: User 1 (admin) does not get a password in rocketship projects. This is for security reasons. Our preferred flow is to have developers log in as user 1 using drush or users on the Platform to get a login using the project's "login" button.
Rocketship is set up as multilingual by default. The required modules are always enabled, and all that's required at any point in time is to just enable an extra language.
If you already know what languages you will use for this site, set them up now. This will place the language switcher block in the correct region.
If your project requires you to use 'disable language' to remove the English language, the editor still needs to be able to find the content that was originally created in English during site installation. Eg. the 404 and 403 page or any default generated content (more on that later).
For this reason, there is an option to set a 'default content language', which will set the original language for those migrated bits of content into your chosen language (eg. Dutch). Otherwise, if the content remains set as 'English', the editor won't have access to it and won't be able to translate them.
Here you can select any extra components + generate dummy content. This includes our pre-made features, and the option to select what theme to use.
For Dropsolid internal use:
At the very least, you can add these settings to get started:
- Blocks: Core, this will give you a large amount of custom block types to use with layout builder
- Core: Core + Content. That way you have a dummy homepage, 404 and 403 to start from
- Page: Every site needs to be able to use pages
- Theme: Rocketship Flex, Starter or Minimal for development.
This will take a while. See the progress on the installation of the extra components.
Rest of the translation stuff getting done, more waiting…
Before you can be finished, you have to set up the config split. This is
done using ../vendor/bin/drush d-set.
For this to work, make sure the following folders are writable:
- config/sync
- config/splits/local
- config/splits/dev
- config/splits/staging
- config/splits/live
- config/splits/whitelist
Read more about this in the Configuration Management section
