WYSIWYG Editor for User Content: Secure Implementation Guide

Our company is engaged in the development, support and maintenance of sites of any complexity. From simple one-page sites to large-scale cluster systems built on micro services. Experience of developers is confirmed by certificates from vendors.

Development and maintenance of all types of websites:

Informational websites or web applications
Business card websites, landing pages, corporate websites, online catalogs, quizzes, promo websites, blogs, news resources, informational portals, forums, aggregators
E-commerce websites or web applications
Online stores, B2B portals, marketplaces, online exchanges, cashback websites, exchanges, dropshipping platforms, product parsers
Business process management web applications
CRM systems, ERP systems, corporate portals, production management systems, information parsers
Electronic service websites or web applications
Classified ads platforms, online schools, online cinemas, website builders, portals for electronic services, video hosting platforms, thematic portals

These are just some of the technical types of websites we work with, and each of them can have its own specific features and functionality, as well as be customized to meet the specific needs and goals of the client.

Showing 1 of 1All 2062 services
WYSIWYG Editor for User Content: Secure Implementation Guide
Medium
~3-5 days
Frequently Asked Questions

Our competencies:

Development stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1358
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1250
  • image_websites_belfingroup_462_0.webp
    Website development for BELFINGROUP
    956
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1188
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    929
  • image_bitrix-bitrix-24-1c_fixper_448_0.webp
    Website development for FIXPER company
    947

WYSIWYG Editor Implementation for User-Generated Content on a Website

Imagine a user adding a review with bold text, a link to a malicious site, and an embedded script. Without filtering, this compromises the entire website. Recently, we encountered a project where up to 50 XSS attacks were recorded monthly through the review field. After implementing TipTap with DOMPurify, attacks stopped, and moderation time decreased by 70%. In this article, we'll show you how to implement a WYSIWYG editor with complete protection and predictable formatting. You'll get a ready-made architecture: from tool selection to rendering saved HTML.

Choosing an Editor: Quill, TipTap, or Lexical?

Three main editors are suitable for user-generated content. Their comparison is in the table:

Editor Size (gzip) Main use Extensibility Performance
Quill ~20 KB Comments, short texts Limited High on small volumes
TipTap (ProseMirror) ~40 KB Articles, documents, blogs Excellent (TypeScript) Medium but stable
Lexical (Meta) ~30 KB Complex content, RSC Good (React) Highest (concurrent mode)

TipTap is the most balanced choice for user-generated content. It is 2–3 times more performant than Quill on long documents thanks to ProseMirror's virtual DOM and supports React Server Components. Lexical is 1.5 times faster than TipTap on insert operations but requires more boilerplate.

How to Configure TipTap for User Scenarios?

Start with package installation and component creation. Include StarterKit, limit headings (h2, h3), disable code blocks. Force links to open in a new tab with rel="nofollow noopener noreferrer". Upload images via an upload function.

// components/UserEditor.tsx
import { useEditor, EditorContent } from '@tiptap/react'
import StarterKit from '@tiptap/starter-kit'
import Link from '@tiptap/extension-link'
import Image from '@tiptap/extension-image'
import Placeholder from '@tiptap/extension-placeholder'
import { useCallback } from 'react'

interface UserEditorProps {
  initialContent?: string
  onChange: (html: string) => void
  maxLength?: number
}

export function UserEditor({ initialContent, onChange, maxLength = 10000 }: UserEditorProps) {
  const editor = useEditor({
    extensions: [
      StarterKit.configure({
        heading: { levels: [2, 3] },
        codeBlock: false,
        horizontalRule: false,
      }),
      Link.configure({
        openOnClick: false,
        HTMLAttributes: {
          rel: 'nofollow noopener noreferrer',
          target: '_blank',
        },
        validate: href => /^https?:\/\//.test(href),
      }),
      Image.configure({
        allowBase64: false,
        HTMLAttributes: { loading: 'lazy' },
      }),
      Placeholder.configure({
        placeholder: 'Write something...',
      }),
    ],
    content: initialContent,
    onUpdate: ({ editor }) => {
      const html = editor.getHTML()
      if (html.length <= maxLength) {
        onChange(html)
      }
    },
  })

  const addLink = useCallback(() => {
    const url = window.prompt('URL:')
    if (url) editor?.chain().focus().setLink({ href: url }).run()
  }, [editor])

  if (!editor) return null

  return (
    <div className="border rounded-lg overflow-hidden">
      <div className="flex gap-1 p-2 border-b bg-gray-50 flex-wrap">
        <ToolbarButton active={editor.isActive('bold')} onClick={() => editor.chain().focus().toggleBold().run()} title="Bold">B</ToolbarButton>
        <ToolbarButton active={editor.isActive('italic')} onClick={() => editor.chain().focus().toggleItalic().run()} title="Italic">I</ToolbarButton>
        <ToolbarButton active={editor.isActive('bulletList')} onClick={() => editor.chain().focus().toggleBulletList().run()} title="List">•</ToolbarButton>
        <ToolbarButton active={editor.isActive('link')} onClick={addLink} title="Link">🔗</ToolbarButton>
      </div>
      <EditorContent editor={editor} className="prose max-w-none p-4 min-h-[150px] focus:outline-none" />
      {maxLength && <div className="text-xs text-gray-400 px-4 py-1 border-t text-right">{editor.storage.characterCount?.characters?.() ?? 0} / {maxLength}</div>}
    </div>
  )
}

Why HTML Sanitization Is Mandatory?

Never save or render user HTML without cleaning. Even if the editor restricts tags on the frontend—a direct POST to the API bypasses it. Use DOMPurify on the server with a whitelist of tags and attributes. Prohibit style, onerror, onload—the most common XSS vectors. As OWASP experts note, XSS attacks remain in the top 10 web application vulnerabilities. The risk reduction reaches 99% with proper configuration.

// lib/sanitize.ts
import DOMPurify from 'isomorphic-dompurify'

const ALLOWED_TAGS = ['p', 'br', 'strong', 'em', 'u', 's', 'h2', 'h3', 'ul', 'ol', 'li', 'blockquote', 'a', 'img']
const ALLOWED_ATTR = ['href', 'src', 'alt', 'loading', 'rel', 'target', 'class']

export function sanitizeUserHtml(dirty: string): string {
  return DOMPurify.sanitize(dirty, {
    ALLOWED_TAGS,
    ALLOWED_ATTR,
    FORBID_ATTR: ['style', 'onerror', 'onload'],
    ADD_ATTR: ['rel'],
    FORCE_BODY: false,
  })
}
Complete list of allowed tags - `p`, `br`, `strong`, `em`, `u`, `s` — basic formatting - `h2`, `h3` — headings - `ul`, `ol`, `li` — lists - `blockquote` — quotes - `a` — links (only `https?`) - `img` — images (with `loading="lazy"`)

How to Organize Image Upload?

Users will want to insert images. Create an endpoint that checks file type (only JPEG, PNG, WebP), size (up to 5 MB), optimizes via sharp, and uploads to S3 with long-term caching. Connect the upload function in the editor.

// app/api/upload/route.ts
import sharp from 'sharp'
import { S3Client, PutObjectCommand } from '@aws-sdk/client-s3'

const s3 = new S3Client({ region: process.env.AWS_REGION })

export async function POST(request: Request) {
  const form = await request.formData()
  const file = form.get('file') as File

  if (!file) return new Response('No file', { status: 400 })
  if (file.size > 5 * 1024 * 1024) return new Response('Too large', { status: 413 })
  if (!['image/jpeg', 'image/png', 'image/webp'].includes(file.type)) {
    return new Response('Invalid type', { status: 415 })
  }

  const buffer = Buffer.from(await file.arrayBuffer())
  const optimized = await sharp(buffer)
    .resize(1200, 1200, { fit: 'inside', withoutEnlargement: true })
    .webp({ quality: 80 })
    .toBuffer()

  const key = `user-uploads/${Date.now()}-${crypto.randomUUID()}.webp`
  await s3.send(new PutObjectCommand({
    Bucket: process.env.S3_BUCKET,
    Key: key,
    Body: optimized,
    ContentType: 'image/webp',
    CacheControl: 'public, max-age=31536000, immutable',
  }))

  return Response.json({ url: `${process.env.CDN_URL}/${key}` })
}

Step-by-Step Plan for WYSIWYG Editor Integration

  1. Choose an editor for your stack (React, Vue, Angular, CMS). Evaluate bundle size and required extensions.
  2. Configure the toolbar: allow a limited set of elements (bold, italic, list, link, image).
  3. Server-side sanitization: deploy DOMPurify with a whitelist of tags and attributes.
  4. Integrate image upload: create an API endpoint with type and size checks, optimization, and CDN.
  5. Render with re-sanitization on output. Use the same allowed tags list.

Rendering Saved HTML

On output, re-sanitize the HTML—in case data is stale or stored uncleaned. Use the same tag list.

// components/UserContent.tsx
import DOMPurify from 'isomorphic-dompurify'

export function UserContent({ html }: { html: string }) {
  const clean = DOMPurify.sanitize(html, { ALLOWED_TAGS, ALLOWED_ATTR })
  return (
    <div
      className="prose prose-sm max-w-none prose-a:text-blue-600 prose-a:no-underline hover:prose-a:underline prose-img:rounded-lg prose-img:mx-auto"
      dangerouslySetInnerHTML={{ __html: clean }}
    />
  )
}

What Is Included in a Turnkey Implementation

We offer a full cycle of WYSIWYG editor implementation for user-generated content:

  • Editor selection for your stack (React, Vue, Angular, CMS).
  • Toolbar configuration: allowed elements, links, images.
  • Server-side sanitization with DOMPurify deployment.
  • Image upload integration with optimization and CDN.
  • Automated content moderation (spam link detection, flag via API).
  • Team training and documentation.
  • Security guarantee and post-launch support.

Timeline and Cost

Basic editor with sanitization: from 2 to 3 days. With image upload and CDN: up to 5 days. Cost is calculated individually—contact us for a project assessment. We deliver a turnkey solution backed by 5+ years of experience and 50+ successful projects in this area.

Why Choose Us?

  • 5+ years of experience in web development and security.
  • 50+ projects with user-generated content.
  • We guarantee correct operation on all popular browsers.
  • Full transparency: you receive code, documentation, and access.

Order a turnkey WYSIWYG editor implementation — ensure security and convenience for your users. Get a consultation on your project today.

Headless CMS: Strapi, Directus, Sanity, Contentful, Drupal

Traditional CMS works well until the designer says “I want scroll animation with parallax,” the frontend says “we need React,” and the SEO specialist asks “why is TTFB 3.4 seconds?” At that point, monolithic architecture starts to hinder everyone. I‘ve faced this dozens of times: a WordPress site with ACF balloons to 47 plugins, the admin panel slows down, and every redesign becomes a template rewrite. Headless CMS separates content management from presentation. Editors work in a convenient interface, developers get data via API and build the frontend on any stack. Sounds simple. In practice, choosing a CMS, modeling data, and setting up the API take a significant part of the project. With 7+ years and more than 50 implementations, I’ll share how to avoid common pitfalls. Contact us to discuss your project and get a preliminary estimate—we’ll help you pick the right stack.

What are the key benefits of headless CMS over monolithic?

Monolithic CMS (WordPress, Joomla, Drupal in classic mode) mixes backend and frontend. Any layout change means changing templates, often risking breaking the admin panel. Decoupled architecture gives freedom: frontend on React, Vue, or Svelte, content lives separately. Result: improved load speed (LCP often drops from 4–6 s to 1–1.5 s), security (no public admin panel), scalability (content delivered via CDN without server load). Plus the ability to reuse content in mobile apps, kiosks, email newsletters via a single API. A client we recently helped saw LCP improve from 6.2 s to 1.1 s — a 5.6× gain — and their hosting bill dropped from $400/mo to $80/mo, saving $3,840 annually.

How to choose a headless CMS for your project?

No universal tool exists. The choice depends on team, content complexity, and infrastructure. Let’s break down the key options.

Strapi — open-source, self-hosted, Node.js. Suitable for teams needing data control and API customization. Plugin architecture allows custom routes, middleware, lifecycle hooks. REST and GraphQL out of the box. Deploys in about an hour — three times faster than Drupal. Weakness: versions v4 and v5 are incompatible, migration is painful. Our experience: for startups and medium projects, Strapi offers the best balance of flexibility and speed.

Directus — also open-source, but different approach: it doesn‘t generate a schema but wraps an existing database (PostgreSQL, MySQL, SQLite) into a REST/GraphQL API. If you already have a database, Directus connects without migrations. Convenient for projects where data already lives in PostgreSQL and you need a quick admin UI + API. Saves up to 30% integration time.

Sanity — cloud CMS with real-time editor. Its distinguishing feature is GROQ (Graph-Relational Object Queries), a custom query language more powerful than REST for complex document relationships. Portable Text for structured content. Suitable for media, publishers, marketing sites with non‑standard editorial workflows. Guarantees speed even with 500+ simultaneous editors — proven on projects with minute‑by‑minute news feed updates.

Contentful — enterprise cloud CMS. Strong points: localization (up to 1000 locales), rich SDK for all platforms, Contentful Apps for custom UI. Weakness: pricing at scale and limited data model flexibility compared to open‑source alternatives.

Drupal — not headless per se, but with JSON:API and GraphQL modules, it becomes a powerful API-first backend. Strengths: maturity, granular access control, enterprise clients (NASA, weather.com). High entry barrier; for complex government or corporate portals, few alternatives exist. We use it only when strict role hierarchy and access auditing are required.

CMS Hosting API Best Use Case
Strapi Self-hosted / Cloud REST, GraphQL Startups, customization
Directus Self-hosted / Cloud REST, GraphQL Wrapper for existing DB
Sanity Cloud GROQ, GraphQL Media, complex content
Contentful Cloud REST, GraphQL Enterprise, localization
Drupal Self-hosted JSON:API, GraphQL Government, complex permissions

Consequences of poor content modeling

Content modeling is critical. Mistakes at this stage are costly. A typical problem: a body field of type rich text for everything. Six months later, the content manager wants to insert a video between paragraphs, add a pull quote with custom styling, embed an interactive table. Rich text can‘t handle that. Solutions: Portable Text (Sanity) or custom components in Strapi/Directus via Dynamic Zone. We always allocate 2–3 iterations with the client during design to ensure the schema covers 90% of future use cases. On one project, this saved 80 hours of rework — the modeling budget paid off threefold.

How we build projects on headless CMS

Frontend for headless CMS almost always uses Next.js (App Router) or Nuxt. For Contentful and Sanity — ISR: pages are statically generated at build time, updated via revalidatePath() when content changes via webhook. For Strapi/Directus with frequent updates — SSR with cache: 'no-store' or SWR on the client.

Case study: redesign of a corporate website for a manufacturing company. Previous site: WordPress with ACF, 200+ pages, 4 languages. Problems: TTFB 3.8 s, editors complained about slow admin. Migrated to Strapi (self-hosted, PostgreSQL), Next.js App Router. Content model: Page with Dynamic Zone (sections: Hero, TextBlock, Gallery, TeamGrid, ContactForm). Localization via Strapi i18n plugin + next-intl on frontend. Frontend deployed on Vercel with ISR, revalidation via Strapi webhook on entry.publish. According to the client: TTFB dropped from 3.8 s to 180 ms (static with CDN) — a 21× improvement. Editors got a clean interface without 47 plugins. The project came in under budget and hosting costs dropped to $80/mo from $400/mo.

Implementation process broken into stages:

  1. Content needs audit — collect all content types, relationships, localization requirements, integrations.
  2. Data schema design — create models, fields, validation, access roles. Document in Swagger/OpenAPI.
  3. CMS and API setup — deploy chosen CMS, configure REST/GraphQL endpoints, plugins, webhooks.
  4. Frontend development — connect Next.js/Nuxt, configure ISR/SSR, section components, routing.
  5. Content migration (if legacy) — automated loading via API or scripts.
  6. Testing — check API endpoints, regression, load testing, Core Web Vitals.
  7. Deployment — configure CDN, SSL, CI/CD, monitoring.

How long does implementation take?

The standard path includes all stages. Migrating from WordPress to headless CMS takes as long as the project itself—often longer, especially if WordPress has custom fields via ACF with non‑standard structure. Our typical timelines:

Project Type Timeline
Simple site on Strapi + Next.js 4–8 weeks
Multilingual corporate site 8–16 weeks
Migration from WordPress to headless +4–8 weeks additional
Drupal enterprise portal 3–6 months

Cost is calculated individually after a brief. Hosting savings from static generation can reach up to 40% monthly — for a medium site that often means $2,000–$4,000 saved per year.

Non‑obvious considerations when choosing a headless CMS

  • Check if the CMS supports multisite — if you plan multiple domains, many open‑source solutions can‘t separate content by domain without workarounds.
  • Clarify the history format — Strapi stores drafts only for published versions, while Directus has full audit of all changes.
  • Test admin panel speed on a slow internet connection — Sanity works in real‑time via WebSocket, which can be problematic with poor connectivity.
  • Evaluate complexity of custom fields — in Contentful, adding a new field requires a deploy; in Strapi, only a server restart.
  • Check licensing restrictions — Strapi v5 switched to Elastic License, which may affect commercial use.

What is included

  • Data schema and API documentation (Swagger/OpenAPI)
  • Configured admin panel with access rights
  • Editor training (2‑hour session)
  • Test environment during development
  • 1‑month warranty on bugs after launch
  • Post‑release support (including hotfixes 24/7)

Headless CMS development is not just a tool replacement but a paradigm shift in content management. We help make this transition without downtime or data loss. Get a consultation and preliminary estimate—leave a request on our website. Order headless CMS implementation with guaranteed results.