Oleg Isonen
1b48716ff4
## Summary - Document how people create, connect, edit, validate, and publish MDX-backed Content Blocks. - Document the complete MCP workflow, including scoped expression sources, frontmatter updates, diagnostics, conflicts, and disconnect behavior. - Add two focused screenshots for the human workflow. - Fix issues found by a low-reasoning MCP agent while executing every documented workflow. Ref #6182 ## Implementation notes - Connection confirmation uses the public `confirmReplacement` field because `confirm` is reserved as a hidden transport field. - MCP edits frontmatter with `update-content-block-frontmatter`; materialized MDX elements are not persistent targets for generic instance mutation tools. - Reload now intentionally discards a conflicted local source and accepts the Asset's latest storage revision before an edit is reapplied. - Generated MCP documentation and runtime contracts are updated from their source files. ## Checklist - [x] Document the human MDX Content Block workflow. - [x] Document MCP discovery, connection, editing, diagnostics, frontmatter, dynamic sources, conflicts, and disconnection. - [x] Add only screenshots that clarify otherwise hard-to-describe UI steps. - [x] Test every documented MDX capability through the local MCP CLI with a low-reasoning agent. - [x] Reproduce and fix the replacement-confirmation schema mismatch. - [x] Reproduce and fix persistent-session conflict reload and reapply. - [x] Add regression tests that failed before each product fix and pass afterward. - [x] Regenerate runtime contracts and generated MCP documentation. - [x] Review authoritative `docs/` content and update affected pages. - [x] Run affected tests, typechecks, formatting, and diff checks. ## Verification - Project Build: 208 affected tests passed. - Content Engine Asset session: 8 tests passed. - CLI documentation tests: 14 tests passed. - MCP docs generator: 3 tests passed. - Content Engine, Project Build, CLI, and MCP docs typechecks passed. - `pnpm oxfmt --check` passed. - `git diff --check` passed. - Low-reasoning MCP evaluation passed all documented workflows, including a real two-client revision conflict, reload, reapply, and final saved inspection.
1.6 KiB
description
| description |
|---|
| This page highlights where to get support for all Webstudio customers. |
🆘 Webstudio Support Process
Account upgrades
If you're looking to upgrade your account and wish to receive a credit for any previous purchase, follow the below steps:
-
Select Existing Lifetime Customer, Click here.
-
Fill out the upgrade request form.
RocketHub account issues
If you're having trouble with an activation through a RocketHub purchase, please reach out to RocketHub support directly. They can issue you a new activation code.
AppSumo account issues
If you're having trouble activating an AppSumo license, ask for help in the Webstudio community. Do not post license codes, authentication links, or other private account information.
Any other type of support
All other support is run directly via our community. We have a thriving community of creators who are always around to help out new members. The core Webstudio team also monitors the community posts daily. You can join the Webstudio community anytime from here.
Related
- Account Limits – View domain and pageview limits for different plans
- FAQs – Common questions and answers about Webstudio
- Roadmap & Links – Official links and community resources