Customizing template.html

[racerxdl]

The issue #355 was closed by the bot. But it is useful to customize the template.html.

[pudiva]

bump. I'd really like to customise some logic there:

• add support for og:video
• automatically generate image and video urls based on id stored on front-matter
• reuse social links that are stored in another config key

[pudiva]

my hope is that such feature would get into gh-pages, for maximum laziness convenience

[davorpa]

I think that generator meta tag should be optional (or at least doesn't show version).

It's well-known to be used to know if site has any vulnerability.

The less information is given about frameworks, application servers, libraries ... the better.

[racerxdl]

Not that it makes much difference for static pages @davorpa , but you're right.

[mattr-]

I appreciate y'all keeping this issue alive for two years while somebody eventually comes and looks at it. I'm not closing this issue out of spite, but rather because customizing the template itself is not the right avenue to support the functionality requests y'all have made and I'd rather see more concrete feature requests to pursue what you're after.

I'll follow up in about a week and if nobody's made the issues, I'll create them myself. At least then there will be placeholders for the requests rather than them getting lost. (And when necessary, the whole jekyllbot stale dance can be done on those too. 😄 )

add support for og:video

This feels like a separate feature request that the plugin should support out of the box if the appropriate config keys are present, similar to how we handle images. I wouldn't support the ability to customize template.html for this use case. I'd be happy to add support for og:video to the plugin itself though.

I think that generator meta tag should be optional (or at least doesn't show version).

Covered by #404

automatically generate image and video urls based on id stored on front-matter

This also sounds like a separate feature request, and I'd support seeing a separate issue with more information about what you're after in that regard. I don't currently see how this sort of customization would be useful.

reuse social links that are stored in another config key

I don't see a reason to provide support for customizing template.html for this either. Plugins need to be isolated and stand alone. Duplication is annoying, yes, but having a concrete well defined way of knowing how things get mapped from config into the tag is better than removing duplication in this case, IMO.