Frequently asked questions

Currently, 'Can clone' and 'Can copy' settings only work for View-only links, not Content edit links. This is a popular request and Webstudio is working on more granular permissions (GitHub issue 5187) to allow content editing while preventing cloning/copying. This would be useful for client work where you want to allow editing but protect your project structure.

To create different navigation styles for different pages, you need to unlink the navigation from the global slot. Copy the navigation out of the 'navbar transparent_home' slot which synchronizes navigation across all pages. Once copied out of the slot, you can style each navigation independently without affecting other pages.

When copying sections from marketplace templates, you should be able to edit text directly in Text and Link components as rich text containers. If you encounter issues where editing destroys the component structure or only shows JSON-like expressions, this was a known bug that has been fixed. The fix ensures Text and Link components are treated as rich text containers rather than requiring parent element editing.

You have two approaches: 1) Wrapper approach: Wrap the entire card in a Link component (better semantics), or 2) Stretched link technique: Set the card to position: relative, add a link inside, then add an element inside that link with position: absolute and inset: 0. However, the stretched link approach can interfere with content editing access for clients. For clients using Content Editor, use a CSS solution that disables the overlay when in edit mode: body:not([tabindex="0"]) [data-card]::after { content: ""; position: absolute; inset: 0; }

This is a known issue that some users experience intermittently. If you cannot drag elements into an Item Trigger, try refreshing the page or checking if the element you're trying to drag has any special properties or constraints. This bug may affect specific element types like h3 or footer elements.

Wrapping the entire card in a Link component is semantically better and more accessible. The stretched link technique (absolute positioned overlay) can hurt screen readers, may be devalued by Google, and blocks content editing access. For content editors, use CSS like 'body:not([tabindex="0"]) [data-card]::after' to only apply the overlay when not in edit mode.

This is a known issue where sometimes elements cannot be dragged into Collection Item Trigger containers. It affects various elements like headings, footers, and other components. This appears to be a UI bug in the drag-and-drop system. Try refreshing the builder, copying and pasting the element instead, or restructuring your layout as a workaround until this issue is resolved.

This is a known intermittent issue where certain elements cannot be dragged into Item Trigger components while others work fine. It's been reported by multiple users and appears to affect various element types (H3, footer elements, etc.) inconsistently. This seems to be a UI bug that the team is aware of and working to resolve.

If you can't edit text in copied marketplace template sections, this was a known bug where Text and Link components weren't being treated as rich text containers. The issue has been fixed - Text and Link components are now properly recognized as editable rich text elements, preventing the editor from trying to edit their parent containers instead.

This is a bug where components that were replaced by the Element component show as 'Ws:Element' in the Content Block dropdown. As a workaround, you can manually specify labels for components. This issue has been fixed in GitHub PR 5363, where proper labels now show in the <tag> format.

If paragraph text becomes invisible (opacity: 0) when trying to edit or select portions of text, this is usually caused by conflicting custom scripts in your project. Check if you have any custom HTML Embed components with scripts that might be interfering with Webstudio's text editor. Remove or modify conflicting scripts to resolve this issue.

Not currently, but markdown support as Content Embed is planned (GitHub issue 3485). This would allow any text field to become rich text, making any database or backend suddenly CMS-capable with decent content editing. Markdown support would enable use of platforms like Strapi and Contentful that output markdown instead of HTML.