Better feedback for better builds.

Submit a deck, a guide, an e-learning package, or a working link — then ask for structured signals across five lenses. Reviewers respond with strong / developing / needs-work and a specific reason. Proof over praise.

Build title

Review type

Stage

What should this help someone do?

0/240

Where should reviewers focus? — pick any

Attach the work

Drop a file or click to upload Decks, guides, or e-learning packages

.pptx · .key · .pdf · .docx · .zip (SCORM / xAPI) — up to 50 MB

Working preview link — required for anything that needs a runtime

Who should review it?

Anything else reviewers should know? — optional

0/240

Loading your reviews…

Loading the queue…

How a review works

1 RequestSay what you built and where to focus. Attach a file or a link.

2 SignalsReviewers rate each lens strong / developing / needs-work, with a reason.

3 ImproveYou get clear signals and mark the review resolved when you ship the next version.

The five lenses

Your review activity

0 RequestedReviews you've opened on your own work.

0 Signals givenEvery signal you give is a Builder Move.

Nova says

Structured beats vague — strong/developing/needs-work with one reason is worth more than "looks good."