A modern, production-ready frontend workflow with Tailwind CSS and Gulp.
-
π¨ Modern Design System
- Tailwind CSS v3.4.15
- Dark mode support with system preference detection
- Custom color schemes (neutral, slate)
- Typography plugin integration
- Responsive design patterns
-
π οΈ Advanced Build System
- Gulp 5.0.0 workflow
- PostCSS processing
- JavaScript minification
- CSS optimization
- Live reload with BrowserSync
- Component-based architecture
-
π§ Development Tools
- Biome JS for formatting and linting
- Source maps for debugging
- Hot module replacement
- NPM scripts for common tasks
- Automated dependency updates
-
π¦ Production Ready
- Minified assets
- Optimized builds
- Cache busting
- SEO friendly
- Performance optimized
-
Clone the repository
git clone [your-repo-url] cd boilerplate
-
Install dependencies
npm install
-
Start development server
npm run dev
-
Build for production
npm run build
boilerplate/
βββ src/ # Source files
β βββ css/ # CSS files
β β βββ app.css # Main CSS file
β βββ js/ # JavaScript files
β β βββ app.js # Main JS file
β βββ components/ # Reusable components
β β βββ header.html
β β βββ footer.html
β β βββ home/ # Page-specific components
β βββ pages/ # HTML pages
β βββ index.html
βββ dist/ # Compiled files
βββ gulpfile.js # Gulp configuration
βββ tailwind.config.js # Tailwind configuration
βββ postcss.config.js # PostCSS configuration
βββ package.json # Project dependencies
The template includes a customized tailwind.config.js
with:
- Custom color schemes
- Dark mode support
- Typography plugin
- Extended theme settings
Components are modular and can be included using:
@@include('../components/header.html')
Dark mode is implemented using Tailwind's dark:
variant and supports:
- System preference detection
- Manual toggle
- Persistent preference storage
npm run dev
- Start development servernpm run build
- Build for productionnpm run clean
- Clean dist foldernpm run format
- Format code with Biomenpm run lint
- Lint code with Biomenpm run check
- Run Biome checksnpm run update-deps
- Update dependencies
- Create a new HTML file in
src/pages/
- Include necessary components
- Add content between header and footer
- Run development server to see changes
- Add new component in
src/components/
- Use Tailwind classes for styling
- Include in pages using
@@include()
- Use Tailwind utility classes
- Add custom styles in
src/css/app.css
- Configure theme in
tailwind.config.js
The production build:
- Minifies CSS and JavaScript
- Optimizes assets
- Generates sourcemaps
- Creates production-ready files in
dist/
We follow a simplified Git flow with these main branches:
main
- Production-ready codedevelop
- Development branch, integration of features
feature/*
- New features and non-emergency fixeshotfix/*
- Urgent production fixesrelease/*
- Release preparation
- Features:
feature/feature-name
- Hotfixes:
hotfix/issue-description
- Releases:
release/version-number
-
Create feature branch from
develop
git checkout -b feature/new-feature develop
-
Work on the feature
git add . git commit -m "feat: add new feature"
-
Merge back into develop
git checkout develop git merge --no-ff feature/new-feature
-
Delete feature branch
git branch -d feature/new-feature
-
Create release
git checkout -b release/1.0.0 develop
-
Merge to main and tag
git checkout main git merge --no-ff release/1.0.0 git tag -a v1.0.0 -m "Version 1.0.0"
- Fork the repository
- Create a feature branch
- Commit your changes
- Push to the branch
- Open a pull request
This project is licensed under the MIT License - see the LICENSE file for details.
Made with β€οΈ by Milon Biswas