Roadmap
Future plans for the project
What's Next?
One day, I hope to make this into a dynamic web app that allows users to build their preferred stack using a nice UI and/or CLI, and thus skip the boring boilerplate configurations + the struggle of having to shoehorn different things together.
When I ditched create-react-app and used Vite to bootstrap a React project, I was blown away by the options provided by the Vite CLI. Despite being relatively inexperienced, I was still able to appreciate all the configuration work that it had saved me.
If this project had a CLI, I envision it would look like this:
- Package Manager: (npm/pnpm/yarn/bun)
- Code Linting and Formatting: (ESLint/ESLint + Prettier/Biome)
- Conventional Commit Linting and Formatting: (Commitizen+Commitlint+Husky)
- Performance Linting: (Million.js)
- Automated Semantic Versioning: (Semantic Release/Standard Version/Release It)
- Unit Testing Frameworks: (Jest/Vitest/Mocha/Chai)
- End-to-End Testing Frameworks: (Playwright/Cypress/Selenium/TestCafe)
- Front-End Language: (JavaScript/Typescript)
- Front-End Library: (React/Preact/Solid)
- Front-End Framework: (Astro/Gatsby/Angular/Svelte/Vue)
- Full-Stack Meta-Framework: (Next.js/Remix/Redwood/Wasp/Analog.js/Nuxt/SvelteKit/SolidStart/Qwik/Ember.js/Meteor.js)
- Front-End Component Sandbox: (Storybook/React Cosmos)
- Back-End Language: (Node.js/Node.ts/Java/Python/Go/Ruby/PHP)
- Database: (PostgreSQL/MySQL/SQLite/MongoDB/Supabase)
- ORM: (Prisma/TypeORM/Sequelize/Drizzle)
- CSS-in-JS UI Libraries: (Bootstrap/Material UI/Radix UI/Chakra UI/Mantine UI/Ant Design)
- Tailwind UI Libraries: (Shadcn/UI/Next UI/Park UI/Material Tailwind/Daisy UI/Preline UI/Flowbite/Headless UI/Tailframes/Keep React)
- State Management: (Redux/Zustand/Jotai/Recoil)
- CMS: (Sanity/Payload/Wordpress/Strapi)
- Monorepo Management/Build System: (Nx/Turbo)
- CI/CD: (GitHub Actions/GitLab CI/Travis CI/Circle CI/Jenkins)
- Popular Community Stacks: (T3/T4/Spartan/)
Milestones:
- Complete basic documentation site for my preferred Next.js stack [WIP]
- Deploy the app to
mfarabi.dev/stackbuilder. See Vercel's guide for serving multiple projects under a single domain. - Ideate further, finalize user flow. How do we manage all the permutations and combinations of tools? Stack Routes?
- Design the homepage
- Develop the homepage (Stack Builder was built with Stack Builder)
- Deploy to
stackbuilder.ioorstackbuilder.shorstackbuilder.dev - Based on the user's choices, generate a customized documentation pathway. Start with the most common stacks such as Angular and Vue.
- Create a customized version of npmtrends without the fluff and with better theming. Also check out npmcompare, npmcharts, and State of JS.
- Based on the user's choices, generate a customized script to bootstrap the app with their preferred stack
- Add authentication so users can save their preferred stack
- Create the Stack Builder CLI
- Create the Stack Builder GUI that generates the CLI commands
- Make it easy for people to create their own templates and share them with the community
Homepage Design Inspiration:
Feature Inspiration:
Last updated on