maker hub

Discover what makers are building today. Stay inspired, explore fresh updates, and keep your own streak alive—one post at a time.
Your daily maker log. Track your build streak, reflect on past updates, and show the world your consistency through raw, honest posts.
Highlight your projects and progress. Share what you’re making, how it’s evolving, and let your work speak louder than credentials.
Join and Sign in page wtih google oauth

Inspiration

A new wave of makers is emerging — not defined by degrees or job titles, but by what they actually build. They're self-driven, community-powered, and shipping with vibes. We wanted to create a space that reflects who they are — not with polished résumés, but with raw daily logs and project streaks. Maker Hub is our answer: a lightweight, streak-based builder log for the next generation.

What it does

Maker Hub lets you post a short update every day about what you're building. Each post builds your streak, shows your progress, and becomes part of your public maker profile. It's part portfolio, part motivation system — built to keep you moving, one post at a time.

How we built it

Everything was built inside bolt.new — from UI design to backend architecture.

Frontend: Next.js 15 + Tailwind CSS Backend & Storage & Auth: Supabase Deployment: Netlify Design & Project Architecture: Prompt-based in bolt.new

I simply gave prompts like “a daily post feed with profile pages,” and bolt.new handled the rest — layout, styling, even the backend architecture. It generated a solid foundation where I could immediately start building and customizing.

The .env.example file was all I needed — copy it to .env.local, and it just worked. Bolt’s base project was so complete, I could focus on extending it with features that matter to me.

Challenges I ran into

Finding the right idea wasn’t easy. I explored many directions to make sure the product would be both useful and personally meaningful.

I didn’t just write one perfect prompt — I went through multiple iterations. Using Discuss mode, I spent a lot of time refining prompts to clearly express my intent. It wasn’t just about getting a response — it was about shaping the product’s structure together with AI.

Then I faced the next challenge: How do I express that structure clearly through UI and UX? I thought a lot about how to make the interface feel minimal but expressive — especially around posting, project selection, and streak tracking.

On the technical side, I was new to Supabase — especially RLS and the database layer. I also had to work around Supabase not fully supporting Next.js 15 server actions.

Accomplishments that I'm proud of

✅ Every core MVP feature we imagined worked on the first try
⚡ Built the entire product—frontend, backend, and auth—inside bolt.new, with zero setup stress
✍️ Created a new kind of builder profile: one post a day, streak-based, raw but real
🧠 Turned a vague feeling ("we need a space for vibe coders") into a working product
💡 Designed and launched in days, not weeks — staying focused, minimal, and maker-first
🎯 Proved that motivation can be built, just like products — through streaks and identity

What I learned

I realized: the definition of “maker” is expanding. It’s not just developers or indie hackers anymore — it’s also designers, PMs, marketers, anyone creating something with intent.

As a frontend developer, I wasn’t familiar with Supabase or Netlify — especially things like databases or RLS (Row Level Security). But bolt.new handled most of it for me, and honestly? It surprised me how well it worked.

The backend architecture, auth, and data flows were solid out of the box. It made me realize: development has gotten easier — now what really matters is what we choose to build.

I also learned how important the first prompt and global settings are when working with prompt-based tools. They shape everything downstream. For my next project, I plan to start with a cleaner, more structured setup — so both bolt and I can work even better together.

This project wasn’t just about shipping a product. It was about realizing how far the tools have come — and how much more creative we can be when we let them handle the scaffolding.