diff options
| author | bjnath <github@bigriver.xyz> | 2020-06-06 11:02:14 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-06-06 17:02:14 +0200 |
| commit | 9439b56f8762b8c9b48d2f9e54dfb467aaa2b3f9 (patch) | |
| tree | 2f373d4995ffec329f758c04e29447c456b02edb /doc/source/dev/howto-docs.rst | |
| parent | f1671076c80bd972421751f2d48186ee9ac808aa (diff) | |
| download | numpy-9439b56f8762b8c9b48d2f9e54dfb467aaa2b3f9.tar.gz | |
DOC: Fixes for 18 broken links (#16472)
* DOC: Fixes for 18 broken links
This, with PR #16465, should fix nearly all the remaining broken links
on the site. 4 or 5 others should be easy to fix and just
need attention from someone more knowledgeable -- will
open an issue. For release notes with dead links,
I could usually find links on archive.org for roughly contemporary
versions.
* DOC: Update to "Fixes for 18 broken links #16472"
* Obsolete links, previously commented out, now deleted:
https://github.com/numpy/numpy/pull/16472#discussion_r433928958
* Semantic markup for reference to Python class:
https://github.com/numpy/numpy/pull/16472#discussion_r433553928
* Missing :ref: in internal link:
https://github.com/numpy/numpy/pull/16472#discussion_r433554484
Not included: Resolution on using external/internal doc link in .py:
https://github.com/numpy/numpy/pull/16472#discussion_r433554824
* DOC: Add internal link for 'Fixes for 18 broken links' PR #16472
Making reference [1] an internal link in function_base.py => numpy.vectorize.html
* DOC: Redirect 2 link fixes in PR #16472
* governance.rst link reverted
* ununcs.rst `overridden` link goes where it was meant to
per https://github.com/numpy/numpy/pull/16472#pullrequestreview-424666070
Diffstat (limited to 'doc/source/dev/howto-docs.rst')
| -rw-r--r-- | doc/source/dev/howto-docs.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/source/dev/howto-docs.rst b/doc/source/dev/howto-docs.rst index 0e2e03e0b..281f87cfb 100644 --- a/doc/source/dev/howto-docs.rst +++ b/doc/source/dev/howto-docs.rst @@ -87,7 +87,7 @@ check out the following specific guides: Major additions to the documentation (e.g. new tutorials) should be proposed to the `mailing list <https://mail.python.org/mailman/listinfo/numpy-discussion>`__. - + Other ways to contribute ------------------------ @@ -145,5 +145,5 @@ the quality of the documentation. resources for technical writing. - Google offers two free `Technical Writing Courses <https://developers.google.com/tech-writing>`__ -- `Software Carpentry <https://software-carpentry.org/software>`__ has a lot of +- `Software Carpentry <https://carpentries.github.io/curriculum-development/>`__ has a lot of nice recommendations for creating educational material. |