07:38:45 <ChrisWarrick> !tell czz Only some extensions have support (as shortcodes). Thumbnails are really simple to do manually: https://getnikola.com/handbook.html#thumbnails 07:38:45 <KwBot> ChrisWarrick: acknowledged. 16:36:01 <KwBot> [nikola] mprasil opened issue #2896: Support hiding post-list in teaser https://github.com/getnikola/nikola/issues/2896 18:27:29 <ralsina> gour: if you have any description of what such a "modern" thing would look like, I'd like to see it, but 61 slides describing every feature the hugo team is thinking about is not it. 18:29:07 <gour> ralsina: hugulp project is more close example 18:30:00 <ChrisWarrick> Also, I really dislike the “but hugo” argument. 18:31:35 <gour> this is also useful example: https://themes.gohugo.io/hugo-theme-foundation6/, but i'm thinking about something more general 18:32:48 <gour> ChrisWarrick: i didn't play with many other ssg-s, except a bit with Pelican in the past, so besides Hugo & Nikola I do not see anything sufficiently interested to take a look at...considering I gave up on things like Grav CMS 18:33:17 <ChrisWarrick> gour: Presenting an idea without the “but hugo” part, instead with real arguments, would work better. 18:33:25 <ChrisWarrick> gour: There’s a foundation 6 theme for Nikola already 18:34:14 <gour> the fact is that today's CSS frameworks use JS-stuff as build system, so idea is to simply hook them into Nikola somehow...in the past, using less/sass and including jquery was probably enough, but not today :-( 18:34:35 <ChrisWarrick> You can just write a plugin that runs those tools, it shouldn’t be a problem. But do you really need to? You would usually make those changes pretty rarely, so you can just run that tool when necessary. 18:34:37 <ChrisWarrick> And from a theme end-user perspective, I don’t want to install the entire Node stack just to compile a single CSS file. Case in point: to do that with Bootstrap, 181 megabytes of disk space are needed. 18:35:17 <gour> ChrisWarrick: foundation6 theme does not have any build capabilities for customizing, afaict 18:35:27 <ChrisWarrick> gour: You can improve that 18:36:05 <ChrisWarrick> gour: And that H**o foundation6 theme uses JS tooling directly 18:36:47 <gour> ChrisWarrick: i also dislike modern JS-based system, but to customize things via SASS, using mixins etc. one probably cannot avoid Node-stuff 18:36:56 <ralsina> Then use SASS 18:37:14 <ralsina> if the tooling is to bundle / minify we already have that in place 18:37:27 <ralsina> If it's to use LESS/SASS, we already have that in place too 18:38:06 <ralsina> And in any case, it's probably easier to just create your theme whatever way you want using whatever tooling you want and just build it and have its output be Nikola's theme 18:38:17 <ralsina> you can even automate that using deploy, somehow 18:38:33 <gour> ralsina: what about things like autoprefixer, uncss and bunch of other things which are applied to css post-festum? 18:38:41 <ralsina> filters 18:38:53 <ralsina> Mind you, I have no idea what those things are :-) 18:39:13 <ralsina> uncss requires that you already have all the HTML built 18:39:21 <ralsina> so they can't even be in the CSS pipeline at all 18:39:36 <ralsina> you just need to run it on output/ 18:39:41 <gour> ralsina: you mean to just output CSS framework's result as Nikola's assets? 18:39:46 <ralsina> Sure 18:39:54 <ralsina> That's how SASS/LESS support is done 18:40:11 <gour> yeah, that looks simple-enough without complicating things further :-) 18:40:35 <ralsina> And you can use whatever the JS universe has decided is "make" this week :-) 18:41:08 <gour> ..which means, as ChrisWarrick suggested, to leave installing build-toolchain to the end-used if he/she want it instead of just customizing CSS directly, right? 18:41:16 <gour> :-D 18:41:29 <ralsina> Yep 18:41:49 <gour> sound good. thank you, guys, for clearing it up ;) 18:41:52 <ralsina> Or provide the equivalent of bower.json for 2017 and let the user use it 18:42:39 <ChrisWarrick> well, for September 2017 18:42:49 <gour> i'm considering to use latest foundation6 which has cli tool to create the project - i really do not want/like to go into Node-stuff 18:43:47 <ralsina> You can use any tooling as long as it ends producing a folder full of CSS Nikola won't notice 18:44:13 <ralsina> ChrisWarrick: first half of september 2017, if it can get done fast enough 18:44:45 <gour> even the small frameworks like https://github.com/owenversteeg/min use that crappy JS stuff :-( 18:45:45 <ChrisWarrick> gour: What else should they be using instead? And you generally don’t need to know JS to use any of it 18:46:15 <gour> ChrisWarrick: well, e.g. plain libsass 18:46:38 <KwBot> [nikola] ralsina closed issue #2896: Support hiding post-list in teaser https://github.com/getnikola/nikola/issues/2896 18:46:50 <ChrisWarrick> gour: That needs writing at least a Makefile 18:47:04 <ChrisWarrick> gour: that doesn’t integrate itself with webpack or whatever the cool tool is today 18:48:53 <gour> ChrisWarrick: i agree that today's front-end dev is simply screXed