4 Commits (a5786bb9cf45fd55de191bedbae79f3766973fdf)

Author	SHA1	Message	Date
Jack Baldry	c1c48dd610	Use relative aliases for all non-current Grafana aliases (#60062) ... * Use relative aliases for all non-current Grafana aliases Prevents non-latest documentation "stealing" the page away from latest and through permanent redirects for latest pages that no longer exist. The redirected pages are indexed by search engines but our robots.txt forbids them crawling the non-latest page. Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Remove aliases from shared pages Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Rewrite all current latest aliases to be next Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Fix typo in latest alias Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Remove all current page aliases find docs/sources -type f -name '*.md' -exec sed -z -i 's#\n *- /docs/grafana/next/[^\n]*\n#\n#' {} \; find docs/sources -type f -name '*.md' -exec sed -Ez -i 's#\n((aliases:\n *-)|aliases:\n)#\n\2#' {} \; Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Prettier Signed-off-by: Jack Baldry <jack.baldry@grafana.com> Signed-off-by: Jack Baldry <jack.baldry@grafana.com>	3 years ago
Jack Baldry	b9d8bcb59b	Use relref resolved from nearest section (#58718) ... As image-rendering is a branch bundle, it is considered a section by Hugo and relrefs should be resolved from there even for child pages. The behavior that worked in `next` but not `latest` could be explained by the lenient but potentially ambiguous relref resolution algorithm Hugo uses. However, I have not determined the exact difference between the two sets of content that causes `next` to work but `latest` not to. Signed-off-by: Jack Baldry <jack.baldry@grafana.com> Signed-off-by: Jack Baldry <jack.baldry@grafana.com>	3 years ago
Christopher Moyer	a9458c8c00	Docs: corrects relrefs (#58706) ... corrects relrefs	3 years ago
Christopher Moyer	cafdbc1644	restructures directories, corrects relrefs (#57130)	3 years ago