Dashboard Tailwind CSS and Jigsaw

OVERVIEW

A repository to keep a study project for the development of a dashboard using only Tailwind CSS.

Tailwind CSS is a utility-first framework package with classes that can be composed to build any design, directly in your markup.

For quick learning this study will be developed with the Jigsaw Framework that allows building static sites using the modern tooling like that Laravel.

TO-DO

• ➕ Dashboard
• ✔️ Inbox
• ✔️ Login
• ✔️ Register
• ❌ DataTable

VIEW DEMO

Tailwind Dashboard Demonstration Some demo pages for the result to be seen

SPECIAL THANKS

This study is based on the content made by Adam Wathan (Creator of Tailwind CSS) in his Live in his YouTube Channel.

I'm just starting with Tailwind CSS but I can only thank Adam for the work he did. He really does an excellent job with Tailwind and his videos.

INSTALLING

To start the project it is essential to install the NPM dependencies:
$ npm install && composer install

BUILDING

When you'd like to generate your site, run the build command from within your project root:
$ ./vendor/bin/jigsaw build production

Jigsaw will generate your static HTML and place it in the /build_local directory by default.

PREVIEWING

To quickly preview your site, use the serve command and access the address http://localhost:8000 in the browser:
$ ./vendor/bin/jigsaw serve

You can also optionally specify the environment and port to serve like so:
$ ./vendor/bin/jigsaw serve production --port=8080

EDINTING

As we are using Laravel Mix to compile your assets (which is included in the default Jigsaw setup), we can use Browsersync by simply running:
$ npm run watch

CONTRIBUTING

1. Fork it!
2. Configuring a remote for a fork
3. Syncing a fork with the latest version
4. Create your feature branch: git checkout -b feature-123
5. Commit your changes: git commit -m 'Commit message'
6. Push to the branch: git push origin feature-123
7. Submit a pull request :D

PRECAUTIONS

Before commit, double check your code. Please dude.

• Execute a git pull to keep your checkout up-to-date
• Invoke a git diff --cached before committing
• NOT COMMIT BEFORE RUNNING THE PROJECT LOCALLY AND SEE THE CHANGES RUNNING
• MAKE SURE THE CHANGES WORK