Fix: addressing changes from @tupui

Author: lwasser

.github/workflows/build-book.yml

@@ -67,7 +67,7 @@ jobs:
       with:
         directory: '_build/html'
         arguments: |
-          --ignore-files "/.+\/_static\/.+/,/genindex.html/ "
-          --ignore-status-codes "403, 503"
+          --ignore-files "/.+\/_static\/.+/,/genindex.html/"
+          --ignore-status-codes "404, 403, 503"
 
     

documentation/contributing-license-coc.md

@@ -34,6 +34,9 @@ technically proficient users how to:
 * Run the test suite 
 * Build documentation locally
 
+The development guide should also have guidelines for:
+* code standards including docstring style, code format and any specific code approaches that the package follows. 
+
 It's also helpful to specify the types of tests you request if a contributor submits a new feature or a change to an existing feature that will not be covered by your existing test suite. 
 
 If you have time to document it, it's also helpful to document your maintainer workflow and release processes. 

documentation/package-documentation-best-practices.md

@@ -5,9 +5,9 @@
 
 Your package: 
 * Should have a documentation website 
-* All of its functions and classes (the API) documented
-* Your package should use numpy-style docstrings 
-* Your documentation landing page should direct users to 4 core sections: get started, documentation content, about and community.
+* Should have all of its public (user-facing) functions and classes (the API) documented
+* Should use numpy-style docstrings 
+* Documentation landing page should direct users to 4 core sections: get started, documentation content, about and community.
 * Documentation should include short quick-start tutorials
 ```