**AWS Student Builder Groups · Campus Hackathon**
## What We Built and Who It Helps
The Club Member Portal is built for a very specific person: a new Student Builder who just joined the club and has basic questions — *When is the next workshop? How do I publish on Builder Center? How do I set up my AWS account?* Instead of digging through scattered docs or waiting on a chat group, they log in, ask, and get a grounded answer with a source citation.
We built this in two phases:
- **Phase 1 (70% baseline, built before the event)** — sign-up, login, forgot-password, and a members-only chat that answers from an 8-file starter document pack, always citing its source.
- **Phase 2 (30%, built on hackathon day)** — a live-update twist. Club admins can publish new or changed documents, and the chatbot and member dashboard must reflect that update within ~60 seconds — no rewrite, no page refresh.
## Phase 1: The 70% Baseline
**Auth**
- Email + password sign-up and login.
- Forgot password: a member requests a reset link or code by email; we used a local mail flow for the prototype (nodemailer-style), with Amazon Cognito + Amazon SES as the intended production path.
- Chat is gated behind login — no guest access.
**Chat + retrieval**
- At startup, the app loads the 8-file starter pack (onboarding FAQ, AWS account setup, Builder Center publishing guide, Bedrock starter, hackathon rules, workshop index, Lambda patterns, and SBG community info) into our retrieval layer.
- Every answer cites the source file and section it came from.
- If the answer isn't in the documents, the bot doesn't guess — it returns a fallback pointing the member to the campus AWS Student Builder contact, pulled from `01-onboarding-faq.md`.
- We never invent AWS pricing, limits, or policy details — anything outside the document pack gets the fallback, not a guess.
**Screenshots to include here:**
- Sign-up screen
- Login screen
- Forgot-password flow (request → reset email/link)
- Chat with a sourced answer
- Chat fallback when the answer isn't in the docs
## Phase 2: The 30% Event-Day Twist
On hackathon day, the scenario changed: schedules moved, rooms changed, lunch was delayed — and club admins needed a way to push updates that members (and the chatbot) would see almost immediately. We extended the same 70% portal rather than rebuilding:
- **Admin publish** — an admin-only page to add or update a club document (paste or upload).
- **Re-index on publish** — new or changed content becomes searchable within ~60 seconds of publishing.
- **Chat sync** — the next question a member asks is answered from the freshly rebuilt index, with no manual refresh.
- **Live dashboard update** — the member's document list updates in place within the same ~60-second window.
- **Event-day briefing loaded** — `event-day-briefing.md` (today's schedule, rooms, judging times, deadlines) was added to the index, and citations reference it directly.
- **Smoke tests** — we ran the 3 required questions from `09-smoke-test-questions.md` against the live system and tracked pass/fail for the demo.
**Required API contract**
Judges and the automated evaluator call our system directly, not through the UI:
```json
// Request
{
"question": "..."
}
// Response
{
"answer": "The grounded answer...",
"sources": [
{
"document": "event-day-briefing.md",
"chunk_id": "optional-team-chunk-id",
"rank": 1,
"score": 0.91
}
]
}
By
Team Rabi
Loading article