Files
webstudio/docs/university/foundations/copy-paste/webflow.md
Oleg Isonen 99371187dc docs: Move product documentation into Builder (#5987)
## Summary

- move the complete GitBook documentation tree and assets into Builder
under `/docs`
- generate the exhaustive MCP page from the local CLI source in the same
change
- publish GitBook from a release-gated `docs` branch containing the
exact successfully released revision
- run MCP documentation tests, typechecking, and stale-output checks
with the existing generated-docs check
- remove links to the Community Discussions repository

## Technical choices

- Import the current documentation as a linear snapshot so the branch
satisfies Builder's required-linear-history protection.
- Keep the Markdown wrapper separate from the TypeScript generator at
`scripts/docs/mcp-page.md`.
- Generate through `packages/cli/local.js` so CLI guidance and its
documentation are reviewed together.
- Let `check:generated-docs` reject CLI changes that leave the committed
MCP page stale.
- After both GitHub release creation and package publication succeed,
fast-forward the read-only `docs` branch to the immutable release tag
commit. A divergent update fails instead of publishing a different
revision.
- Configure GitBook to publish `/docs` from the `docs` branch, not
directly from `main`.
- Exclude `/docs` from the repository-wide `oxfmt` scan so imported
GitBook Markdown retains its established formatting; generator tests and
stale-output checks still validate the MCP page.
- Exclude `transcripts/` and GitHub Discussions from the migration.

## Todo

- [x] Import documentation, navigation, includes, and assets under
`/docs`.
- [x] Generate the MCP page from the local CLI source.
- [x] Move MCP generation and validation into Builder.
- [x] Require MCP documentation updates alongside CLI changes.
- [x] Publish released revisions through a read-only `docs` branch.
- [x] Remove Community repository links from Builder and the migrated
docs.
- [x] Preserve and verify a final Community Git bundle locally.
- [ ] Merge this pull request.
- [ ] Let the next successful release create or advance the `docs`
branch.
- [ ] Repoint GitBook Git Sync to `webstudio-is/webstudio`, branch
`docs`, root directory `/docs`.
- [ ] Verify `docs.webstudio.is`, navigation, assets, anchors, and the
MCP page in production.
- [ ] Delete `webstudio-is/webstudio-community`.

## Verification

- `pnpm check:generated-docs`
- `pnpm lint`
- `pnpm oxfmt --check`
- `git diff --check origin/main...HEAD`
- generator regression test demonstrated failing when the GitBook
wrapper behavior was removed, then passing after restoration
- no fixture inputs or outputs are affected

## Known limitation

All documentation merged after the previous release waits for the next
successful release before GitBook publishes it. This deliberately keeps
the public MCP reference aligned with an installable CLI revision.

Ref #5986
2026-08-03 17:55:50 +02:00

15 KiB
Raw Permalink Blame History

description
description
Webstudio supports pasting Webflow Elements, converting them from Webflow format to Webstudio format.

↔️ Webflow

It works by copying anything in Webflow format, such as component libraries and projects, and pasting it into Webstudio, transferring the structure and styles.

If the pasted Webflow content references images, including background images, Webstudio uploads those images into Assets and rewrites the pasted components/styles to use the uploaded assets.

What does and doesn’t transfer

Elements

Webflow Element Transfers? Notes
Section ✅
Container ✅
Quick Stack ✅
V Flex ✅
H Flex ✅
Div Block ✅
List ✅
List Item ✅
Link Block ✅
Button ✅ Maps to "Link". Buttons are for interactions, like submitting a form, not linking.
Heading ✅
Paragraph ✅
Text Link ✅
Text Block ✅
Block Quote ✅
Rich Text ✅ There is no Rich Text component in Webstudio, though any children of the copied Rich Text paste in as their respective components. For example, Rich Text with a Heading and Link will transfer as a Heading and Link.
Collection List ❌ Though Webstudio does have a "Collection" component.
Image ✅
Video ❌ Can be rebuilt “Vimeo” or “HTML Embed”
YouTube ❌ Can be rebuilt using “HTML Embed”. See status of this component in Webstudio.
Lottie Animation ❌ Can be rebuilt using “HTML Embed”
Spline Scene ❌ Can be rebuilt using “HTML Embed”
Form Block ✅
Label ✅
Input ✅
File Upload ❌ See status of this component in Webstudio
Text Area ✅
Checkbox ✅
Radio Button ✅
Select ✅
reCAPTCHA ❌ reCAPTCHA doesn’t transfer as Webstudio uses alternative methods of preventing spam.
Form Button ✅ Maps to "Button"
Search ❌
Background Video ❌
Dropdown ❌ Can be rebuilt using Radix “Select”
Code Embed ✅
Lightbox ❌
Locales List ❌
Navbar ✅ Generates the corresponding components such as Boxes and Links with Tokens and styles.
Slider ❌ Can be rebuilt using Swiper.js in the Marketplace
Tabs ❌ Can be rebuilt using Radix “Tabs”
Map ❌
Facebook ❌
X (Twitter) ❌
Custom Element ❌ See status of this component in Webstudio
Code Block ✅
Grid ✅
Columns ✅

Styles

✅ Both Webflow and Webstudio support all CSS properties, allowing all styles defined in the style panel to transfer.

✅ Webflow preset styles, which Webflow adds by default to pages and Elements.

❌ Webflow variables and their values do not transfer as those values are not available within the Webflow copy.

❌ User-defined styles on global tag selectors as they are not available in the Webflow copy. For example, global styling on an H1 does not transfer, but a Token of h1 is created and available for applying the styles.

Global tag styling in webflow h1 token in webstudio

Classes

✅ Classes and combo classes will transfer as Tokens with their respective styles.

{% hint style="success" %} Pasting a class/Token that already exists will not cause duplication or override it. {% endhint %}

Breakpoints

✅ Responsive styles and breakpoints will transfer.

Interactions

❌ Interactions and animations do not transfer.