readme changes
This commit is contained in:
parent
89972fb172
commit
95829ca58c
1 changed files with 17 additions and 1 deletions
18
README.md
18
README.md
|
|
@ -1,4 +1,4 @@
|
||||||
# Write a new Blog Post (readmy)
|
# Write a new Blog Post
|
||||||
|
|
||||||
1. Create a new file in `/src/posts/`.
|
1. Create a new file in `/src/posts/`.
|
||||||
- You can create it in the VSCode sidebar, or in the windows flie manager, or in the terminal. It doesn't matter.
|
- You can create it in the VSCode sidebar, or in the windows flie manager, or in the terminal. It doesn't matter.
|
||||||
|
|
@ -31,6 +31,22 @@ npm run serve
|
||||||
|
|
||||||
Now, your blog is ready to be deployed. All generated files are located at `_site` folder, which you can deploy with any hosting service.
|
Now, your blog is ready to be deployed. All generated files are located at `_site` folder, which you can deploy with any hosting service.
|
||||||
|
|
||||||
|
|
||||||
|
# Pull down Spencer's changes from the git repo
|
||||||
|
|
||||||
|
Go to the Source Control panel (Ctrl+Shift+G) and click the 🔃 Synchronize Changes button under **Source Control Repositories**.
|
||||||
|
|
||||||
|
|
||||||
|
# Push up your own changes to the git repo
|
||||||
|
|
||||||
|
1. Save your work
|
||||||
|
2. Go to the Source Control panel (Ctrl+Shift+G). You should see pending changes.
|
||||||
|
3. Type a short explanation of your change into the 'message' text box.
|
||||||
|
4. Click commit, and click yes (or always) to 'stage changes and commit them directly'.
|
||||||
|
5.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
# Glossary of Terms
|
# Glossary of Terms
|
||||||
|
|
||||||
## Markdown
|
## Markdown
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue