Unit 07
The Studio
By the end of this unit your team has a real project environment — a cloned repo, a shared board, an organised file system — and you can point at a specific card and say "that one was mine," with hours logged and a link to prove it.
Six units, and every one of them was you, alone, on your own machine. That was deliberate — you needed to be fluent before you needed to coordinate. It stops now.
The Studio is a bigger project than Top 6: a multi-page site, built from a
ThemeStarter template handed to your team through GitHub Classroom, not
just to you. You will divide it, build it, argue about it, and ship it
together — and this unit is the scaffolding that makes “together” work
instead of turning into three people quietly rewriting each other’s CSS.
File systems
A professional project is not a folder called stuff2-FINAL-reallyfinal. It
is organised the same way every time, so that anyone on the team — including
you, in three weeks — can find anything without asking.
| Folder | Holds |
|---|---|
STOCK | Raw sourced images, not yet edited — straight off Unsplash or your camera. |
IMG | Edited images, ready for the web — cropped, compressed, exported at the size the site actually uses. |
HTML | The code. |
LOGO | The Adobe source files and the delivered logo package, from Unit 5. |
RESEARCH | Reference articles, comparison screenshots, the stuff that justified a decision. |
Add this question to
Loading your meetings…
A teammate found three competitor sites and screenshotted the ones with layouts worth studying, before you started building. Which folder?
Five folders, five jobs, no overlap. A file system a stranger can navigate without asking you where things are is a professional habit, not a formality.
Two of those folders live somewhere your repository does not: a shared,
cloud-synced drive with offline access — Google Drive, OneDrive, whatever
your team already has — holding STOCK and RESEARCH so the whole team can
drop files into them without a pull request. Your repository is for code.
Your cloud folder is for the raw materials that become code. Confusing the
two is the single most common way a Studio project turns into “wait, who has
the good version of that photo.”
KANBAN
Your team’s board lives on Trello — a free account, one board per team. We are not building a first-party version of this, on purpose: the whole point of a KANBAN board is that it is a shared, external, always-current record of who is doing what, and that is exactly what a real team uses one for. Learning Trello here is learning the tool, not a simulation of it.
A board has three columns you will actually use: To Do, In Progress, Done. A card moves left to right, never backward without a conversation.
Add this question to
Loading your meetings…
Which of these is a well-written card?
A card is a problem, sized to one class period or at most a week, that any team member could pick up and solve without a prior conversation about what 'better' means.
When a card moves to Done, it carries evidence — not “I did it,” but what you actually did, logged in 15-minute increments. That granularity is not arbitrary: it is fine enough to be honest and coarse enough to not be annoying, and it is the unit this course’s invoicing is built on.
Working as a team
A team divides work into pieces one person owns and finishes — not “we both kind of did the whole thing,” which is how nobody can tell you what either of you actually built.
That division is the whole reason Studio teams stay small: two people, sometimes three. Any more and “who owns this” stops having a clean answer.
Here is where you set your team up for real, and where the record of what you, specifically, delivered gets built — one line at a time, tied to a card, with a link.
Final project planner
Six steps. Everyone on the team fills this out — your invoice is yours alone.
Who's on this?
Commit to a mood
The same eight themes from Units 3 and 5. Pick the one your Studio project is actually built on top of — this is a record of a decision you already made, not a new one.
Clone your repo with GitHub Desktop
Link your board
Your invoice
One line per Trello card you completed. Hours in quarter-hour steps —
WD7.2.C asks for real 15-minute increments, not round numbers picked to look tidy.
Review, then submit
What earns points5 pts
- 1Repo cloned through GitHub Desktop and a live Trello board linked
- 2Every line item names a specific completed task with a real Trello card link
- 1Hours are logged in genuine 15-minute increments, not round guesses
- 1Notes give a teacher enough context to check the work against
Revision
A first draft of a team project is never the shipped one. WD7.4 is the
habit of taking that seriously instead of personally.
| Reacting | Revising | |
|---|---|---|
| First move | Defend the decision | Write down what was actually said |
| What changes | Whatever feels easiest to argue away | The specific things named, in priority order |
| How you know it worked | "I think it's better" | You can point at the before and the after |
Submit for review · text
Read by a human · you can resubmit
Get real feedback on your Studio project — from a classmate, your teacher, or someone outside the class who'll actually look. Convert it into a prioritized list: the two or three changes that matter most, in order, and why those and not the others.
What earns points5 pts
- 1 Reflects feedback that was actually given, not invented
- 2 Puts items in a real, defensible order, not just a list
- 2 Says why those items outrank the ones left off
Feedback arrives as a pile. WD7.4.B is the skill of turning a pile into a plan — which is the difference between revising and just reacting to whatever was said last.
Submit for review · text
Read by a human · you can resubmit
Publish the improved draft, then say what changed between the two versions and how you know it's actually better — not 'it looks nicer,' something checkable.
What earns points5 pts
- 2 Names a specific, real change between the two drafts
- 2 States how they know it improved
- 1 The improved draft is actually live
This is WD5.6.C again, at the scale of a team project instead of a solo one — and it is the last time this course asks you to defend a change with evidence before it asks you to ship for real.
That is the unit: a file system organised the same way every time (WD7.1);
a shared board where a card names a problem and Done means evidenced
(WD7.2); work divided into pieces one person owns (WD7.3); and feedback
turned into a plan instead of just absorbed (WD7.4).
Unit 8 is where the training wheels come off the stylesheet and the project goes to a real address — not a preview, an actual URL you hand someone.
Where you are
Not startedAnswer the checks above whenever you like. They're not graded, and you can retry any of them.
Kept in this browser only, unless you sign in.
Signing in carries this — and everything else you've done here — onto any device, and keeps it if you clear this browser.
Intro to Web Design · members' unit
The Studio is behind a locked door
Units in Intro to Web Design are for people taking the course. Getting in takes a link or a key — signing in on its own doesn't do it.
What's in this unit · 5 min read
- File systems
- KANBAN
- Working as a team
- Revision
2 quick checkscode exercises
1 Sign in
With your school Google account. This is how your work reaches the gradebook — it doesn't open the unit by itself.
A key unlocks this browser and keeps your progress here; signing in keeps it with you across devices. Either way the key itself is only ever checked as a hash. Manage all of this on your account, read what signing in stores, or go back to Intro to Web Design.
Sources
- Gilmour Academy — Intro to Web Design
- Trello, Inc. — Trello