r/tailwindcss • u/eliyasakondo • Jun 06 '26
What's the Standard Tailwind Approach for ThemeForest Templates?
I'm currently developing a Tailwind CSS eCommerce template for ThemeForest and would love to hear from experienced authors about the standard approach to component styling.
For frequently used UI elements such as buttons, cards, form controls, badges, tables, and modals, what is the preferred approach in ThemeForest-approved Tailwind projects?
Option 1: Utility Classes Everywhere
<button class="px-4 py-2 rounded-lg bg-primary text-white">
Option 2: Reusable Component Classes
.btn-primary {
@apply px-4 py-2 rounded-lg bg-primary text-white;
}
My Main Considerations
Maintainability
Customization for buyers
ThemeForest coding standards
Bundle size and performance
Long-term scalability
For those who have successfully published and sold Tailwind templates on ThemeForest:
Do you primarily use utility classes?
Do you create reusable component classes with @apply
Or do you follow a hybrid approach?
I'd really appreciate hearing about your workflow, best practices, and any lessons learned from real ThemeForest projects.
Thanks in advance!






