Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix docs.nativelink.com based URL not working #1385

Open
aleksdmladenovic opened this issue Oct 3, 2024 · 1 comment · May be fixed by #1386
Open

Fix docs.nativelink.com based URL not working #1385

aleksdmladenovic opened this issue Oct 3, 2024 · 1 comment · May be fixed by #1386

Comments

@aleksdmladenovic
Copy link
Contributor

Currently, it seems like every sub URLs of https://docs.nativelink.com is always redirected to https://www.nativelink.com/docs/introduction/setup after we deployed our documentation code to NativeLink Web Platform.

For instance, in README.md, we have this link - https://docs.nativelink.com/contribute/nix for Nix development guide.
But it redirects to https://www.nativelink.com/docs/introduction/setup, now.

Correct URL should be https://nativelink.com/docs/contribute/nix, currently.

The setups below are **production-grade** installations. See the [contribution docs](https://docs.nativelink.com/contribute/nix/) for instructions on how to build from source with [Bazel](https://docs.nativelink.com/contribute/bazel/), [Cargo](https://docs.nativelink.com/contribute/cargo/), and [Nix](https://docs.nativelink.com/contribute/nix/).

All docs.nativelink.com based URL needs to be fixed by replacing that with nativelink.com/docs.

@aleksdmladenovic aleksdmladenovic linked a pull request Oct 3, 2024 that will close this issue
6 tasks
@aleksdmladenovic
Copy link
Contributor Author

I hope you to check this issue and my PR. Thanks.

cc: @allada, @MarcusSorealheis, @blakehatch, @SchahinRohani

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant