Repository navigation
docs: add commercial workflow and agency lip-sync guides - #582
Merged
Merged
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
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.
Buyers and developers choosing a workflow need to know whether to start with a product photo, existing speaker footage or a still portrait. Add a commercial workflow chooser and an agency lip-sync pilot, linked from the integration navigation, existing evaluation guide and lip-sync guide. Reuse the SDK/Colab recipes and evaluation scorecard, with current commercial-use terms and explicit web/API/MCP catalog differences.
Proof:
yarn checkreports no broken links, touched files pass Prettier, and both new pages render in the Mintlify preview at desktop and mobile widths without page overflow. Referenced public product/API resources returned HTTP 200. No measured provider superiority or new benchmark result is claimed.Merge Danger
Door: two-way. Revert the documentation and navigation changes; no application or billing behavior changes.
Blast Radius: Docs readers and documentation-search clients. Incorrect workflow guidance could misdirect an integration; links reuse existing API references and UGC is explicitly labeled as having no dedicated current API endpoint.