JSON:API spec experiment #145
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for openpodcastapi ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Use banners instead of asides
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
🚨 EXPERIMENT ONLY 🚨
This PR is just a brain dump of some things I've been thinking about regarding a structured and linked approach to designing the API. Nothing in this PR is agreed-upon with the team. This PR exists only to generate a preview link.
Overview
This PR is the culmination of many different thoughts I've had about the Open Podcast API, its future, and how we can try to unstick the project. It takes the existing ideas already present and rearranges them in the following ways:
Starlight changes
This PR also brings some changes to clean up the appearance of Starlight. This is just an experiment to see how well this would work for our use case. These changes can easily be ported.