Hi.

I'm currently working on genericizing your homepage using Mustache templates.

I work on Linux and have a problem with CRLF line endings here - would you mind changing line endings of all test files to LF?

AFAIK git has a neat way to handle LF in repo and CRLF in checkout - core.autocrlf = true option or .gitattributes file. Unfortunately, it is difficult the other way.

Hi, it's me again ^ ^.

I think it would be nice to make this homepage generic, so that anyone could make own version by modifying something more friendly than separate HTML, CSS and some JS.

I was thinking about two approaches: templating or dynamically generating the page in JS.
a) Templating - generating files from Mustache (or other) templates and user-supplied config in YAML/JSON.
A proof-of-concept is on my fork - https://github.com/Xender/homepage/tree/OLD/static-templating.
While not requiring big modifications to files, it requires user to re-run generation script each time config is modified (please see new section in README).
Also, this is only a proof-of-concept, so if you were to approve it, please don't merge it into your tree by now.
b) Dynamic generation - something like what https://github.com/mukyu/NeaterPage has - config.js file & adding elements to DOM in runtime.
I think this is nicer, because doesn't require user to "recompile" page. But it would require some code rewriting.

I also plan on making script which would automatically download sites' favicons (and optionally turn them gray using ImageMagick). I don't see a way to do that dynamically, so it would also require recompiling.

Also introduction of light theme doubled most of the files. I think it would be nice to also genericize styles, so users could painlessly change colors and mascots.

Considering all of the above, please let me know, what do you think about genericing the homepage and whether the templated or dynamic would be better.

Thanks for reading such a long comment ^ ^.

EDIT: updated branch name from /templating/ to /static-templating-OLD/