Create “things you can do with template changes” documentation

[da2x]

AUTHOR_PORTRAITS = { "john": { "100x100": "/images/pretty_john.jpeg", }, }

[davidak]

👍 + default to gravatar

[da2x]

Gravatar has privacy implications … .

[davidak]

ok, yes. your e-mail address get's sent to them. you may don't want that.

so by default empty. option 'gravatar' to use the authors e-mail

[tritium21]

This is a place where you can easily make the source of the images plugable. The default should be to use the standard image locations, but allow a plugin to define a location (or you define a location for the plugin), and simply build a command plugin, or signal handler to go out to the source and fetch the images.

Baking gravatar into nikola bugs me in the same way comments are currently baked in; once its done, it makes it hard for someone else to come along with a plugin to override whats there, or provide another source.

[ralsina]

So... does it make sense to implement this in core?

It seems it would be, like described above, just a matter of changing templates, since there is nothing preventing anyone from adding things in GLOBAL_CONTEXT anyway.

[tritium21]

I think, perhaps, this is a great time to bring up an idea I had all of 3 seconds ago... We should have a cookbook of template hacks in the docs. There are so many changes that I have seen suggested here and on irc (and to a lesser extent, the mailing list) that are trivial-to-straight-forward template changes. This falls into that category. Perhaps we don't bake them into core... perhaps we just... show people how easy it is to DIY.

[Kwpolska]

@tritium21 Great idea. I renamed this issue so this isn’t lost.

[ralsina]

@tritium21 Great idea! A cookbook would be great.