[WIP] Jupyter book v2

[martin-springer]

Describe your changes

Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.

Issue ticket number and link

Fixes # (issue)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist before requesting a review

• I have performed a self-review of my code
• Code changes are covered by tests.
• Code changes have been evaluated for compatibility/integration with Scenario analysis (for future PRs)
• Code changes have been evaluated for compatibility/integration with geospatial autotemplating (for future PRs)
• New functions added to init.py
• API.rst is up to date, along with other sphinx docs pages
• Example notebooks are rerun and differences in results scrutinized
• What's new changelog has been updated in the docs

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 74.67%. Comparing base (51172fd) to head (7c02b9a).
⚠️ Report is 341 commits behind head on development.

Additional details and impacted files

@@               Coverage Diff               @@
##           development     #303      +/-   ##
===============================================
+ Coverage        71.66%   74.67%   +3.01%     
===============================================
  Files               40       41       +1     
  Lines             4524     4813     +289     
===============================================
+ Hits              3242     3594     +352     
+ Misses            1282     1219      -63     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.