Progress 0 / 8 lessons completed

Quiz state is saved in this browser

Basics

Vibe Coding Basics

Your first steps in vibe coding: turn a real campus problem into a real app with GitHub Copilot.

Lesson 1

What is vibe coding?

Vibe coding means building an application by describing what you want to an AI, instead of writing every line of code yourself. With GitHub Copilot, you explain your need in plain language and the AI proposes the code; you stay in charge — you read, adjust, and approve.

For higher education, this changes everything: you can finally build the small tool you've imagined for years, without waiting on an IT department or spending six months learning to program. This track walks you through it step by step, using one real teaching project as your thread.

TipYou don't need to install anything to read this track. Installing Copilot comes in the next lesson.
Try it yourselfWhatever your role — teaching, studying, IT, HR, management, finance — write down, in one sentence, the small app you'd love to have. You'll build a real one in Lesson 3.
Lesson 2

From a real campus problem to an app idea

The best starting point is never a technology, it is a real campus problem: students have no easy way to revise, a service keeps answering the same question by email, a team tracks a budget line in ten spreadsheets, a lab needs a lightweight booking page. Start from lived friction.

Describe the problem in one sentence, then imagine the smallest possible app that would reduce that friction. A quiz, a page, a calculator, a tracker, a searchable FAQ: keep it simple first, then grow it once people are actually using it.

TipWrite your idea as: “An app that lets [who] do [what] so that [what benefit]”.
Try it yourselfPick ONE real problem you or a colleague complains about weekly — in class, at the help desk, during onboarding, in a budget meeting — and write your app idea using the sentence above.
Lesson 3

Your first web app with GitHub Copilot

This is the lesson where you actually build something. Install the GitHub Copilot extension in Visual Studio Code, or open Copilot Chat directly on github.com/copilot with your GitHub account, then create a new file called index.html.

Below, we build a real, working example together — a “Quick Poll” you could use in a class, a training session, a team meeting, or a town hall. Follow the steps with your own copy of Copilot, then try the finished result live at the end.

Step 1 — Describe the skeleton

Open Copilot Chat and describe the smallest possible version of your idea. Be specific about what's on the page.

Copilot Chat
Build a simple webpage called "Quick Poll" with a question and four buttons as answer options.
Here's a starting point:
<!DOCTYPE html>
<html>
<head><title>Quick Poll</title></head>
<body>
  <h2>What would help you most this term?</h2>
  <button>Worked examples</button>
  <button>More exercises</button>
  <button>Short videos</button>
  <button>Live Q&amp;A</button>
</body>
</html>

Save this, open it in your browser by double-clicking the file. You now have a real, if plain, webpage.

Step 2 — Ask for the logic

A page with buttons that do nothing isn't very useful yet. Ask Copilot to make the buttons count votes.

Copilot Chat
When someone clicks a button, save a vote count for that option in the browser (localStorage), so it's remembered if the page reloads.
I added this script at the bottom of your page:
<script>
  document.querySelectorAll("button").forEach((btn, i) => {
    btn.addEventListener("click", () => {
      let votes = JSON.parse(localStorage.getItem("votes")) || [0,0,0,0];
      votes[i]++;
      localStorage.setItem("votes", JSON.stringify(votes));
      alert("Thanks for voting!");
    });
  });
</script>

Test it: click a button, reload the page, click again — the count keeps growing even though you can't see it yet. That's next.

Step 3 — Show the results

Now ask Copilot to replace that plain alert() with something people can actually see.

Copilot Chat
Instead of an alert, hide the buttons after voting and show each option as a percentage bar based on the votes so far.
Good idea — that's much clearer for people voting. I replaced the alert with a small results view that calculates each option's share of the total votes and animates a bar for it. Want me to also add a "vote again" link to reset it for this demo?

Keep going like this — one small request at a time — until the page looks and feels the way you want.

Step 4 — Try what you just built

This is exactly the app described above, already built and running below. Click an option and watch the results appear — this is what your students, colleagues, or team will see once you publish yours (next lesson).

quick-poll.html
TipAlways start from a tiny working version before adding features — step 1 above is a complete, working page all on its own.
Try it yourselfRebuild this exact Quick Poll yourself in a new index.html file, then change the question and the four options to match your own role — a class topic, an onboarding question, a budget priority, anything real to you.
Lesson 4

Saving and publishing with GitHub

Once your first version works, create a repository on GitHub and push your code to it — this is called a commit. From that point on, your work is saved online, versioned, and you can always go back to an earlier version if something breaks.

Then turn on GitHub Pages for that repository: in a few clicks, your app becomes reachable through a simple link you can share with students or colleagues, with no server to manage.

TipA GitHub repository is also your backup: even if your computer dies, your project is safe.
Try it yourselfCreate a free GitHub account if you don't have one, push your Quick Poll to a brand-new repository, and turn on GitHub Pages for it.
Lesson 5

Testing and improving with Copilot Chat

Have one or two colleagues try your app, or test it yourself by putting yourself in a student's shoes. Note every bug or awkward moment, then describe them one by one to Copilot Chat: “when I click this button, nothing happens, fix it”.

Copilot can also explain existing code you don't fully understand yet: ask “explain this part to me” before asking for a change.

TipOne fix at a time: it's easier to check it worked, and easier to undo if needed.
Try it yourselfSend your published link to two colleagues (or classmates) and ask them to click through it. Write down every awkward moment they hit, then fix the first one with Copilot Chat.
Lesson 6

Improving style and appearance

Once your app works, ask Copilot to improve the presentation: your institution’s colours, clearer spacing, more readable text, stronger accessibility. You can also create a small Copilot Space with example copy, slides, or a style guide so the suggestions stay grounded in your own material.

Think about accessibility too: enough contrast, readable text, clear labels, and buttons that are easy to hit. Ask Copilot to check those points explicitly before you publish.

Try it yourselfAsk Copilot to restyle your Quick Poll using two colors that represent your institution or team, then open it on your phone to check it still looks good.
Lesson 7

Adding images, files, and documents

Many teaching tools need images, PDFs, or downloadable documents: a handout, a diagram, a form. Ask Copilot to add an image display area or a download button, then simply drop the file into your GitHub repository.

GitHub hosts your code and these files alike: no need for another tool to store your app's resources.

Try it yourselfAdd one image or one downloadable PDF to your Quick Poll (even a placeholder), commit it, and confirm it loads correctly on the published page.
Lesson 8

Wrap-up and on to the Advanced track

You now know how to turn a teaching idea into a real app: build with Copilot, save and publish with GitHub, test, improve the style, add files. The one habit that matters most: always move forward in small, checkable steps.

The Advanced track picks up from here to go further: connecting a real database, giving your project a lasting memory, and managing your code with GitHub like a real project meant to last.

Try it yourselfWrite a 3-line README for your project: what it does, who it's for, and how to reopen it with Copilot next time.
Track quiz

Basics quiz — can you launch a first app safely?

Five quick checks before you move on. Answer each question and read the explanation straight away.

Score0 / 5
Answered0 / 5

Quiz state is saved in this browser

1

Where can you try Copilot Chat with zero install from any GitHub account?

2

What is the best first shape for a vibe-coding project?

3

Why put even a tiny project on GitHub early?

4

What is the safer way to improve an app with Copilot?

5

Who stays in charge when Copilot proposes code?

Was this page helpful?