A comprehensive test post exercising all rich-text block types — headings, paragraphs, lists, blockquotes, code, inline marks, and more — to verify the Lexical editor renders everything correctly.
Heading 1 — The Big Title
This is a normal paragraph under Heading 1. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque habitant morbi tristique senectus et netus.
Heading 2 — Section Title
This paragraph contains bold text, italic text, and bold-italic text. You can also check strikethrough rendering here.
Heading 3 — Subsection
Heading 3 should feel smaller than H2 but still stand out from body text.
Heading 4 — Deep Subsection
Heading 4 is compact — used for fine-grained breakdowns.
Unordered List
- First item in the bullet list
- Second item with bold inside it
- Third item — back to root level
- Fourth item — final
Ordered List
- Step one — do this first
- Step two — then do this
- Step three — finally wrap up
- Step four — profit
Checklist
Blockquote
"The best way to predict the future is to invent it."
— Alan Kay
Inline Code
Inline code looks like this: npm run dev. It should render in a monospace font with a subtle background highlight.
Fenced Code Block
```js
async function fetchPosts(slug) {
const res = await fetch(/api/posts?slug=${slug});
if (!res.ok) throw new Error('Failed to fetch');
return res.json();
}
```
Link
Visit the [Payload CMS docs](https://payloadcms.com/docs) to learn more about the CMS powering this site.
Table
Feature | Status | Notes |
|---|---|---|
Headings H1–H4 | Working | All levels render |
Bold / Italic | Working | Inline marks OK |
Unordered list | Working | Bullets render |
Ordered list | Working | Numbers render |
Checklist | Working | Checkboxes render |
Blockquote | Working | Left border accent |
Inline code | Working | Monospace highlight |
Code block | Testing | Fenced ``` block |
Links | Testing | [text](url) syntax |
Table | Testing | This very table |
Mixed Inline Formatting Stress Test
This paragraph mixes bold, italic, inline code, and a [link](https://payloadcms.com) all in the same line to ensure none of them break each other's rendering in the Lexical output.
Closing Paragraph
If every section above renders correctly — headings, spacing, colors, inline styles, code blocks, links, and the table — then the full rich-text pipeline from Lexical to HTML is confirmed working.

Comments
No comments yet. Be the first to comment.
Leave a comment
Comments are moderated and will appear once approved. Sign in with Google coming soon.