This repository has been archived by the owner on Jul 19, 2021. It is now read-only.
Docs new getting started #205
Merged
Conversation
This file contains 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
bertiful
suggested changes
Jul 19, 2017
|
|
||
| Create `config.yml` in your root using [this sample file](https://github.com/Shopify/slate/blob/master/config-sample.yml), then use [theme commands](#theme-commands) to start developing. | ||
| A `config.yml` will also be created in your root directory which is required for [build commands](#build-commands) and [sync commands](#sync-commands). |
docs/index.md
Outdated
| @@ -47,8 +69,8 @@ The steps below walk through installing Slate globally and configuring your deve | |||
|
|
|||
| > Learn more about [all commands and descriptions](/slate/commands/) or how to [deploy to multiple environments](/slate/commands/#sync-commands). | |||
|
|
|||
| ## Working with `git` | |||
| ## Working with git repositories | |||
docs/index.md
Outdated
|
|
||
| A new Slate project comes with a `.gitignore-sample` file. This file is meant to be a starting point for your own `.gitignore` file if you will be using `git` for version control. The sample files contains a list of files and folders to be ignored when committing to a git repository. Ignored files are both Slate project specific files as well as commonly ignored files on any project. | ||
| A new Slate project comes with a `.gitignore` file. This file is useful if you plan on using `git` for version control as it contains a list of files and folders to be ignored when committing to a git repository. Ignored files are both Slate project specific files as well as commonly ignored files on any project. |
There was a problem hiding this comment.
Same here - instances of git and "git" with Git
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What are you trying to accomplish with this PR?
New documentation to reflect the changes coming from 0.11.0 #202
Additionally, I've changed the setup instructions to start a new project from a manual deploy. The existing steps were shorter, but it also assumed you had a theme in your store you'd want to overwrite (to get the theme ID). The problem with this is now your live theme may have folders not in your local project.
Checklist
For contributors:
For maintainers:
package.jsonversion in a separate PR, if applicable.