midudev / midudev/itsfree.dev

Proposal: Suggested $0-starting Stack Builder based on catalog metadata

Open
#20 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
76
Forks
18
Avg merge
3d 20h
Merged PRs (30d)
1

Description

Problem / Motivation

Currently, itsfree.dev is fantastic for discovering individual tools by category or search. However, when developers start a new project (SaaS, API, static site, internal tool), they typically need to manually assemble and cross-reference multiple layers of infrastructure (Hosting + Database + Auth + Storage + Email + Monitoring + Analytics) to ensure they can launch without unexpected initial costs.

Proposed Solution

A lightweight, non-intrusive section on the home page that suggests cohesive infrastructure stacks based entirely on existing catalog metadata:

  • 100% Grounded in Catalog Data: Does not introduce external services, AI models, or accounts. It uses the tools, tags, and limits already verified in itsfree.dev.
  • Honest & Pragmatic Copy: Avoids misleading claims like "free forever" or "unlimited". It frames recommendations transparently: "Starting at $0 / mo · within listed free-tier limits".
  • Native Design System: Built with the exact same .resource-card architecture, typography, and dark/light tokens already present in the catalog.
  • Developer Utility: Includes a 1-click "Copy Markdown Stack" button so makers can instantly paste their chosen architecture into their project's README.md.
Preview / Screenshot
Image
Status & Prototype

I have already implemented and tested this component in my fork with zero build errors (pnpm check and pnpm build clean, 0 external dependencies):

Would you be interested in a Pull Request for this feature, or would you prefer any adjustments to the scope/UX first?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the existing home page catalog, catalog metadata, and .resource-card design system before evaluating the proposed stack builder. Compare the fork's feat/stack-builder prototype and its pnpm check and pnpm build results with the requested catalog-grounded recommendations and Copy Markdown Stack behavior. Done means an agreed scope and a working, native component without external dependencies.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
developer-experience, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.