Branch: refs/heads/main
Revision: faabec830138d06f52723e7fa0f57b9d0dc7e1bb
Author: bradcray
Link: Update docs to point to new webpages rather than old by bradcray · Pull Request #26632 · chapel-lang/chapel · GitHub
Log Message:
Update docs to point to new webpages rather than old (#26632)
[reviewed by @brandon-neth ]
This updates URLs within our docs to point to the new website rather
than the URLs from the old website. I believe most of these cases would
automatically redirect to the new website, but the more we establish the
new URLs as the canonical versions, the happier our Google search
dashboard will be.
The one change here that's a little borderline is
Reporting Chapel Issues — Chapel Documentation 2.3 which has been a (client-side)
redirect for ages, though what it redirects to isn't the greatest of
pages (a docs page that basically says "file a github issue." Here, I've
updated one such instance to avoid the redirect, but there are lots of
others that I skipped over, feeling like we should probably establish a
better bugs page in general. I've opened an issue on the chapel-www
repository to determine what we should do here.
Diff:
M README.rst
M doc/rst/developer/bestPractices/GettingStarted.rst
M doc/rst/language/evolution.rst
M doc/rst/platforms/aws.rst
M doc/rst/users-guide/base/hello.rst
M doc/rst/usingchapel/QUICKSTART.rst
M util/build_configs/cray-internal/generate-dev-releaseinfo.bash
https://github.com/chapel-lang/chapel/pull/26632.diff