Minified templates are not a good basis for customization

What’s the recommended path for customizing base.html, main.html, and the partials?

Prior to 4.3.0, I would grab any file I needed to customize from the material/ directory and include it in my build. Now, however, those are minimized. While that does save in bandwidth, it also makes them a challenge to work with when customizing. (Perhaps I’m missing the obvious, but I’m not finding any cli tools that will pretty-print a jinja2 template.)

Using the files in src works for many. However, at least base.html has some templating that causes it to differ from the final output file. Assuming you don’t have in interest in reverting the behavior to what it was prior to 4.3.0, would it be possible to have non-minimized html files output to an additional/alternate directory?

[squidfunk]

@wilhelmer - thanks, I just removed minify_js from the docs in 13c8ad337000a4d0dc4926acff04637c5e8692b5.

[wilhelmer]

@squidfunk Co-author of the plugin here. Setting minify_js to true doesn’t do anything unless you specify the files to be minified under js_files. So I suggest that you either remove the minify_js entry in the documentation or specify some template files that should be minified.

Currently, the documentation gives the impression that the plugin will automatically minify all your JS files, which it doesn’t.