Setting Up Your Course Workspace in VS Code
What is the course workspace?
The course workspace is where you keep everything you write and build this term. It is a VS Code folder, copied from a GitHub template, that holds your journals, literature notes, project files, and reusable templates, all version-controlled with Git. Everything is plain Markdown and plain files, so you own your work and can read it anywhere.
There is no separate notes app and no plugins to configure. You organize your work with folders and write in Markdown, the same tools you use for the rest of the course.
Step 1: Install VS Code, R, and Git
If you have not already, follow the Install VS Code guide. You also need R and Git, covered in Install R and Getting Started with GitHub.
Step 2: Create your copy from the template
- Go to the v2v-workspace repository.
- Click Use this template, then Create a new repository.
- Name it something like
mc451-workspace. Private is fine. - Click Create repository.
You now have your own copy of the workspace on GitHub.
Step 3: Clone it into VS Code
- Copy your new repository’s URL (the green Code button).
- In VS Code, open the Command Palette:
Ctrl+Shift+P(Windows) orCmd+Shift+P(Mac). - Type Git: Clone and press Enter.
- Paste your repository URL.
- Choose a folder you will remember, for example
Documents/MC451/. - When VS Code asks, click Open to open the cloned workspace.
Step 4: Install the recommended extensions
When the workspace opens, VS Code shows a prompt in the bottom-right: “This workspace has extension recommendations.” Click Install All. These are defined in .vscode/extensions.json so the whole class shares one environment:
| Extension | What it does |
|---|---|
| Quarto | Preview and render .qmd documents |
| R (REditorSupport) | Run R code and view data inside VS Code |
| GitLens | See who changed what, and when, in your Git history |
If you miss the prompt, open the Extensions view (Ctrl/Cmd+Shift+X), type @recommended, and install from there.
Step 5: Read the README
Open README.md in the file explorer (left sidebar). It explains the folder structure and how to start a journal entry.
The workspace is pre-organized:
- 00_inbox captures ideas quickly.
- 01_journal holds your weekly reflections (committed to GitHub).
- 02_literature holds reading notes and Zotero annotations.
- 03_project holds your active research work.
- 04_resources holds images, PDFs, and attachments.
- **_templates** holds reusable templates.
Follow this structure to stay organized.
Step 6: Start a journal entry from the template
- In the file explorer, open
_templates/journal-entry.md. - Right-click it and choose Copy, then right-click the
01_Journal/folder and choose Paste. - Rename the copy for the week, for example
week-02-curiosity-and-trust.md. - Fill in the prompts and write your reflection.
Name files in lower case with hyphens instead of spaces (week-02-curiosity.md, not Week 2 Notes.md). Consistent names sort cleanly and never break links.
Step 7: Basic Markdown syntax
Notes use Markdown. The essentials:
| Syntax | Result |
|---|---|
# Heading 1 |
Large heading |
## Heading 2 |
Medium heading |
**Bold text** |
Bold text |
*Italic text* |
Italic text |
- List item |
Bullet list |
1. Numbered item |
Numbered list |
[Link text](https://example.com) |
Hyperlink |
> Quote |
Block quote |
`code` |
Inline code |
VS Code shows a live preview with Ctrl/Cmd+Shift+V.
Step 8: Commit and push your work
At the end of each week, save your work to GitHub. You can use VS Code’s Source Control panel (the branch icon in the left bar): stage your changes, write a short message, and click Commit, then Sync Changes. Or use the terminal:
git add .
git commit -m "Week 2 journal and literature notes"
git pushThis gives you a backup, a history of your work, and a way for Dr. Leith to see your entries. It also builds the version-control habit you use in the White Paper.
Troubleshooting
The extension prompt never appeared
Open the Extensions view (Ctrl/Cmd+Shift+X), type @recommended, and install the listed extensions.
I cannot push to GitHub
Confirm you are signed in to GitHub in VS Code (the Accounts icon, bottom-left) and that you cloned your copy of the repository, not the original template.
VS Code opened the wrong folder
Use File > Open Folder and select the workspace folder you cloned, not a parent folder above it.
Next steps
- Install VS Code, R, and Git.
- Create your copy from the template and clone it.
- Install the recommended extensions.
- Read
README.md. - Start your first journal entry from the template.
- Begin Phase I: The Journalist.
Resources
- VS Code docs: code.visualstudio.com/docs
- Markdown guide: markdownguide.org
Stuck? Come to office hours.