I was Googling for something and landed on `<https docs lake lakeFS #dev

I was Googling for something and landed on `<https...

Robin Moffatt

03/14/2023, 6:37 PM

I was Googling for something and landed on

<https://docs.lakefs.io/setup/>

which seems to be a stale page based on the current nav that you see at docs.lakeFS.io root. a) Should I add a

redirect_from

deploy/index.md

to catch this and subpages on

/setup

? b) Should we be deleting stale pages from our docs site so that users get a 404 (and Google un-indexes them) than having this situation where nothing's "broken" but users see stale pages and a confusing nav that changes depending on which page you're on. (am I right to think it's GitHub Pages hosted with this as the relevant page in this case? https://github.com/treeverse/docs-lakeFS/tree/main/setup)

Yoni Augarten

03/14/2023, 8:34 PM

It's a bug on our doc deployment actually - when we delete a page, it's not really deleted from https://github.com/treeverse/docs-lakeFS. So redirects will not catch it, because this page technically does exist. For now I will delete it from the repo and let's see what happens.

Yoni Augarten

03/14/2023, 8:38 PM

Generally, we should delete these pages and replace them with redirects to other pages that are relevant, so existing links are not broken.

Yoni Augarten

03/14/2023, 8:40 PM

Update: so after deleting the page, I get a 404. We can leave it like this and let Google un-index it, or add the redirect as you suggested. If you choose the redirect, ideally it should catch any URL under the "/setup" path, e.g. "setup/create_repo.html".

Robin Moffatt

03/14/2023, 8:43 PM

thanks @Yoni Augarten

Robin Moffatt

03/14/2023, 8:44 PM

tomorrow I'll maybe do a diff between a fresh build and the current docs deployment repo and see if there's much else to flush out

👌🏻 1

Robin Moffatt

03/14/2023, 8:46 PM

https://github.com/treeverse/lakeFS/issues/5484 to track

3 Views

Open in Slack

Previous Next