[v5] Adjust the doc for GraphQL being optional

docs/api/graphql/graphql.md

@@ -10,9 +10,8 @@ The GraphQL implementation for [[= product_name =]] is located in [`ibexa/graphq
 ## Setup
 
 Using GraphQL requires a domain schema.
-The schema is generated automatically when installing [[= product_name =]].
 
-When you modify content types or product types in your installation, you need to regenerate the schema:
+Before using GraphQL for the first time, or anytime you modify content types or product types in your installation, you need to generate the schema:
 
 ``` bash
 php bin/console ibexa:graphql:generate-schema

docs/getting_started/install_ibexa_dxp.md

@@ -242,7 +242,6 @@ Install [[= product_name =]] and create a database with:
 
 ``` bash
 php bin/console ibexa:install
-php bin/console ibexa:graphql:generate-schema
 ```
 
 Before executing the command make sure that the database user has sufficient permissions.
@@ -256,7 +255,6 @@ Make sure to use a [strong password](security_checklist.md#strong-passwords) mee
 
     ``` bash
     php bin/console ibexa:install --no-interaction
-    php bin/console ibexa:graphql:generate-schema
     ```
 
     If doing so, [modify the password for the `admin` user](update_basic_user_data.md#change-password) before [going live with your project](security_checklist.md).

docs/getting_started/install_with_ddev.md

@@ -159,7 +159,6 @@ Once you've made this change, you can proceed to install [[= product_name =]].
 
 ```bash
 ddev php bin/console ibexa:install
-ddev php bin/console ibexa:graphql:generate-schema
 ```
 
 ### 7. Open browser
@@ -391,7 +390,6 @@ ddev composer install
 ddev php bin/console ibexa:install
 # Add some content types using a migration file (previously created on another installation) and update the GraphQL schema
 ddev php bin/console ibexa:migrations:migrate --file=project_content_types.yaml
-ddev php bin/console ibexa:graphql:generate-schema
 # Open the project in the default browser which should display the default SiteAccess frontpage
 ddev launch
 ```

docs/infrastructure_and_maintenance/security/security_checklist.md

@@ -319,4 +319,3 @@ to receive notifications when a security fix is released in a GitHub-hosted depe
 - Enable logging for [[= product_name =]], the web server, any frontend proxies, and the database.
 - Monitor the logs for unusual and suspicious activity. Consider using log monitoring software to make this easier.
 - Consider using different accounts for manual administrative tasks and for the day-to-day running of your installation. You could for instance configure [[= product_name =]] to use a different database user than the one you use during upgrades. This can make it easier to filter out noise in your log monitoring solution.
-