Repository navigation
Docs: state web app fit and durability in the FAQ and llms.txt - #6153
Draft
cloutiertyler wants to merge 1 commit into
Draft
cloutiertyler wants to merge 1 commit into
cloutiertyler wants to merge 1 commit into
Conversation
Add a direct FAQ answer that SpacetimeDB is a good fit for web apps, describe confirmed reads in the persistence answer, and add the same facts to the llms.txt intro that AI assistants read first.
cloutiertyler
force-pushed
the
docs/llms-faq-web-apps-durability
branch
from
October 12, 2026 20:48
271ef01 to
adb7ec2
Compare
This branch has not been deployed
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
1 participant
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 of Changes
This PR updates the FAQ and the llms.txt intro to say plainly that SpacetimeDB is well suited to web apps and to describe its durability model, matching #6152.
API and ABI breaking changes
n/a
Rollback safety impact
n/a
Expected complexity level and risk
1
Testing