I see some potential issue with the deprecactions, especially .Site.BuildDrafts and maybe .Site.Languages, since I can’t see the direct replacements in the table provided by @jmooring
The most obvious is certainly .Site.BuildDrafts - this is not a “odd construct” at all, since there are use cases where the relevant entity in content modeling is not a individual page. One of those are draft menu entries as discussed in:
- Draft menu entries with @irkode (and as a follow up: Menus in Hugo draft mode · Christian Mahnke)
So, if this shouldn’t be kept, a (less optimal) migration strategy might be something like a environment (-e).
Basically the same point (regarding to the entity in the content model) applies to the language (Site.Languages). I haven’t looked into this that deep but if I unterstand it correctly, the table and example above implies that if a page isn’t translated I can’t access the other languages the site is available in? This can’t be true, right?
Just in case it is: Of course I need to have a language switch, even if no translation (let’s say for a deep linked page in German), I need to have a link to a English and Swedish translation of the Site, they just need to either link to the start or a page that explains that the page is not available as a translation.
So having Site.Languages can be helpful, especially when having a list based on the current page is incomplete.