# Usability request re: Outdated documentation

**URL:** <https://community.grafana.com/t/usability-request-re-outdated-documentation/77808>\
**Category:** Site Feedback\
**Created:** [December 11, 2022, 2:26am UTC](https://community.grafana.com/t/usability-request-re-outdated-documentation/77808 "2022-12-11T02:26:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![elasticdotventures](https://avatars.discourse-cdn.com/v4/letter/e/439d5e/32.png) [@elasticdotventures](https://community.grafana.com/u/elasticdotventures)\
**Post date:** [December 11, 2022, 2:26am UTC](https://community.grafana.com/t/usability-request-re-outdated-documentation/77808/1 "2022-12-11T02:26:23Z")

</div>

Sorry - as a new user, I need to munge some of these links, since I am limited to two:

If I go to an older version of Grafana docs such as:

> **[Prometheus data source | Grafana documentation](https://grafana.com/docs/grafana/v9.2/datasources/prometheus/)**
>
> Guide for using Prometheus in Grafana

The link to view the latest version is “lazy”, it simply links to:  
/docs/Grafana/latest

It would be much more functional if it linked to:

> **[Prometheus data source | Grafana documentation](https://grafana.com/docs/grafana/latest/datasources/prometheus/)**
>
> Guide for using Prometheus in Grafana

Even if pages have changed, 99% of pages aren’t going to change between releases, and it’s stupid to have users reading old docs, but also google doesn’t index new versions of docs immediately - so this would be a good compromise.

---

<div class="post-metadata">

**Author:** ![fionaartiaga](https://avatars.discourse-cdn.com/v4/letter/f/9de0a6/32.png) [@fionaartiaga](https://community.grafana.com/u/fionaartiaga)\
**Post date:** [December 13, 2022, 5:14pm UTC](https://community.grafana.com/t/usability-request-re-outdated-documentation/77808/2 "2022-12-13T17:14:47Z")

</div>

Thanks so much for reaching out. The docs don’t directly map back to to the same topic for all of our content as we move forward with releases, so it’s not possible for us to direct readers of old docs 1:1 to a new version of the content.

However, this isn’t a great experience for our users, so we’ll look at how we can improve this moving forward.