Rewrite extension docs for the web ecosystem#43
Open
Conversation
Replace outdated extension docs with comprehensive documentation for the TLSNotary web ecosystem: browser extension overview, plugin system (architecture, capabilities API, handler reference), and verifier server (deployment, API endpoints, webhooks). Remove the old provider API page.
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
2 participants
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.
Summary
docs/extension/README.mdas an overview of the TLSNotary web ecosystem (extension, plugins, verifier), with installation instructions and links to the demo site and interactive tutorialdocs/extension/plugins.mdwith full plugin system documentation: architecture, lifecycle, capabilities API (DOM, hooks,prove(), handlers), a complete X-Profile example, security model, and development guidedocs/extension/verifier.mdcovering the verifier server: architecture, built-in proxy, API endpoints, session flow, webhook system, deployment (Docker, nginx), and configurationdocs/extension/provider.mdTest plan
npm run build)