Choose the structure
Insert a checklist, comparison, callout, FAQ or other supported block. Review typed fields and the live preview; generating a field and laying out a block are separate actions.
Write and edit with 21+ content block types, a floating toolbar with built-in AI actions, and a live content analysis panel that tracks word count, character count, and reading time. This is an editorial workspace, not a chatbot wrapper.
A 75-second walkthrough of a source-based draft, a claim compared with uploaded notes and the exported article.
Recorded in the product using fictional inputs. Follow the input, the review step and the exported result.
Watch on YouTube ↗A worked workflow
Use a short, permissioned source with a heading, numbered procedure, table and image caption. The task is to improve one unclear paragraph while preserving the rest of the document’s structure.
The fictional checklist shows a Pro Tip and a saved 333-character Simplify edit. A separate field-service run shows a 238-character Power Edit of its escalation-protocol paragraph.
These are two fictional documents and separate runs. Power Edit changed one paragraph; its full-run snapshots include other insertions, so their surrounding HTML differs. The new Simplify returned three paragraphs and preserved surrounding visible text and the Tip markup; reloading tidied its paragraph wrapper. Inspect the exact checks in the record. Brand-voice behavior, other documents and editorial approval need their own review.
Choose the appropriate pasted text, HTML, Markdown, document, spreadsheet, OCR or supported media path and review extracted content before using it.
Inspect: Extraction can change layout and structure. Check the list numbering, table cells, caption and source identity; do not infer lossless import from a successful upload.
Select the paragraph, provide the Power Edit instruction, inspect streamed or completed suggestions and explicitly apply the replacement when satisfied.
Inspect: Full-document context informs the response but is not permission to replace the whole document. Compare the selected range and surrounding content after applying.
Choose the block type, complete its typed fields and inspect the preview. Use item-level regeneration only where the form offers it.
Inspect: A block’s layout and its AI field assistance are separate operations. Verify supplied figures and labels before insertion.
Inspect Image Studio’s subject, style, dimensions and other offered controls. Compare a finish or prompt edit with the original, then review alternative text.
Inspect: An edited image is a new result. Keep source attribution where required and check that text removal or a crop did not alter meaningful content.
Set the supported format, theme, spacing, author, headers and footers, then open the actual Word/PDF/HTML outputs.
Inspect: Check that the heading, list, table and attribution remain usable. Editable Word, print PDF and web HTML have different structure and layout behavior.
Source-traced editing and export walkthrough using a fictional source structure. General-editor controls do not establish that the same unrestricted tools are available in Lex.
Move between structured blocks, selected-text assistance and document-level review without confusing their scope. The exported checklist shows the resulting content structure.
Checklist items grouped by phase, each with a priority tag and a way to check it, with links to Google, W3C and FTC guidance for the search, accessibility and security items.
Write an actionable checklist for a small business about to launch a new website. Group the items under content, search visibility, accessibility, performance, security and privacy, analytics, and what to verify on launch day. Each item should be a single action someone can tick off and should say how to check it. Cite published guidance for the search, accessibility and security items.
Open the full export and compare its statements with the cited sources before reuse.
Insert a checklist, comparison, callout, FAQ or other supported block. Review typed fields and the live preview; generating a field and laying out a block are separate actions.
Select a passage for Quick AI or Power Edit. Use the conversation to refine the selected range, preview the result and explicitly apply or discard it. Full-document reference context does not expand the replacement range.
Check surrounding claims and formatting after a replacement. For a broader revision, use the reviewable document flow and inspect individual proposed changes before export.
Power Edit starts from an active selection. You can give iterative or voice-transcribed instructions, choose a reply language, stop a streamed response, inspect the result and explicitly replace the selected range. Full-document context is reference material. Structured blocks have typed fields, item-level regeneration and previews; their AI field assistance is separate from their layout.
Use builder or advanced prompts with the subject and document context. Shape style, mood, lighting, palette, composition, camera and supported image dimensions. Inspect generated alternatives or a selected real photo, retain required source attribution and edit alternative text before insertion. Finishes and prompt edits create a new result; compare it with the original instead of assuming an edit is lossless.
Import options depend on the source type: pasted text, Markdown or HTML; document extraction; spreadsheet cells; image OCR; and supported media transcription. Review extracted material before drafting. Export settings include the supported format, theme, author, spacing, headers, footers and page appearance. Inspect the actual download because HTML, print PDF and editable Word represent structure differently.
Formatting support differs by editor host and export format. A useful rewrite still needs a factual and editorial review.
An AI content editor is a block-based editorial workspace where AI actions operate inline on the document you're writing, instead of a separate chatbot you copy-paste from. Gixo's version gives you 21+ structured content block types (CTAs, FAQs, pros/cons, checklists, steps, recipes, exercises, definitions, key takeaways, custom HTML), a floating toolbar with 3 Quick AI actions (rewrite, simplify, expand), and a live Content Analysis panel tracking word count, character count, and reading time. You compose structured content directly, then export as PDF, DOCX, HTML, Markdown, TXT, and JSON.
Three different jobs, three different tools. Pick by how much of the piece you want to change.
Quick AI — three one-click actions on the selection: rewrite, simplify and expand. The result replaces your selection in place and you accept or undo it. To fix grammar or change the tone, ask Power Edit.
Power Edit — type your own instruction instead of picking an action, with the rest of the article available as context. Preview the replacement before you accept it.
Ask Quill — describe the change you want and Quill proposes the individual edits, each with its reason, before anything is saved. Keep the ones that help and drop the rest. Proposing uses your plan's capacity; applying what you keep is free.
A proposal can still be wrong, and Ask Quill needs full edit access on the document. Reviewing what it suggests is the point — nothing is saved until you choose it.
Try a writing task
Open the prepared draft, review its three supplied sources, and edit it in Quill. Your next step starts with this text rather than an empty prompt.
Fictional exercise, authored for this page. The edited illustration below is hand-edited, not a generated Quill result or a customer outcome.
Make the draft easier to scan, remove repeated promises, keep the source links, and separate launch checks from claims about ranking or accessibility. Review each suggested edit before applying it.
Acorn Studio is a fictional design team preparing a small website. We want people to understand our work and contact us. This note brings together the things we should check before publishing. We should check everything carefully because a good launch is important. We want the website to be easy to find, easy to read and easy to use. This exercise does not describe a real client or a measured result.
For search, we should make our service pages clear and useful. We should check the page titles and make sure the text tells a visitor what the studio offers. We should also make sure that links point to the right pages and that important pages can be reached. The Google Search Central guide explains discovery and useful content, but publishing a page does not guarantee that Google will index it or rank it first. We should remember that there is no guaranteed position.
For reading the page, we should use headings that describe each section. The W3C WAI headings guidance explains how headings communicate structure. We should inspect the heading order and check that the page still makes sense when someone scans those headings. This is one accessibility check, not a claim that the whole website passes every accessibility requirement. We should review other requirements separately.
For loading the page, we should look at the main content and the images. The web.dev LCP guide explains a loading metric for the largest visible content element. We should measure the actual page rather than promise that a smaller image alone will solve performance. Before launch, one person should check the content and links, another should review structure and loading, and we should record anything that still needs work. Then we can decide what is ready to publish.
This fictional design team needs visitors to understand its work and find a contact path. Review three parts of the launch; none guarantees a ranking, full accessibility or a performance result.
Check clear service descriptions, descriptive page titles and working links to important pages. Use the Google Search Central guide to review discovery and content basics. Publication alone does not guarantee indexing or a particular position.
Use descriptive headings and inspect their order, following the W3C WAI headings guidance. Scan the headings to see whether they explain the page. Complete other accessibility checks separately.
Review the page's main content and images, then measure its loading experience. The web.dev LCP guide explains the metric; changing an image alone is not proof of a good result.
Assign content/link checks and structure/loading checks to reviewers. Record unresolved issues before deciding which pages are ready. Keep the supplied source links with the finished note.
The links are references to inspect, not proof that every draft statement is verified. AI suggestions require review; AI actions and exports keep their current account, trial and plan requirements.

Inspect a selected passage, an article-level request and the image editor. These are actual Quill screens from a local demonstration using a reviewed sample article clone.
Captured on 9 October 2026. Scratch identity details are masked. Creation and AI assistance depend on editing access, product eligibility and available plan allowance.
When a draft needs more than paragraphs, the editor should help you finish it in context. Quill provides insertable CTAs, FAQ sections, comparison tables, and checklists alongside inline editing. Choose blocks because they help the reader complete the task; a particular block or layout does not guarantee search visibility.
The Gixo Quill Editor works differently. It is a block-based editorial workspace where every piece of content is composed of discrete, structured blocks. You can insert a CTA block, a FAQ accordion, a pros/cons comparison, a step-by-step guide, a recipe card, an exercise block, a key takeaway callout, or a definition list directly into your document. Each block type has its own layout, and the editor renders a preview of the final output as you build. You are not formatting text after the fact. You are composing structured content from the start.
The floating toolbar includes Quick AI actions: rewrite, simplify and expand. To fix grammar or change the tone, ask Power Edit. Select any text, pick an action, and the AI modifies your selection in place. Quick AI acts on the selection; Power Edit accepts your own instruction, and Ask Quill proposes article-level changes for review. You do not need to copy the result out of a separate tool. The AI operates on the text you are editing, within the context of the surrounding content, and the result appears exactly where you need it.
The Content Analysis panel sits alongside the editor and updates in real time. It shows your current word count, character count, and estimated reading time. This matters for writers targeting specific content lengths for SEO, email newsletters, or social media repurposing. You know exactly where you stand as you write, not after you finish.
Four steps from first draft to review-ready, structured content.
Open the Insert Block panel and choose from 21+ block types: CTAs, FAQs, checklists, steps, recipes, exercises, definitions, key takeaways, pros/cons, and more.
Use the floating toolbar for headings, lists, tables, links, alignment, and find/replace. Every formatting option is one click away.
Select any text and trigger Quick AI: rewrite, simplify, expand, fix, professional, or casual. The AI modifies your selection inline.
Check word count, character count, and reading time in the Content Analysis panel. Export as PDF, DOCX, HTML, Markdown, TXT, and JSON when ready.

Each block type renders with its own structured layout. No manual formatting required.
Insert call-to-action buttons and key takeaway callouts as dedicated blocks. They render with proper styling and stand out from body text without manual CSS.
Add FAQ accordions and definition lists directly in the editor. Each FAQ block supports question-answer pairs. Definitions display with term and explanation formatting.
Build side-by-side pros and cons or multi-column comparisons. Readers scan these instantly, and they perform well for informational search queries.
Create actionable checklists and numbered step-by-step guides. Each step renders as a distinct item with its own title and description fields.
Specialized blocks for recipes (ingredients, instructions, times) and exercises (sets, reps, descriptions). Structured data that search engines can parse directly.
Drop in raw HTML when you need embeds, widgets, or custom layouts that go beyond the standard block types. Full control when you need it.
| Capability | Detail |
|---|---|
| Content block types | 21+ (CTA, FAQ, pros/cons, checklist, steps, recipe, exercise, definition, key takeaway, custom HTML, and more) |
| Quick AI actions | 3 — rewrite, simplify, expand |
| AI interaction model | Quick AI and Power Edit for selections; Ask Quill for reviewed article-level proposals |
| Content analysis | Live word count, character count, reading time |
| Export formats | 6 — PDF, DOCX, HTML, Markdown, TXT, and JSON |
| Toolbar formatting | Headings (H1–H4), bold, italic, bulleted/numbered lists, tables, links, alignment, find/replace |
| Best for | Content marketers/SEO writers, freelance writers/agencies, product/technical writers |
| Aspect | Without Gixo | With Gixo |
|---|---|---|
| Content structure | Plain text, no blocks | 21+ structured block types |
| AI assistance | Separate tool, copy-paste loop | Inline AI in the toolbar |
| Formatting | Manual HTML or Markdown | Floating toolbar, one-click |
| Content analysis | External word counter | Real-time word, char, reading time |
| Block types (FAQ, CTA, etc.) | Built manually every time | Pre-built, insert in seconds |
| Workspace | Multiple tools, tabs, windows | Everything in one editor |
Three types of professionals who benefit most from a block-based, AI-powered editing workspace.
Quill gives you a document you set up first, with a live preview that redraws as you change it. To compare another AI writer, ask for its exported file and check the headings, lists and citations in Word yourself.
Headings export as real Word heading styles, not bold paragraphs, so the navigation pane and any contents list work. Numbered and bulleted lists carry their own numbering rather than typed-in digits.
Pick a theme, write the cover, choose where page numbers sit, turn the contents list on or off, set line spacing and orientation. A live preview redraws the whole document as you change each control, so you know what you are getting before you download it.
Inline markers, a references section with retrieval dates and full URLs, or both — they are separate switches. Images keep their attribution and licence line as a caption, so the file you hand over carries its own provenance rather than losing it at the door.
Six formats — PDF, Word, HTML, Markdown, plain text and JSON. The cover page and the contents list, when you include them, open both the PDF and the Word file; in Word the headings are real heading styles, the lists carry Word's own numbering and the footer numbers the pages.
Rather than describe the export, here is one. Both files are the same Quill article, exported on 30 September 2026 through the ordinary Export Document screen, both A4 portrait. Nothing was tidied up afterwards, and the article is a sample written for this purpose rather than a customer document.
3.2 MB, 36 pages, A4 portrait. The document design exactly as it was set up: a cover page with the title and date, a contents list, and a numbered footer on every page.
2.8 MB, A4 portrait, opens in Word. The same article as an editable layout: the same cover page and contents list, real Word heading styles so the navigation pane works, list numbering Word owns rather than typed-in digits, a page-numbered footer, and 19 embedded images.
They are not identical, and that is the point. PDF carries the designed print layout; DOCX arrives as an editable Word layout, where fonts, backgrounds and page breaks may differ. Inspect the downloaded file for the destination you need. Both open with the cover page and the contents list. In the Word file that list is written out as text rather than a field Word refreshes, so if you restructure the document, retype it; and the file names its fonts rather than carrying them, so a computer without Inter shows another font in its place. Both files carry the same 19 images, byte for byte. Open both before deciding which one your workflow needs — Quill exports PDF, DOCX, HTML, Markdown, TXT, and JSON, and these two are the ones that carry a document design.
You publish blog posts, landing pages, and pillar articles on a regular schedule. You need FAQ sections that answer distinct reader questions, CTAs for conversion, and real-time word count tracking to hit your target lengths. The content editor gives you all of these as insertable blocks so you spend time on strategy instead of formatting. Quick AI actions let you tighten prose or adjust tone without switching to a separate tool.
You produce content for multiple clients, each with different formatting requirements. One client needs checklists and step guides. Another wants pros/cons tables and key takeaway boxes. Instead of rebuilding these structures in a basic text editor for every deliverable, you select the block type, fill in the content, and export. The editor handles layout consistency across every piece you produce.
You document features, write how-to guides, and create knowledge base articles. Your content is inherently structured: definitions, step sequences, callouts, and code snippets. The block-based editor mirrors how your readers consume documentation. You compose in structured blocks, and the output is immediately scannable without post-production formatting.
The floating toolbar appears when you select text or position your cursor in a block. It includes controls for headings (H1 through H4), bold, italic, bulleted lists, numbered lists, tables, links, text alignment, and find/replace. Every formatting action is applied directly to the content block you are editing. There is no mode switching between "edit mode" and "preview mode." Preview the chosen export or CMS destination too: fonts, pagination and supported formatting can differ.
Three AI actions sit inside the same toolbar you use for formatting. Select a paragraph and click Rewrite to get an alternative version to review. Click Simplify to reduce complexity and reading level. Expand adds supporting detail to a thin section. Ask Power Edit to correct grammar and punctuation or to adjust the tone of the selected text. Each action operates on your selection, preserves the surrounding content, and returns the result inline. You accept or reject with one click. Nothing here is a chat window you copy out of — the AI works on your text, inside your editor. When you want more than a preset action you can type your own instruction with Power Edit, or ask for a set of changes across the whole piece with Ask Quill and keep only the ones that help.
Inside Quill
Updated