Best solution in terms of complexity

nfriedli · January 19, 2024, 11:17am

All the title tags on my site take the form: page title - site title.
Except on the home page, where the title tag is: site title - headline.

Everything works fine on my site, but that’s just technical curiosity.

I write in pseudo code.

if isHome solution:

In baseof.html, I have such a title tag:

if isHome
    siteTitle - headline
else
    pageTitle - siteTitle

In this way, the condition is executed on all pages of the site without exception.

block solution:

In baseof.html, I have such a title tag:

define blockTitle
    pageTitle - siteTitle

And in my home.html:

define blockTitle
    siteTitle - headline

Here, the default block is selected, except on the home page, where it is redefined.

questions:

Is one of the solutions better in terms of performance, computing cost or maintenance?
Or another solution I haven’t thought of?

bep · January 19, 2024, 3:09pm

It should be neglibable, but if I would guess, I would say that the define blockTitle would be slightly faster.

The only one may be my hackish thougts about passing data up to the base templates in:

github.com/gohugoio/hugo

A way for a template (e.g. single.html) to signal a flow in the base template

opened 10:55AM - 26 May 23 UTC

bep

Proposal

The files in the PR in #11024 is a technical way of implementing this in the tem…plates today (we could consider adding some built-ins for this if needed). Those file don't demonstrate "how useful" this is, but I will talk a little about that below. ``` -- hugo.toml -- -- content/_index.md -- -- content/p1.md -- -- layouts/_default/baseof.html -- {{ block "_baseof_start" . }}{{ end }} <html> <head> {{/* Lots of imports of SEO partials, stylesheets, JS and whatnot. */}} </head> <body> {{ $flow := .Store.Get "_baseof_flow" | default "default" }} {{ if eq $flow "default" }} <div> <h1>Default flow</h1> {{ block "main" . }}{{ end }} </div> {{ else if eq $flow "foo" }} <div> <h1>Foo flow</h1> {{ block "main" . }}{{ end }} </div> {{ else if eq $flow "bar" }} <div> <h1>Bar flow</h1> {{ block "main" . }}{{ end }} </div> {{ end }} </body> </html> -- layouts/index.html -- {{ define "_baseof_start" }}{{ .Page.Store.Set "_baseof_flow" "foo" }}{{ end }} {{ define "main" }}Main Home{{ end }} -- layouts/_default/single.html -- {{ define "_baseof_start" }}{{ .Page.Store.Set "_baseof_flow" "bar" }}{{ end }} {{ define "main" }}Main Single{{ end }} ``` In many sites, even bigger ones, you end up _wanting_ to have only one `baseof.html` template. You can of course create several templates and avoid some DRYness by adding the common pieces via partials, but it can still be a hassle if only small parts of your base template changes. The tooling you have for this today are: * `block` definitions in the base template that can be _implemented_ with `define` in e.g. `single.html`. * `partial` or `template` invocations from the base template. But there are often subtle structural difference in the different layouts (e.g. grid layouts, table of contents), which leads to either * Conditional on the form `{{ if .IsPage }}Insert table of contents{{ end }}` * A duplication of lots of markup in layouts. The above construct may help simplify things, and it could also be a way to pass data up to the base template.

Topic		Replies	Views
Trying to define a page support	1	545	December 9, 2017
None of my pages have titles support	4	123	February 26, 2024
Reusable template code for page <head> tags (<title> and other) support	3	355	May 5, 2021
Cascading template blocks feature	2	766	December 7, 2017
Change taxonomy list page html title? support taxonomy	3	1501	January 6, 2021

Best solution in terms of complexity

Related Topics