# Documentation for older versions

**URL:** <https://discourse.gohugo.io/t/documentation-for-older-versions/47208>\
**Category:** support\
**Created:** [November 22, 2023, 4:34pm UTC](https://discourse.gohugo.io/t/documentation-for-older-versions/47208 "2023-11-22T16:34:15Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![anmith](https://avatars.discourse-cdn.com/v4/letter/a/b5a626/32.png) [@anmith](https://discourse.gohugo.io/u/anmith)\
**Post date:** [November 22, 2023, 4:34pm UTC](https://discourse.gohugo.io/t/documentation-for-older-versions/47208/1 "2023-11-22T16:34:15Z")

</div>

Hi,

from time to time I struggle when using the official hugo documentation with hugo v0.104.3 which I’m still using.

The official documentation reflects the current hugo version and all its available commands which might not be available in an older version.

Two ideas come to mind:

- Keeping the documentation for older versions unchanged and offer an option to select the version and view the corresponding documentation
- Add a marker like “requires vxxx” to new stuff so it’s visible it won’t work with older releases

Am I the only one who would find something like the suggestions mentioned above helpful?

---

<div class="post-metadata">

**Author:** ![McShelby](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/mcshelby/32/15112_2.png) [@McShelby](https://discourse.gohugo.io/u/McShelby)\
**Post date:** [November 22, 2023, 5:29pm UTC](https://discourse.gohugo.io/t/documentation-for-older-versions/47208/2 "2023-11-22T17:29:26Z")

</div>

> [@Documentation for deprecated functions, methods, etc](https://discourse.gohugo.io/t/documentation-for-deprecated-functions-methods-etc/46919):
>
> I’d like to bring up some concerns about the documentation for deprecated functions, methods etc. I observed that whenever a feature/method is deprecated, it’s removed from the documentation. This can be a problem for some people. For example, .Site.IsServer is deprecated in Hugo v0.120.0. What if someone not using v0.120.0, needs to know about .Site.IsServer ? Instead of removing .Site.IsServer from documentation, would it be possible to relocate it to a dedicated page, perhaps docs/content/…

---

<div class="post-metadata">

**Author:** ![frjo](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/frjo/32/18626_2.png) [@frjo](https://discourse.gohugo.io/u/frjo)\
**Post date:** [November 22, 2023, 6:54pm UTC](https://discourse.gohugo.io/t/documentation-for-older-versions/47208/3 "2023-11-22T18:54:43Z")

</div>

The documentation uses “New in x.x”, like e.g. on:

> **[Markdown render hooks](https://gohugo.io/templates/render-hooks/)**
>
> Render Hooks allow custom templates to override markdown rendering functionality.

---

<div class="post-metadata">

**Author:** ![anmith](https://avatars.discourse-cdn.com/v4/letter/a/b5a626/32.png) [@anmith](https://discourse.gohugo.io/u/anmith)\
**Post date:** [November 22, 2023, 9:37pm UTC](https://discourse.gohugo.io/t/documentation-for-older-versions/47208/4 "2023-11-22T21:37:48Z")

</div>

Hi,  
not in all places. Last thing I struggled with was math.Abs and the [documentation](https://gohugo.io/functions/math/abs/) doesn’t show any information about the required version.

---

<div class="post-metadata">

**Author:** ![jmooring](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/jmooring/32/4214_2.png) [@jmooring](https://discourse.gohugo.io/u/jmooring)\
**Post date:** [November 22, 2023, 10:21pm UTC](https://discourse.gohugo.io/t/documentation-for-older-versions/47208/5 "2023-11-22T22:21:33Z")

</div>

I’ve gone back 18 months to v0.100.0, and have added “new in” labels to methods and functions added since that time. See [https://github.com/gohugoio/hugoDocs/pull/2339](https://github.com/gohugoio/hugoDocs/pull/2339).

We’re not going to version the documentation any time soon, nor will we retain “new in” labels forever. No one wants or needs to see a “New In v0.54.0” label.

Perhaps I’m too aggressive, but to me something that was new 12 months ago isn’t new anymore, and I think the label should be removed.

* * *

Going forward, a “new in” label will be hidden if the specified version is older than a predefined threshold, based on differences in major and minor versions. This is similar to Hugo’s [deprecation logic](https://gohugo.io/troubleshooting/deprecation/). See&nbsp;[details](https://github.com/gohugoio/hugoDocs/blob/master/layouts/shortcodes/new-in.html).

---

<div class="post-metadata">

**Author:** ![anmith](https://avatars.discourse-cdn.com/v4/letter/a/b5a626/32.png) [@anmith](https://discourse.gohugo.io/u/anmith)\
**Post date:** [November 23, 2023, 4:27pm UTC](https://discourse.gohugo.io/t/documentation-for-older-versions/47208/6 "2023-11-23T16:27:20Z")

</div>

Hi - first of all, thanks for your work, much appreciated.

For my personal workflow, I adopted the Debian stable timeline, which offers an updated platform to work on every two years and keeps versions locked until the next update. This suits my needs better than a rolling release platform which might (and does according to my experiences) break the workflow way too often for me.

Debian 10 was released with Hugo v0.55, Debian 11 with Hugo v0.80 and Debian 12 with Hugo v0.111 - so if I understand the minorVersionDiffThreshold of correctly, 30 should be a good value to work with! 🙂