update create astro and template flag instructions#2339
Merged
Conversation
✅ Deploy Preview for astro-docs-2 ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This fixes the instructions for running create astro with a template flag in the migration guides.
It also adds the example we have for starting a new project from any GitHub template from the hidden
integrations/integrationspage to Auto install, to better surface these instructions.Lastly, it changes most instances of
create-astrotocreate astro, since we are usually referring to the command to run, not the name of the package itself. (This has caused confusion in the past, so doing this while I'm here, but can be talked out of that change.) Admittedly, some of these occurances (both changed, and not changed) were judgment calls. Mostly based on what I thought might be least confusing to the reader. e.g. If the name of the wizard shows up JUST BEFORE they need to run the command, then I removed the hyphen so the reader is not seeing two conflicting things together.