Include composer create-project command in installation example
#79
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I am new to the Laravel ecosystem, and the wording install Jetstream into your new Laravel project contradicted the red warning box further down in the Installation docs about "Jetstream should only be installed into new Laravel applications." In my mind, the ambiguity was "do I need to include the Laravel framework first before I
composer requireJetstream?"Again, new to the ecosystem, so I wasn't sure if the
artisancommand only came from the Laravel framework. My assumption was that "creating a new Laravel project" would mean that Jetstream included the necessary bits to start a new Laravel project, and that I shouldn't start withcomposer create-project laravel/laravel.After asking a couple people, I was informed that I was wrong, and that yes, I need to create a Laravel project first, before installing Jetstream. I figure that revising the docs may clear up any ambiguity for other new users.