Skip to content

Commit 9a51633

Browse files
brunoborgesCopilot
andcommitted
Remove hardcoded navigation links from workshop markdown
The step viewer HTML/JS already provides prev/next navigation, so inline navigation links in markdown files are redundant. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
1 parent 74532f0 commit 9a51633

7 files changed

Lines changed: 0 additions & 14 deletions

File tree

workshop/00-overview.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,5 @@
11
# 🎮 Mona Mayhem — VS Code GitHub Copilot Workshop
22

3-
[← README](../README.md)
4-
53
---
64

75
> **Duration:** ~1 hour

workshop/01-setup.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,5 @@
11
# Part 1: Setup & Context Engineering
22

3-
[← Overview](00-overview.md)
4-
53
---
64

75
In this part you'll set up your development environment **and** teach Copilot about the codebase — so every future prompt starts with the right context.

workshop/02-plan-and-scaffold.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,5 @@
11
# Part 2: Plan & Scaffold
22

3-
[← Part 1](01-setup.md)
4-
53
---
64

75
Before writing any code, let's use **Plan Mode** to think through the architecture. Planning first helps you design better systems and gives Copilot the context it needs to generate higher-quality code.

workshop/03-agent-mode.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,5 @@
11
# Part 3: Agent Mode — Build the Game
22

3-
[← Part 2](02-plan-and-scaffold.md)
4-
53
---
64

75
Agent Mode lets Copilot autonomously plan and implement changes across multiple files. Instead of writing code line by line, you describe what you want and Copilot figures out which files to create or modify, then implements everything end to end.

workshop/04-design-vibes.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,5 @@
11
# Part 4: Design-First Theming
22

3-
[← Part 3](03-agent-mode.md)
4-
53
---
64

75
In this part, you'll use **Plan Mode** to design a comprehensive theme transformation, then **Agent Mode** to implement it. This is design-first development — start with the vision, iterate on the visuals, and let Copilot handle the CSS heavy lifting.

workshop/05-polish.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,5 @@
11
# Part 5: Polish & Multi-Agent
22

3-
[← Part 4](04-design-vibes.md)
4-
53
---
64

75
Now that the app works and looks great, it's time to polish. Instead of doing everything sequentially, you'll hand off polish tasks to **background and cloud agents** that work in parallel — letting you review results as they come in.

workshop/06-bonus.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,5 @@
11
# 🎉 Bonus & Extensions
22

3-
[← Part 5](05-polish.md)
4-
53
---
64

75
You've built a fully functional GitHub Battle app! Now it's time to push further with **open-ended challenges**. Use **Agent Mode** for all of these — describe what you want, and let Copilot help you build it.

0 commit comments

Comments
 (0)