Repository navigation
Add learning resource on public pages and private API boundaries - #1170
Open
cnvxstudio wants to merge 1 commit into
Open
cnvxstudio wants to merge 1 commit into
cnvxstudio wants to merge 1 commit into
Conversation
Add one article link using the documented resources frontmatter. The note explains generated markup, hybrid routing, authentication, ownership and request-versus-confirmation semantics.
✅ Deploy Preview for jamstack-site ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
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.
Adds one article to the learning resources collection: A Jamstack boundary to keep: public pages are not private API responses.
The note explains how generated HTML, hybrid delivery, caching, server-side authorization and account ownership fit together. It also uses appointment requests to illustrate why an API's persisted state should match the outcome described in the interface.
Disclosure: I work with the Frontel team, whose implementation provides the concrete example. The article contains an original explanation and response inventory, with no customer information, credentials or private source code.
Validation: checked the resource frontmatter against the README reference and reviewed the rendered article and its source-supported statements. The diff adds one seven-line Markdown resource file; a local site build was not run.