2 ms·

it looks like tabler uses jekyll underneath for docs and demo (which i personally like and am comfortable with). the demo is really nice, ahd while i'm not big

it looks like tabler uses jekyll underneath for docs and demo (which i personally like and am comfortable with). the demo is really nice, ahd while i'm not big on js any more, the js driving tabler looks fairly straightforward and appropriate to my eyes. the underlying html and css, however, give me pause about how easy it would be to integrate into a larger project. <div> soup is how i'd describe the demo html, and its css uses custom properties (css variables) in a way that, on first glance, seems to make it more verbose without adding power, flexibility, or maintainability (or accessibility, but that seems a really big challenge for data-heavy frontends like this). i'd probably try this out if i needed a dashboard on a project, but perhaps would want to test drive it on a small/test project to see where the gotchas are first.

tragictrash 4y ago
This is the kind of feedback that can really help a developer improve their skills
jcpst 4y ago
From what I understand, it should also work ok with more semantic html elements. But it would be nice to see maybe a little of that in the examples.
- krsdcbl 4y ago
  Basically even if it's not built in, adding a reset stylesheet underneath it would make it work with semantic tags just like with divs, so no worries about that. then again, you'd probably not have to care about semantic structure in dashboards anyways, as it's unlikely SEO is a concern. Might be worth considering for accessibility though.
  - jcpst 4y ago
    I liked the look of this enough for certain products ideas that I would just use this as customer facing!
EthicalSimilar 4y ago
The CSS variables actually provide that exact functionality, in a sense. They allow you to adjust the colour scheme, font sizes, layout (margins, padding) without having to grep all of the stylesheets. I stumbled across Tabler a few months ago and have integrated it into one of my projects. I love how easy it has been to throw a site together for a client with minimal time spent on writing stylesheets, or modifying your more generic "admin dashboard" templates that used to be the norm. I do, however, completely agree with your comment regarding <div> soup.
- clairity 4y ago
  i appreciate you contributing your experience on this. to be more specific, it looks to me like a lot of the css variables are too granular, likely because they're being generated via scss functions, and so must conform to a set of algorithmic conventions. but a lot of the time, you don't want to tweak just the default border color of the card component separate from its border width separate from the border color of a generic container (or whatever). i haven't delved deep enough to know precisely how this all plays out, but that's what it looks like to me on first perusal. bootstrap does this as well, and since tabler is built on bootstrap, it seems they're extending that precedent (there's a lot of "!important" going on to, which is not a good sign). i'll admit i'm not much of a bootstrap fan either. i'm slowly developing my own personal css framework where i'm trying to have no tooling at all, including no scss, and very, very minimal js (and certainly no framework or packaging/transpiling of js at all) by default. it leans heavily on css variables and all the other current css goodies (good riddens IE!). that way, it can fit into any use case without having to worry about tooling conflicts. bulma kinda takes this approach (particularly, no js), but it's weirdly not as extensive as i'd expected it to be.

tragictrash 4y ago

This is the kind of feedback that can really help a developer improve their skills

jcpst 4y ago

From what I understand, it should also work ok with more semantic html elements. But it would be nice to see maybe a little of that in the examples.

krsdcbl 4y ago
Basically even if it's not built in, adding a reset stylesheet underneath it would make it work with semantic tags just like with divs, so no worries about that. then again, you'd probably not have to care about semantic structure in dashboards anyways, as it's unlikely SEO is a concern. Might be worth considering for accessibility though.
- jcpst 4y ago
  I liked the look of this enough for certain products ideas that I would just use this as customer facing!

EthicalSimilar 4y ago

The CSS variables actually provide that exact functionality, in a sense. They allow you to adjust the colour scheme, font sizes, layout (margins, padding) without having to grep all of the stylesheets. I stumbled across Tabler a few months ago and have integrated it into one of my projects. I love how easy it has been to throw a site together for a client with minimal time spent on writing stylesheets, or modifying your more generic "admin dashboard" templates that used to be the norm. I do, however, completely agree with your comment regarding <div> soup.

clairity 4y ago
i appreciate you contributing your experience on this. to be more specific, it looks to me like a lot of the css variables are too granular, likely because they're being generated via scss functions, and so must conform to a set of algorithmic conventions. but a lot of the time, you don't want to tweak just the default border color of the card component separate from its border width separate from the border color of a generic container (or whatever). i haven't delved deep enough to know precisely how this all plays out, but that's what it looks like to me on first perusal. bootstrap does this as well, and since tabler is built on bootstrap, it seems they're extending that precedent (there's a lot of "!important" going on to, which is not a good sign). i'll admit i'm not much of a bootstrap fan either. i'm slowly developing my own personal css framework where i'm trying to have no tooling at all, including no scss, and very, very minimal js (and certainly no framework or packaging/transpiling of js at all) by default. it leans heavily on css variables and all the other current css goodies (good riddens IE!). that way, it can fit into any use case without having to worry about tooling conflicts. bulma kinda takes this approach (particularly, no js), but it's weirdly not as extensive as i'd expected it to be.