The Main Rule: Build Through the Plugin
- You must complete this hackathon using the Devpost Codex plugin inside Codex.
- Run the full flow through the plugin: discover the hackathon, register, ideate, build, and submit. Don't drop out to the Devpost website unless the plugin can't do something.
- If you do leave the plugin for any step, note what forced you out. That's exactly the kind of feedback we want.
Track Feedback As You Go
- Keep a running log of feedback while you use the plugin. Don't wait until the end and try to remember.
- Capture anything worth noting: confusion, friction, bugs, dead ends, missing features, things that felt great, copy that read oddly, moments you weren't sure what to do next.
- For each note, jot down where you were in the flow (e.g., "during registration," "ideation, Path B") and what happened.
- Screenshots or short clips of anything broken or confusing are hugely helpful.
Suggestions Welcome
- Beyond bugs, tell us what you'd change. What would make a step smoother, faster, or clearer?
- Note anything you expected the plugin to do that it didn't.
Build Something Small
- The tool itself is secondary. Keep it tiny so you can move through the whole flow without getting stuck building.
- A simple, working tool is plenty. The point is to exercise the plugin, not to win.
Debrief
- After you submit, you'll sit down with the Devpost team to walk through your feedback log together.
- Come ready to talk through what worked, what didn't, and what you'd change.
- Honest, specific, critical feedback is the goal. Don't soften it. We want the rough edges.