Tools & Account

• Install VSCode.
• Make a work folder somewhere sensible (like Documents), e.g. ITIS3135Work. Not Downloads, not Desktop, not a random spot — know how to navigate to it.
• Create a GitHub account (personal or school email — personal keeps access after you leave CLT) and install GitHub Desktop.

The Repo & Pages

• In GitHub Desktop, create a repo named exactly yourgithubid.github.io (login Bobby77 → repo Bobby77.github.io), inside your work folder. Public, not private — these are webpages. A readme is a good idea.
• On github.com, in the repo's settings, turn on GitHub Pages with main as the web root.
• In VSCode: create index.html ("Yo it's so-and-so, and this is the root of my website!"). Turn on auto-save (on focus change) and install the Live Server extension (Ritwick Dey) — Go Live previews your page properly.
• In GitHub Desktop: commit, then push to origin. Test at http://yourgithubid.github.io (may take a few minutes) and see the files at http://github.com/yourgithubid (instant).

Course Folder Structure

• Inside the repo, make an itis3135 folder with its own index.html: "<h1>I am so-and-so and this is my ITIS3135 First Course Page</h1>" — with your name.
• Also inside itis3135, create: images/, components/ (empty header.html + footer.html), scripts/ (empty include_components.js), styles/ (empty default.css), and z_archives/ (for junk you're afraid to delete). GitHub ignores empty folders until they have files — that's fine.
• Commit and push again; confirm itis3135/ loads on your Pages site.

Submitting

• The URL of your repo on github.com.
• The URL of your GitHub Pages site (yourgithubid.github.io).
• Anything you'd like to note.
• Then reply to two peers with constructive feedback — find a real problem and tell them politely.

What gets checked: your github.io site loads, and your name appears somewhere on the page.