Foru.ms

"A Next.js & Firebase community platform that redefines the forum. We use 'Creative Misuse' to transform standard threads into Job Boards, Collaborative Stories, and Product Roadmaps—all in one app."

Comment

Inspiration

We entered this hackathon with one goal: to break the internet's oldest social structure—the Forum. Forums haven't changed in 20 years. We asked ourselves: "What if a thread wasn't just a discussion? What if it could be a Vote, a Job, or a Book?" This aligned perfectly with the "Creative Misuse" theme. We wanted to take a standard Forum database schema and "misuse" it to build three completely different applications.

What it does

Foru.ms is a chameleon. It looks and acts like a different app depending on the category you visit:

The Job Board:

Threads become job listings with salary tags, external application links, and company branding.

The Collaborative Storybook:

Threads become books. Comments become chapters. The UI shifts to a reading focus, encouraging users to write novels together.

The Product Roadmap:

Threads become feature requests. The "Reply" count becomes a "Vote" count, and status badges (Planned, In Progress) appear automatically.

Migration Engine:

We added a powerful /tools suite that allows communities to Export their entire forum to CSV and simulate Imports from legacy platforms like Discourse.

How we built it

We built Foru.ms using Next.js 16 (Turbopack) for its incredible speed and Server Components.

The Engine:

The core logic lies in our dynamic routing. We check the category type on the server and swap out the entire React component tree instantly.

Data Layer:

We used Firebase Firestore for its flexibility. We designed a "super-schema" for Threads that can hold metadata for any of our use cases without needing complex joins.

Design:

We customized Shadcn UI & Tailwind CSS to creating a "Secret Admin" mode that is invisible to normal users but gives us full control.

Challenges we ran into

The biggest challenge was the "Polymorphic Data" problem. How do you store a "Salary Range" and a "Book Chapter" in the same database table properly? We solved this by creating a flexible metadata system within Firestore. We also struggled with implementing universal access rights, leading us to build a Granular Thread Action system that ensures Edit/Delete buttons appear correctly for authors across all different dynamic views (Job, Roadmap, etc.).

Accomplishments that we're proud of

We are incredibly proud of the User Experience. The transition from a "Roadmap" to a "Story" feels magical because it happens instantly without a page reload. We also successfully implemented a "Seed Engine" that can populate the database with realistic AI-generated examples for every category in seconds, and a working Data Migration Tool that empowers users to own their data via CSV exports.

What's next for Foru.ms

We plan to add Real-Time Collaboration (using Firebase listeners) so multiple authors can write a story chapter simultaneously. We also want to implement AI Moderation to automatically tag job posts and filter spam.

Try It Out

Foru.ms

Built With

Share this project:

Updates