How much does zuzu.codes cost?

The starter track is free — read all lessons and practice for free. Full access to every track (current and future) is $14.99/month. Cancel anytime.

How long does each track take?

Each track is designed as a 30-day challenge — one lesson per day, about 15 minutes each. Go at your own pace, but the structure is built around daily consistency.

What's the lesson format?

Each lesson is a student-teacher dialogue with code examples, followed by a hands-on code challenge in an in-browser editor. You read, you understand, then you write real code.

Do I need prior coding experience?

Our beginner track starts from absolute zero — no prior experience needed. Advanced tracks build on earlier ones, and the platform tells you exactly where to start.

How is zuzu.codes different from freeCodeCamp or Codecademy?

zuzu.codes uses a structured 30-day track format with dialogue-based teaching, an in-browser code editor, and gamification (XP, streaks, progress tracking). The format builds genuine understanding through daily practice.

Day 20 · ~12 min●

Google Docs comes next — the API for documents. The simplest write is the one you always do manually: create a new doc with a title. What do you think the params are?

Probably just a title? A doc is a title plus a body, and the body starts empty?

Exactly. GOOGLEDOCS_CREATE_DOCUMENT takes one required field — title. Google assigns a fresh documentId and sends it back in the response so your code can find the doc again later:

python

result = toolset.execute_action(Action.GOOGLEDOCS_CREATE_DOCUMENT, {"title": "Meeting notes"})
doc_id = result.get("documentId", "")

The documentId is the hook — if I want to read or edit this doc later, I need to hold onto that id?

That id is the key to everything else Docs can do — read content, update it, share it. Always return the whole response from a create action so the caller can grab the id themselves:

python

def create_doc(title: str) -> dict:
    result = toolset.execute_action(Action.GOOGLEDOCS_CREATE_DOCUMENT, {"title": title})
    return result

If I call create_doc("Meeting notes") twice, do I get one doc or two?

Two separate docs, each with a unique documentId and the same display title. Google does not deduplicate by title — that is left to your code. Most automations check for an existing doc first when uniqueness matters.

So Python can spin up a fresh report template on demand — one doc per meeting, per project, per anything?

That is exactly the unlock. Every scheduled run creates a fresh canvas and hands back the id so the next step can drop content into it.

Creating Documents

TL;DR: One required field — title. The response carries the new documentId you will use for every follow-up call.

Action enum — Action.GOOGLEDOCS_CREATE_DOCUMENT
Single param — title shows at the top of the doc
Response dict — {"documentId": "...", "revisionId": "..."}
No dedup — Google allows two docs with the same title; your code must check

Why return the whole dict

Field	Caller might need
`documentId`	fetch, edit, share later
`revisionId`	cache-busting, concurrency guards

Sign up to practice

Create a free account to get started. Paid plans unlock all tracks.

Day 20 · ~12 min●

Google Docs comes next — the API for documents. The simplest write is the one you always do manually: create a new doc with a title. What do you think the params are?

Probably just a title? A doc is a title plus a body, and the body starts empty?

Exactly. GOOGLEDOCS_CREATE_DOCUMENT takes one required field — title. Google assigns a fresh documentId and sends it back in the response so your code can find the doc again later:

python

result = toolset.execute_action(Action.GOOGLEDOCS_CREATE_DOCUMENT, {"title": "Meeting notes"})
doc_id = result.get("documentId", "")

The documentId is the hook — if I want to read or edit this doc later, I need to hold onto that id?

That id is the key to everything else Docs can do — read content, update it, share it. Always return the whole response from a create action so the caller can grab the id themselves:

python

def create_doc(title: str) -> dict:
    result = toolset.execute_action(Action.GOOGLEDOCS_CREATE_DOCUMENT, {"title": title})
    return result

If I call create_doc("Meeting notes") twice, do I get one doc or two?

So Python can spin up a fresh report template on demand — one doc per meeting, per project, per anything?

That is exactly the unlock. Every scheduled run creates a fresh canvas and hands back the id so the next step can drop content into it.

Creating Documents

TL;DR: One required field — title. The response carries the new documentId you will use for every follow-up call.

Action enum — Action.GOOGLEDOCS_CREATE_DOCUMENT
Single param — title shows at the top of the doc
Response dict — {"documentId": "...", "revisionId": "..."}
No dedup — Google allows two docs with the same title; your code must check

Why return the whole dict

Field	Caller might need
`documentId`	fetch, edit, share later
`revisionId`	cache-busting, concurrency guards

Creating Documents

TL;DR: One required field — title. The response carries the new documentId you will use for every follow-up call.

Action enum — Action.GOOGLEDOCS_CREATE_DOCUMENT

Single param — title shows at the top of the doc

Response dict — {"documentId": "...", "revisionId": "..."}

No dedup — Google allows two docs with the same title; your code must check

Why return the whole dict

Field	Caller might need
`documentId`	fetch, edit, share later
`revisionId`	cache-busting, concurrency guards

Creating Documents

TL;DR: One required field — title. The response carries the new documentId you will use for every follow-up call.

Action enum — Action.GOOGLEDOCS_CREATE_DOCUMENT

Single param — title shows at the top of the doc

Response dict — {"documentId": "...", "revisionId": "..."}

No dedup — Google allows two docs with the same title; your code must check

Why return the whole dict

Field	Caller might need
`documentId`	fetch, edit, share later
`revisionId`	cache-busting, concurrency guards