Skip to content

Working with Project Files in VS Code

mike-snhu edited this page Aug 16, 2026 · 1 revision

Working with Project Files in VS Code

The projects repository uses several file types because different SDLC phases use different tools.

Markdown (.md)

Examples:

  • README.md
  • game_storyboard.md
  • text_based_game_sdw.md

Markdown is plain text with simple formatting marks.

To preview a Markdown file in VS Code, right-click the file and choose Open Preview, or use the Markdown preview button when available.

Draw.io (.drawio)

The Project One world map uses Draw.io format.

Open design/game_map.drawio in the course IDE. The course setup includes Draw.io integration in VS Code.

Keep the required .drawio format. Do not replace the graded map file with only a screenshot, PNG, or PDF unless the current assignment directions explicitly allow that format.

Pseudocode (.pseudo)

The course IDE includes pseudocode support for .pseudo files.

Pseudocode is a design language, not executable Python. Use clear steps, indentation, and course-appropriate keywords to describe logic.

Python (.py)

The milestone and Project Two use Python source files:

  • prototype/move_between_rooms.py
  • src/text_based_game.py

Run Python from the repository root so relative paths in the instructions match your current location.

Work From the Repository Root

When the Explorer shows it140-projects as the top folder, your integrated terminal should normally be able to use paths such as:

design/game_storyboard.md
prototype/move_between_rooms.py
src/text_based_game.py

If a command says a file does not exist, first run:

pwd
git status

On PowerShell, Get-Location can also show the current folder.

Avoid Editing Course-Managed Files

The repository may contain configuration, workflow, or reference files that support the course environment.

Edit the student-work files identified by the README. Leave course-managed files unchanged unless the activity specifically tells you to modify them.

Clone this wiki locally