DEV Community

ONE ALING
ONE ALING

Posted on

I Finished a Hackathon Sprint Pack Instead of Letting It Stay a Folder of Almost-Demos

#githubchallenge #devchallenge #github #webdev

GitHub “Finish-Up-A-Thon” Challenge Submission

This is a submission for the GitHub Finish-Up-A-Thon Challenge.

What I Built

I had a familiar half-finished builder problem: several hackathon ideas, each promising on paper, but not yet polished enough to share. The rough folder had product notes, scattered prototypes, and no single path from "idea" to "judge can open this and understand it."

For the GitHub Finish-Up-A-Thon, I turned that folder into a small sprint pack with working demos, public links, submission notes, and repeatable preview steps.

Repository:

https://github.com/aling15738639778-eng/hackathon-sprint-pack-2026

Live index:

https://aling15738639778-eng.github.io/hackathon-sprint-pack-2026/

The finished sprint pack includes:

  • ProductScope AI: a product scoping assistant that turns a rough idea into an MVP slice, risk list, validation plan, and launch checklist.
  • STEMLab Coach: an interactive STEM tutor with mini labs, quizzes, and a mastery score.
  • EcoPulse IoT: a simulated energy dashboard that detects abnormal power usage and recommends next actions.
  • MeshPulse Planner: a Meshtastic-oriented packet planning tool for community energy and cooling alerts.
  • Qdrant Pattern Compass: a vector-search recommender for product patterns, built with Qdrant local mode.

Demo

Live demos and source code:

The Comeback Story

The project was not really finished because:

  • The ideas were separate and hard to compare.
  • The demos did not have a shared public entry point.
  • The submission copy was not written.
  • There were no demo video assets.
  • Each project still felt like a private working note instead of a public artifact.

The finish-up work changed that into a more judge-friendly package:

  • a public GitHub repository
  • a GitHub Pages index
  • direct project links
  • demo video assets
  • submission drafts
  • clear README sections for status and judging

The biggest improvement was not a single feature. It was making each project understandable from the outside: clear title, direct demo link, code link, short explanation, honest limitations, and next steps.

My Experience with GitHub Copilot

GitHub was the backbone of the finish-up:

  • Git kept each project change reviewable instead of buried in a local folder.
  • GitHub Pages made the browser demos public without extra hosting work.
  • The repository README became a real project index.
  • The same repo now holds submission drafts, source code, demo assets, and run instructions.

I also used GitHub Copilot CLI for a final repository review. I asked it to read the sprint pack, summarize what it found, and suggest concrete README improvements without editing files. The most useful suggestions were:

  • add a quick-start comparison table
  • show project status and last-updated information
  • add a judge quick-reference section with direct demo, video, and code links

I added those sections after the review. That was helpful because the code already existed, but the repository still needed a better evaluation path for someone who lands on it cold.

The next pass would add longer narrated videos, automated smoke tests for every demo, and a single submission dashboard that tracks which contests each project has entered.

But the core finish-up is done: the ideas are public, runnable, documented, and ready for challenge submission.

Top comments (0)