Adding a WYSIWYG to a DXP component

NickyP · December 4, 2025, 11:24pm

Hello Squiz community

Apologies if this question is simple question but (I’m trying to create my first DXP component) has anyone created a DXP component and added a minimal WYSIWYG to the manifest.json?

Is this correct?

      "summary": {
          "type": "wysiwyg",
          "label": "Summary",
          "toolbar": ["bold", "italic", "link", "unorderedList", "orderedList"],
          "required": false
        },

I believe you can’t test it locally?

Many thanks
N

isimmons · December 5, 2025, 3:17am

Hi @NickyP !

Hope you’re doing well!

You’re actually looking for the FormattedText input field type

Here’s an example manifest:

github.com/squizlabs/dxp-component-library

dxp/component-service/content-summary/manifest.json

main


      
          },
          "heading": {
            "type": "string",
            "title": "Heading",
            "description": "The main heading text.",
            "default": "Heading",
            "ui:metadata": {
              "inlineEditable": true
            }
          },
          "textContent": {
            "type": "FormattedText",
            "title": "Text Content",
            "description": "The main text content displayed in the section.",
            "ui:metadata": {
              "inlineEditable": true
            }
          },
          "link": {
            "type": "SquizLink",
            "title": "Link",

Not sure about testing locally, see how you go with the above. You will probably want to look at making it inline editable in DXP Page Builder in Matrix.

Let me know how you go.
– iain

NickyP · December 5, 2025, 3:25am

Hey Iain
Thanks heaps! This is exactly what I was after :-1

Cheers
Nick

aleks · December 10, 2025, 5:13pm

Nice one buddy - how you finding the experience of building components?

NickyP · December 10, 2025, 11:55pm

Hi Aleks,

How am I finding the component development workflow?
It has definitely been a steep learning curve, but I am enjoying the process.

The main gap I have noticed is the transition between the Academy’s “build your first component” training and actually developing a production-ready component for a real-world site. There is very little guidance or support for that middle layer - the practical application, best-practice patterns, and troubleshooting required to bridge the two.

This is an area where I believe Squiz could provide stronger support and clearer pathways.

BTW can anyone tell me if this the correct schema URL and NOT the localhost:3000
“$schema”: “http://squiz.cloud/components/schemas/v1.json#”

aleks · December 15, 2025, 7:14pm

Yeh it was the same for me. Looking at how others built components helped more than the academy training! [dxp-component-library] [squiz-dxp-component-system-squiz-qol-collab]