Blueprint Configuration
Blueprint aims to provide sensible defaults which align nicely with Laravel's conventions. However, you are free to configure Blueprint to follow your own custom conventions.
You may publish the configuration file when running the blueprint:new command by passing the --config (or -c) flag:
php artisan blueprint:new --config
Alternatively, you may publish the configuration file with the following standalone command:
php artisan vendor:publish --tag=blueprint-config
This will copy a blueprint.php file into the config folder. Similar to the default Laravel configuration files, each of the configuration options are preceded by a detailed comment.
In summary, there are options for customizing the paths and namespaces for generated components, as well as options to toggle code generation. For example, to always generate foreign key constraints or PHPDocs for model properties.
To see all the available options, browse the blueprint.php configuration file on GitHub.