Completely agree with your sentiment. It has been incredibly refreshing to use Tabler on my projects in comparison to the norm ("admin dashboard" templates) that tend to fight you when you don't follow their pre-defined layout, or when you want to extend the UI kit with your own components without having to re-implement the styling used by the kits.

How do you approach building on top of a dashboard template?

> Any change in /src directory will build the application and refresh the page.

Do you start from the demo page and start ripping off components that you don't need? Or do you pick specific parts from the template and build it from scratch from bottom up?

Even though templates seem to be an easy way to build stuff, I never understood the approach building from templates.

In this instance, think of it less as a template and more of a UI Kit. The demo is just there to showcase what's available in the kit.

Dashboards are usually quite unique depending on the data they display and purpose of them, so just ripping the demo isn't necessarily going to be the best approach to go with.

In my case I'd start with choosing a layout and throwing together a rough sort of navigation menu, and then building each page by scratch (or based off previous pages). It's as simple as browsing the demo to find which components you need and then just copy / pasting them, either directly from the demo page or from the documentation.

The only times I've ripped entire pages have been for auth pages, error pages, etc - i.e. pages that are usually quite common to all applications. I find that it's better to take a standardised approach for these pages as it's more intuitive for the users rather than reinventing the wheel.

Thank you for adding this. I love the look of this project and was quite excited. But I couldn't figure out how one would actually get started creating a site with it. Now I get it...