veea

<p style="text-align: right;">This document is used to test the core editing capabilities of the documentation editor.<br>It is written like a real internal or product document and includes multiple content structures to verify how different blocks behave during editing.This document is used to test the core editing capabilities of the documentation editor.<br>It is written like a real internal or product document and includes multiple content structures to verify how different blocks behave during editing the document.</p><p>The goal is to ensure smooth typing, block separation, formatting, and content manipulation.</p><p></p><p>/</p><h2>Introduction</h2><p>Good documentation helps teams move faster and stay aligned and awesome.<br>A well designed editor should make writing, editing, and organizing content feel effortless.</p><p>This section tests basic paragraph blocks.<br>You should be able to click, edit, split, merge, and move these paragraphs without issues.</p><p>Documentation is not just about writing words.<br>It is about structuring information in a way that is easy to read and easy to maintain.</p><h2>Headings and Structure</h2><p>Headings help readers scan content quickly.<br>They also define the hierarchy of the document.</p><h3>When to Use Headings</h3><p>Use large headings for major sections.<br>Use smaller headings for supporting ideas or nested sections.</p><p>A good rule of thumb is to keep headings clear, short, and descriptive.</p><h3>Consistency Matters</h3><p>Consistent heading levels improve readability.<br>They also help with navigation and future collaboration.</p><h2>Lists and Organization</h2><p>Lists are useful for breaking down ideas into clear, scannable points.</p><h3>Unordered List Example</h3><ul><li><p>Write clear documentation</p></li><li><p>Keep sections focused</p></li><li><p>Use headings consistently</p></li><li><p>Avoid unnecessary complexity</p></li></ul><h3>Ordered List Example</h3><ol><li><p>Define the goal of the documentssss</p></li><li><p>Outline the main sections</p></li><li><p>Write content for each section</p></li><li><p>Review and refine</p></li></ol><h3>Nested List Example</h3><ul><li><p>Documentation types</p><ul><li><p>Product documentation</p></li><li><p>Internal documentation</p></li><li><p>API documentation</p></li></ul></li><li><p>Common audiences</p><ul><li><p>Developers</p></li><li><p>Designers</p></li><li><p>Stakeholders</p></li></ul></li></ul><h2>Checklists</h2><p>Checklists are useful for workflows and repeatable processes.</p><ul><li><p>Draft the document</p></li><li><p>Review content accuracy</p></li><li><p>Check formatting and structure</p></li><li><p>Publish or share with the team</p></li></ul><h2>Quotes and Emphasis</h2><p>Sometimes you need to highlight an important idea.</p><blockquote><p>Clear documentation is a force multiplier for growing teams.</p></blockquote><p>You should be able to edit quoted text just like normal paragraphs.</p><h2>Code and Technical Content</h2><p>Documentation often includes technical examples.</p><p>Inline code can look like this: <code>npm run dev</code></p><p>Below is a longer code example.</p><pre><code class="language-plaintext">function createDoc(title) {
  return {
    title: title,
    status: "draft",
    createdAt: new Date()
  };
}
</code></pre><p>This block tests how the editor handles multiline content and fixed width text.</p><h2>Tables and Structured Data</h2><p>Some information is easier to understand in a structured format.</p><table class="border-collapse table-auto w-full" style="min-width: 75px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th class="border border-gray-300 dark:border-dark-border p-2 bg-gray-50 dark:bg-dark-border font-semibold" colspan="1" rowspan="1"><p>Feature</p></th><th class="border border-gray-300 dark:border-dark-border p-2 bg-gray-50 dark:bg-dark-border font-semibold" colspan="1" rowspan="1"><p>Status</p></th><th class="border border-gray-300 dark:border-dark-border p-2 bg-gray-50 dark:bg-dark-border font-semibold" colspan="1" rowspan="1"><p>Notes</p></th></tr><tr><td class="border border-gray-300 dark:border-dark-border p-2" colspan="1" rowspan="1"><p>Rich text editing</p></td><td class="border border-gray-300 dark:border-dark-border p-2" colspan="1" rowspan="1"><p>Enabled</p></td><td class="border border-gray-300 dark:border-dark-border p-2" colspan="1" rowspan="1"><p>Supports paragraphs and headings</p></td></tr><tr><td class="border border-gray-300 dark:border-dark-border p-2" colspan="1" rowspan="1"><p>Lists</p></td><td class="border border-gray-300 dark:border-dark-border p-2" colspan="1" rowspan="1"><p>Enabled</p></td><td class="border border-gray-300 dark:border-dark-border p-2" colspan="1" rowspan="1"><p>Ordered and unordered</p></td></tr><tr><td class="border border-gray-300 dark:border-dark-border p-2" colspan="1" rowspan="1"><p>Tables</p></td><td class="border border-gray-300 dark:border-dark-border p-2" colspan="1" rowspan="1"><p>In progress</p></td><td class="border border-gray-300 dark:border-dark-border p-2" colspan="1" rowspan="1"><p>Basic support only</p></td></tr></tbody></table><p>You should be able to place your cursor inside each cell and edit content naturally.</p><h2>Notes and Callouts</h2><p>This section represents an informational note.</p><p>Note: This editor should support visually distinct blocks for tips, warnings, or important messages.</p><p>These blocks are often used to draw attention without breaking the reading flow.</p><h2>Mixed Content Section</h2><p>This section combines text, lists, and code to test real world editing scenarios.</p><p>You might:</p><ul><li><p>Edit text above a list</p></li><li><p>Convert a paragraph into a heading</p></li><li><p>Move sections up or down</p></li><li><p>Copy and paste blocks across documents</p></li></ul><pre><code class="language-plaintext">Example:
Convert this code block into a normal text block if needed.
</code></pre><h2>Conclusion</h2><p>If this document feels easy to write, edit, and reorganize, the editor is doing its job well.</p><p>Next steps might include testing collaboration, comments, version history, and permissions.</p><p>End of document.</p><p>The goal is to ensure smooth typing, block separation, formatting, and content manipulation.</p><h2>Introduction</h2><p>Good documentation helps teams move faster and stay aligned.<br>A well designed editor should make writing, editing, and organizing content feel effortless.</p><p>This section tests basic paragraph blocks.<br>You should be able to click, edit, split, merge, and move these paragraphs without issues.</p><p>Documentation is not just about writing words.<br>It is about structuring information in a way that is easy to read and easy to maintain.</p><h2>Headings and Structure</h2><p>Headings help readers scan content quickly.<br>They also define the hierarchy of the document.</p><h3>When to Use Headings</h3><p>Use large headings for major sections.<br>Use smaller headings for supporting ideas or nested sections.</p><p>A good rule of thumb is to keep headings clear, short, and descriptive.</p><h3>Consistency Matters</h3><p>Consistent heading levels improve readability.<br>They also help with navigation and future collaboration.</p><h2>Lists and Organization</h2><p>Lists are useful for breaking down ideas into clear, scannable points.</p><h3>Unordered List Example</h3><ul><li><p>Write clear documentation</p></li><li><p>Keep sections focused</p></li><li><p>Use headings consistently</p></li><li><p>Avoid unnecessary complexity</p></li></ul><h3>Ordered List Example</h3><ol><li><p>Define the goal of the document</p></li><li><p>Outline the main sections</p></li><li><p>Write content for each section</p></li><li><p>Review and refine</p></li></ol><h3>Nested List Example</h3><ul><li><p>Documentation types</p><ul><li><p>Product documentation</p></li><li><p>Internal documentation</p></li><li><p>API documentation</p></li></ul></li><li><p>Common audiences</p><ul><li><p>Developers</p></li><li><p>Designers</p></li><li><p>Stakeholders</p></li></ul></li></ul><h2>Checklists</h2><p>Checklists are useful for workflows and repeatable processes.</p><ul><li><p>Draft the document</p></li><li><p>Review content accuracy</p></li><li><p>Check formatting and structure</p></li><li><p>Publish or share with the team</p></li></ul><h2>Quotes and Emphasis</h2><p>Sometimes you need to highlight an important idea.</p><blockquote><p>Clear documentation is a force multiplier for growing teams.</p></blockquote><p>You should be able to edit quoted text just like normal paragraphs.</p><h2>Code and Technical Content</h2><p>Documentation often includes technical examples.</p><p>Inline code can look like this: <code>npm run dev</code></p><p>Below is a longer code example.</p><pre><code class="language-plaintext">function createDoc(title) {
  return {
    title: title,
    status: "draft",
    createdAt: new Date()
  };
}
</code></pre><p>This block tests how the editor handles multiline content and fixed width text.</p><h2>Tables and Structured Data</h2><p>Some information is easier to understand in a structured format.</p><table class="border-collapse table-auto w-full" style="min-width: 75px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th class="border border-gray-300 dark:border-dark-border p-2 bg-gray-50 dark:bg-dark-border font-semibold" colspan="1" rowspan="1"><p>Feature</p></th><th class="border border-gray-300 dark:border-dark-border p-2 bg-gray-50 dark:bg-dark-border font-semibold" colspan="1" rowspan="1"><p>Status</p></th><th class="border border-gray-300 dark:border-dark-border p-2 bg-gray-50 dark:bg-dark-border font-semibold" colspan="1" rowspan="1"><p>Notes</p></th></tr><tr><td class="border border-gray-300 dark:border-dark-border p-2" colspan="1" rowspan="1"><p>Rich text editing</p></td><td class="border border-gray-300 dark:border-dark-border p-2" colspan="1" rowspan="1"><p>Enabled</p></td><td class="border border-gray-300 dark:border-dark-border p-2" colspan="1" rowspan="1"><p>Supports paragraphs and headings</p></td></tr><tr><td class="border border-gray-300 dark:border-dark-border p-2" colspan="1" rowspan="1"><p>Lists</p></td><td class="border border-gray-300 dark:border-dark-border p-2" colspan="1" rowspan="1"><p>Enabled</p></td><td class="border border-gray-300 dark:border-dark-border p-2" colspan="1" rowspan="1"><p>Ordered and unordered</p></td></tr><tr><td class="border border-gray-300 dark:border-dark-border p-2" colspan="1" rowspan="1"><p>Tables</p></td><td class="border border-gray-300 dark:border-dark-border p-2" colspan="1" rowspan="1"><p>In progress</p></td><td class="border border-gray-300 dark:border-dark-border p-2" colspan="1" rowspan="1"><p>Basic support only</p></td></tr></tbody></table><p>You should be able to place your cursor inside each cell and edit content naturally.</p><h2>Notes and Callouts</h2><p>This section represents an informational note.</p><p>Note: This editor should support visually distinct blocks for tips, warnings, or important messages.</p><p>These blocks are often used to draw attention without breaking the reading flow.</p><h2>Mixed Content Section</h2><p>This section combines text, lists, and code to test real world editing scenarios.</p><p>You might:</p><ul><li><p>Edit text above a list</p></li><li><p>Convert a paragraph into a heading</p></li><li><p>Move sections up or down</p></li><li><p>Copy and paste blocks across documents</p></li></ul><pre><code class="language-plaintext">Example:
Convert this code block into a normal text block if needed.
</code></pre><h2>Conclusion</h2><p>If this document feels easy to write, edit, and reorganize, the editor is doing its job well.</p><p>Next steps might include testing collaboration, comments, version history, and permissions.</p><p>End of document.</p><p></p>

This document is used to test the core editing capabilities of the documentation editor.

It is written like a real internal or product document and includes multiple content structures to verify how different blocks behave during editing.This document is used to test the core editing capabilities of the documentation editor.

It is written like a real internal or product document and includes multiple content structures to verify how different blocks behave during editing the document.

The goal is to ensure smooth typing, block separation, formatting, and content manipulation.

Good documentation helps teams move faster and stay aligned and awesome.

A well designed editor should make writing, editing, and organizing content feel effortless.

This section tests basic paragraph blocks.

You should be able to click, edit, split, merge, and move these paragraphs without issues.

Documentation is not just about writing words.

It is about structuring information in a way that is easy to read and easy to maintain.

Headings help readers scan content quickly.

They also define the hierarchy of the document.

Use smaller headings for supporting ideas or nested sections.

A good rule of thumb is to keep headings clear, short, and descriptive.

Consistent heading levels improve readability.

They also help with navigation and future collaboration.

Lists are useful for breaking down ideas into clear, scannable points.

Checklists are useful for workflows and repeatable processes.

Sometimes you need to highlight an important idea.

You should be able to edit quoted text just like normal paragraphs.

Documentation often includes technical examples.

function createDoc(title) {
  return {
    title: title,
    status: "draft",
    createdAt: new Date()
  };
}


This block tests how the editor handles multiline content and fixed width text.

Some information is easier to understand in a structured format.

You should be able to place your cursor inside each cell and edit content naturally.

This section represents an informational note.

Note: This editor should support visually distinct blocks for tips, warnings, or important messages.

These blocks are often used to draw attention without breaking the reading flow.

This section combines text, lists, and code to test real world editing scenarios.

Example:
Convert this code block into a normal text block if needed.


If this document feels easy to write, edit, and reorganize, the editor is doing its job well.

Next steps might include testing collaboration, comments, version history, and permissions.

Good documentation helps teams move faster and stay aligned.

Comments

No comments yet