Discussion map · Where to post what, and how to find things

[akash-coded]

Eight categories, and it is not always obvious which one you want. This is the whole decision in one table.

You want to…	Post in	Why there
Ask something and get an answer	Q&A	Answerable — good answers get marked and stay findable
Report a broken notebook or wrong doc	Issues	Not a discussion. Issues get tracked and closed
Work through an exercise, or compare answers	Exercises	Reply in the exercise's own thread
Work through a multi-hour lab or capstone	Hands-on Labs	Same, for the longer builds
Share what you built	Show and tell	The most persuasive content here
Propose a topic, lab or improvement	Ideas	Feeds the extension roadmap
Vote on what gets built next	Polls	Reaction-vote threads; results steer the roadmap
Anything else	General	Introductions, war stories, opinions
Read what changed	Announcements	Maintainer-only

---

Finding things

There are 50+ practice threads. Two ways in:

The index — every exercise and lab, by track and level.

Labels — every practice thread is tagged with a track, a level, and a format. Filter directly:

Level	🟢 foundational · 🟡 intermediate · 🔴 advanced
Format	💻 code · ✏️ no-code · 📐 design
Track	retrieval · agent-loop · evaluation · product · and ten more

Combine them. label:"track: retrieval" label:"level: foundational" is a perfectly good way to start.

---

What makes a good post here

Asking. Four things turn a question that sits for a week into one answered in an hour: the module or lab, the exact error pasted in full, your region, and what you already tried. Check troubleshooting first — it covers the errors this curriculum actually produces.

⚠️ Remove your AWS account ID and any credentials before pasting. Account IDs in this repo are the placeholder 123456789012; do the same with yours. (This is not hypothetical — a real account ID was found and scrubbed from an existing thread here.)

Answering. Beginners asking beginner questions is what this place is for. "Just read the docs" helps nobody. Two minutes of your time saves someone an evening.

Sharing. What it does, which modules it came from, and what was harder than expected. That third one is usually the most useful part.

Disagreeing. Encouraged, on specifics. Several exercises here have more than one defensible answer, and where a solution states a preference it should give a reason. If it does not, say so.

---

Conventions

• Reply in the thread, not a new one. An exercise thread with fifteen replies is worth more than fifteen threads.
• Titles should survive being a search result. "Help!!" and "question about RAG" will be retitled.
• Spoilers. Working through an exercise? Wrap a full solution in <details><summary>Solution</summary> so other people can still attempt it.
• Code in fences, with the language tag. Errors in full, not summarised.

---

Not sure? Post in General

Wrong category is not a problem — maintainers move things. Posting nothing because you could not decide is a problem.