Fix various links

This merge also makes warnings report as errors when building
the docs and removes references to the autogenerated API.

Two unused pages have been removed.

Author: xylar

docs/Makefile

@@ -11,7 +11,7 @@ BUILDDIR      = _build
 # Build into a versioned subdirectory
 versioned-html:
 	@echo "Building version: $(DOCS_VERSION)"
-	$(SPHINXBUILD) -b html "$(SOURCEDIR)" "$(BUILDDIR)/html/$(DOCS_VERSION)"
+	$(SPHINXBUILD) -b html -nW --keep-going "$(SOURCEDIR)" "$(BUILDDIR)/html/$(DOCS_VERSION)"
 	@echo "Build finished. The HTML pages are in $(BUILDDIR)/html/$(DOCS_VERSION)."
 	@echo "Setting up shared version switcher for local preview..."
 	mkdir -p _build/html/shared

docs/conf.py

@@ -42,8 +42,6 @@
     "sphinx.ext.napoleon",
 ]
 
-autosummary_generate = ['developers_guide/api.md']
-
 # Otherwise, the Return parameter list looks different from the Parameters list
 napoleon_use_rtype = False
 # Otherwise, the Attributes parameter list looks different from the Parameters

docs/index.md

@@ -5,8 +5,23 @@
 introduction
 quickstart
 using-tools
-testing-release-candidates
+
 releasing/release-workflow
+releasing/conda-vs-spack
+releasing/planning-updates
+releasing/creating-rcs/overview
+releasing/creating-rcs/rc-dependencies
+releasing/creating-rcs/rc-e3sm-unified
+releasing/creating-rcs/rc-troubleshooting
+releasing/testing/overview
+releasing/testing/spack-updates
+releasing/testing/mache-updates
+releasing/testing/deploying-on-hpcs
+releasing/testing/troubleshooting-deploy
+releasing/adding-new-machines
+releasing/finalizing-release
+releasing/maintaining-past-versions
+
 packages
 troubleshooting
 contributing

docs/releasing/adding-new-machines.md

@@ -44,15 +44,15 @@ After updating `mache`, you'll need to:
 2. **Update Spack if needed**
 
    * If new versions of external tools are required, update the
-     [`spack_for_mache_<version>`](spack-updates.md) branch of the
+     [`spack_for_mache_<version>`](testing/spack-updates.md) branch of the
      [E3SM Spack fork](https://github.com/E3SM-Project/spack)
 
 ---
 
 ## ✅ Testing Your Changes
 
 Use the standard test deployment approach from
-[Deploying on HPCs](deploying-on-hpcs.md):
+[Deploying on HPCs](testing/deploying-on-hpcs.md):
 
 ```bash
 cd e3sm_supported_machines
@@ -88,4 +88,4 @@ During testing, focus on:
 
 ---
 
-➡ Next: [Publishing the Final Release](publishing-final-release.md)
+➡ Next: [Publishing the Final Release](finalizing-release.md)

docs/releasing/maintaining-past-versions.md

@@ -95,4 +95,4 @@ because of this.
 
 ---
 
-Back to: [Publishing the Final Release](publishing-final-release.md)
+Back to: [Publishing the Final Release](finalizing-release.md)

docs/releasing/planning-updates.md

@@ -69,7 +69,7 @@ The final list of packages is curated by the Infrastructure Team based on:
 * Community need and usage patterns
 
 Once the list is mostly settled, the team begins creating release candidates
-using the [Creating Release Candidates](creating-rcs.md) workflow.
+using the [Creating Release Candidates](creating-rcs/overview.md) workflow.
 
 ---