Skip to content

update: add webflow-code-component-skills#10

Merged
viratatwebflow merged 2 commits intomainfrom
code-component
Mar 11, 2026
Merged

update: add webflow-code-component-skills#10
viratatwebflow merged 2 commits intomainfrom
code-component

Conversation

@viratatwebflow
Copy link
Copy Markdown
Collaborator

  • Introduced a new skill for building and deploying Webflow Code Components with validation workflows.
  • Updated plugin.json to include the new skill in the skills array.

…onfigurations

- Introduced a new skill for building and deploying Webflow Code Components with validation workflows.
- Updated plugin.json to include the new skill in the skills array.
Copy link
Copy Markdown

@tim-webflow tim-webflow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got these to work locally. 👍

Copy link
Copy Markdown

@federico-fiorini federico-fiorini left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I left a couple of suggestions but this looks great!


| Look For | Recommendation |
|----------|----------------|
| Hardcoded text strings | Expose as `props.Text()` or `props.RichText()` |
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

RichText should probably go on the next line "Text that designers should edit on canvas". It's not a single text string but it supports markup etc and it can be edited on canvas

Copy link
Copy Markdown
Collaborator Author

@viratatwebflow viratatwebflow Mar 11, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added thank you

| Issue | Detection | Fix |
|-------|-----------|-----|
| Using site/global CSS classes | Class names like `.container`, `.btn` | Use CSS Modules or component-scoped styles |
| CSS-in-JS not configured | styled-components/Emotion without decorator | Add globals.ts with `styledComponentsShadowDomDecorator` (styled-components) or `emotionShadowDomDecorator` (Emotion/MUI) |
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's also another requirement to get styled-components and emotion work fine in SSR, which is to use the corresponding serve renderer in the webflow.json config

e.g.

  "library": {
    "renderer": {
      "server": "@webflow/styled-component-utils/server"
    }
  }

This doesn't necessarily fall under the shadow DOM compatibility but something worth calling out

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Make sense, made the changes

**For both CSS-in-JS approaches**, update `webflow.json`:
```json
{
"library": {
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe here add the server renderer config

  "library": {
    "renderer": {
      "server": "@webflow/emotion-utils/server"
    }
  }

Copy link
Copy Markdown
Collaborator Author

@viratatwebflow viratatwebflow Mar 11, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just added those info

- Corrected the recommendations for exposing text properties in component audit documentation.
- Added detailed SSR configuration instructions for styled-components and Emotion in the convert component documentation.
@viratatwebflow viratatwebflow merged commit 2a23e91 into main Mar 11, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants