Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR implements two documentation build/deployments and updates the corresponding links in the readme and top page of the docs.
The two builds are:
stable: deployed at dascore.org and built whenever a new release is made from github (which triggers PyPI/conda releases).
development: deployed at dascore.quarto.pub/dascore and built whenever commits are merged into master.
The problem this solves:
New users install dascore with pip/conda. Then they look at dascore.org, but the code there might not work since currently it is for the master branch (which might be quite different from the previous release). Essentially, this PR should make for a better (less confusing) onboarding experience for new users while still giving us a chance to see up-to-date development (from master branch) docs.
The hosting site for the development docs is (quarto-pub)[https://quartopub.com/], a free site for hosting quarto projects up to 100mb. Dascore's docs are currently ~40mb.
closes #160
Checklist
I have (if applicable):