WRIGHT for Tailwind — A Simple Project Structure Generator

[fouad-salehi]

Hello,

I recently developed WRIGHT for Tailwind, a small Node.js CLI tool designed to simplify the initial setup of Tailwind CSS projects.

The tool generates a clean and organized project structure, including the basic files and directories needed to start building a web project without having to create the same structure manually each time.

Features
Organized project structure
Tailwind CSS setup
Pre-configured index.html
JavaScript entry file
CSS structure
Images and fonts directories
Favicon setup
Basic README generation
The main goal of the project is to reduce repetitive setup work and provide a simple starting point for Tailwind CSS projects.

GitHub repository:

https://github.com/fouad-salehi/wrightForTailwind

I would appreciate any feedback, suggestions, or recommendations from the Tailwind CSS community.

Thank you.

[Jeanlaris]

Hi @fouad-salehi,

This is a fantastic automation tool! Scaffolding boilerplate structures manually for Tailwind CSS projects can indeed become repetitive, and a CLI utility solving this natively streamlines setup significantly.

To make the tool even more versatile for modern workflows, you could consider adding:

1. Tailwind v4 Support: Automatic configuration of the new @import "tailwindcss"; CSS entry structure alongside legacy config options.
2. Template Presets: Options to scaffold directly with popular meta-frameworks or build tools (like Vite, Next.js, or Astro) instead of vanilla setups alone.

Great job sharing this project with the community. Keep up the excellent work!

[fouad-salehi]

Thank you so much for the detailed feedback, @Jeanlaris!

Tailwind v4 support and template presets for tools like Vite, Next.js, and Astro are definitely interesting directions for WRIGHT. I’ll keep these ideas in mind for future versions.

I really appreciate you taking the time to check out the project and share your thoughts!

[Jeanlaris]

I'm the one who feels honored to have the opportunity to collaborate. Coming from a hands-on mechanical background dealing with coffee dryers in rural Brazil, I've learned to look at systems from the ground up, and learning this fast has been amazing. Excited to see those features land!

[fouad-salehi]

That’s really interesting, @Jeanlaris! I really appreciate you sharing your perspective. Feel free to explain your ideas in more detail, especially regarding Tailwind v4 support and the template presets. I’ll take a look at them and consider them for future versions of WRIGHT. Thanks again for the thoughtful feedback!

[nhannm-vn]

_Congrats on the launch! Simplifying the repetitive bootstrap phase for Tailwind CSS projects is a great way to save setup time.

_Quick Feedback & Suggestions
Framework Agnostic vs. Vite Integration: Since many Tailwind users pair it with Vite, consider adding a quick CLI flag (e.g., --vite) to generate a Vite-powered Tailwind setup alongside the plain HTML/CSS static option.

_Tailwind v4 Alignment: Make sure the CLI template accounts for Tailwind CSS v4's CSS-first configuration (@import "tailwindcss";) so new users get a modern structure out of the box.

_Customization Prompts: Adding interactive clack or inquirer prompts (e.g., asking whether to include standard directories like fonts/ or images/) can help keep the generated output lightweight for users who want a minimal setup.

Great utility tool—thanks for sharing it with the community!

[fouad-salehi]

@nhannm-vn Thank you so much for the thoughtful feedback and suggestions! I really appreciate you taking the time to review the project.

Your suggestions about Vite integration, Tailwind CSS v4, and customizable directory generation are really useful. I’ll definitely keep them in mind for future updates.

Thanks again, @nhannm-vn, for the great feedback and for supporting the project!

[fouad-salehi]

Hi @Jeanlaris and @nhannm-vn,

Quick update — thanks again for your feedback earlier on this project.

I've added Tailwind version selection (v3 / v4) to WRIGHT for Tailwind. Users are now asked which version they want during setup, and the generated project adapts accordingly:

• v3 → https://cdn.tailwindcss.com
• v4 → https://cdn.tailwindcss.com/4

The generated stylesheet.css also uses the correct directive:

• v3 → @tailwind base; @tailwind components; @tailwind utilities;
• v4 → @import "tailwindcss";

Your suggestions were really helpful and directly shaped this update. Thanks again for taking the time to review the project.

Repo: https://github.com/fouad-salehi/wrightForTailwind

[nhannm-vn]

Hi there @fouad-salehi ,

Thank you so much for the update! I'm really glad that our feedback was helpful to you. The v3/v4 selection feature is an awesome addition and will definitely make the project much more flexible.

Let's follow each other here on GitHub so we can keep sharing ideas, learning, and maybe collaborating on future projects. Wishing your project continuous growth and success!

Cheers!

[fouad-salehi]

Hi @nhannm-vn,

Thanks a lot for the kind words! Really glad the update aligns with what you had in mind. Your feedback was genuinely helpful.

Just followed you back — happy to stay connected and keep sharing ideas.

Cheers!

[fouad-salehi]

@nhannm-vn Quick follow-up — I just released the full WRIGHT v2.0.0.

It's a multi-preset architecture that unifies vanilla, Tailwind, and Bootstrap into a single tool with a shared core and independent presets.

The Tailwind v3/v4 support you suggested is now a core part of the Tailwind preset — that idea came directly from your feedback.

If you'd like to check it out:

https://github.com/fouad-salehi/wright

Thanks again — this release genuinely wouldn't look the same without your input.

Cheers!

[nhannm-vn]

@fouad-salehi ya sure, i will try it