Getting started on motu · Article 1

Introduction to motu

6 min read

Welcome to motu 👋 This first article is your map. We'll cover what motu is, what's on the platform, how we think about using AI while you learn, and what this path will leave you with. The next two articles get you set up to build, and then you're straight into your first challenge.

What motu is

Most people learning to code hit the same wall. You've watched the tutorials and followed along. You've built things by copying someone else's screen. Then you open a blank file to build something on your own, and nothing comes.

That wall is the gap between watching and building, and motu exists to get you over it. We give you real projects: a proper brief, a professional design and all the assets. No step-by-step instructions. You work out how to build it, exactly like you would for a client.

When you're done, you submit your solution. You get an AI review of your code, fix what it flags, and submit again to check the issues are gone. Then you look at how other people built the same thing, and give them feedback.

That's the loop: build, submit, get feedback, improve, build again.

A quick look at what's here

You don't need to learn all of this now. You'll meet most of it naturally as you go through this path.

Challenges are the heart of motu. They're sorted into five levels: Newbie, Junior, Intermediate, Advanced and Guru. Everything on this path is Newbie level, the right place to practise HTML and CSS. As you climb the levels you'll add JavaScript, accessibility, animation, APIs and full apps. Some challenges are free and some are part of Pro.

Pro is our membership. It gives you an AI code review on every solution, premium challenges, design files and asset packs, and extras like private solutions and custom domains. Free accounts get one AI review a month, and automated checks on every other submission. Pro is worth knowing about, but it's not something you need to decide on yet.

The AI code review scores your code on code quality, design and UX, and documentation, then tells you what stood out. We'll look at how to read one in article 3.

Learning paths are sets of articles and challenges, like this one. Each takes you from one clear starting point to another.

Product challenges (coming soon) are a newer format where you build from a product spec rather than a design. You make the design decisions yourself, build it with AI, and ship something real. Not something to think about yet.

How we think about AI here

AI tools like Claude, Cursor and Copilot are part of how developers work now, and you should learn to use them well. But if the AI writes everything, you learn nothing, and it shows the moment you're asked to explain your code.

So we use AI like a mentor, not a ghostwriter. Ask it to explain things. Ask for hints. Ask why something isn't working. Then write the code yourself.

AGENTS.md: how this is built into motu

Every challenge's starter files include an AGENTS.md file. Most AI coding tools read it automatically. It tells the AI how to help you at your level: lots of patient hints and analogies on Newbie challenges, and more independence as you get to Guru.

You don't need to do anything. Open the starter folder in your editor and your AI tool will pick it up.

What this path will leave you with

By the end of this path you'll have:

  • A working setup: an editor, GitHub and free hosting
  • Four finished, live projects you can show people
  • Your first AI reviews, and the habit of improving your code based on feedback
  • A feel for how the community works

What's next

Next up: getting your tools set up. It takes about 10 minutes and you only do it once.

Next step…

Setting up your development environment

Log in to save your progress