Workflow-specific products Content, decks, visuals, briefs, proposals, legal, books, and project delivery each have a clearer buying path.
Review before delivery Draft, edit, collaborate, approve, and export in the same workspace.
Security + procurement path Security policy, support, and Azure Marketplace buying are public.

Quill output sample

Inspect the artifact, not just the promise.

Open the 36-page finished PDF, a real Quill export, and inspect the product screens behind the workflow. It is a sample guide, not verified subject-matter advice or a customer result.

The PDF opens in a new tab. Product screens below open at their original image size.

Compare the authored source revision against the downloaded HTML, PDF and Word files

An output sample is most useful when you can inspect the exact input alongside the finished file. For web publication, compare the structured source record with the rendered desktop and mobile HTML views; for document exports, compare the imported Markdown manuscript with the paginated PDF and editable Word file.

Compare the authored source revision against the downloaded HTML, PDF and Word files
ArtifactWhat to inspect
Supplied web source JSONContains the exact sections, comparison table rows, FAQ items, layout key and theme key passed to the HTML renderer.
Blog HTML (Guide + Botanical)Sticky section navigation, responsive comparison table and phone-width reflow at 390×844 without horizontal scroll.
Webpage HTML (Bento + Heritage)Bento grid cards, session outline anchor jump and expandable details blocks opened directly in the browser.
Document PDF & DOCXPreserved headings, inserted Tip block, Power Edit paragraph replacement and Image Studio illustration across fixed A4 pages and Word styles.

The two HTML files are deterministic exports from authored instructional inputs, not unreviewed AI customer pages or live third-party websites.

A worked workflow

Import, selected-text editing and a structured handoff

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.

Follow the imported guide and web source into the saved HTML, PDF and Word exports

The fictional field-service guide was imported with headings, a table and a checklist, edited with a Pro Tip block, a Power Edit revision of the escalation-protocol paragraph and an Image Studio illustration, and exported to PDF and Word. Alongside it, two authored web sources were rendered through Quill's responsive HTML designer (Guide + Botanical blog layout and Bento + Heritage webpage composition) and inspected at desktop (1440×1050) and mobile (390×844) widths.

Desktop view of the downloaded Guide + Botanical blog HTML
Actual HTML article export at 1440×1050 showing section navigation and comparison table. Open full size ↗
Mobile view of the downloaded Guide + Botanical blog HTML at 390×844
Same portable HTML file opened independently at phone width (390×844). Open full size ↗
Desktop view of the downloaded Bento + Heritage webpage HTML
Actual HTML webpage export at 1440×1050 for the fictional Fieldnote Workshop. Open full size ↗
Mobile view of the downloaded Bento + Heritage webpage HTML at 390×844
Same portable webpage HTML reflowing at phone width (390×844). Open full size ↗
First page of the actual exported Quill field-service guide
Actual PDF export from the captured import, edit and save workflow. Open full size ↗
Second page of the actual Quill export showing the retained table and checklist
The original exported file remains available for inspecting structure and the applied passage. Open full size ↗

The HTML files are deterministic exports from the authored source JSON using Quill's production HTML helpers, embedded CSS and font links; hosted images keep their URLs and no external CMS or form backend is implied.

The supplied brief

Source structure
One heading, a three-step list, a two-column table and a caption with attribution.
Edit boundary
Select only the unclear paragraph and request a shorter explanation for a first-time reader.
Block requirement
Insert a structured comparison block with supplied item names and criteria.
Image requirement
Use an approved image or a clearly identified new result, with appropriate attribution and alternative text.
  1. Inspect the imported structure

    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.

  2. Edit only the intended selection

    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.

  3. Build the structured block

    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.

  4. Review an image revision

    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.

  5. Compare the exported formats

    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.

Before approving the result

  • Compare the selected paragraph and untouched surrounding text.
  • Read the inserted block and image alternative text.
  • Inspect the actual downloaded file after changing export settings.

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.

Start with your source

Check the structure before you change the wording.

The fictional Northwind field-service source contains four headings, a four-column table and four checklist lines. The original Markdown is available alongside its edited PDF and Word result. Check the cells and checklist markers separately from the later prose edits.

Original Northwind Guide article: service table on desktop and a readable checklist excerpt on phones
Original source rendered through the current Markdown pipeline and Guide + Modern SaaS HTML exporter. The phone preview focuses on the checklist; open the HTML to inspect every table column. The edited production PDF and Word are a separate saved revision from 21 October.

Inspect the same source in three places

  1. Before import: read the supplied headings, the three service tiers and the four checklist lines. Keep the source file.
  2. After import: compare the actual editor content. Check all four table columns and the checked/unchecked markers; upload success alone does not establish a lossless import.
  3. After editing: inspect the saved paragraph and inserted Tip in the PDF or Word result. The edited escalation paragraph differs from the original, so these files are not interchangeable source snapshots.

This retained run demonstrates one fictional Markdown import and later editing. It does not establish identical fidelity for scanned PDFs, spreadsheets, OCR, audio or every Word document.

PDF · 36 pages

The Definitive Guide to AI Flowchart Generators

A downloadable long-form Quill export on A4, with a cover page, a contents list and illustrated pages. Use it to assess information hierarchy, layout, scanability, and whether the finished artifact matches the standard your team needs. It is a sample article made for this purpose, not verified subject-matter advice.

View the complete PDF

Four more finished articles

Different briefs, different formats, the same export.

Each article was generated in Quill on 3 October 2026 from the brief shown, with sources Quill found itself, and exported as a PDF and a Word file without editing. They are samples, not verified advice. Before publishing, an independent AI reviewer checked about twenty claims in each against the pages it cites: none contradicted a cited page, and a few were not fully supported by the page cited.

A page of the home emergency kit guide: a tip box and a troubleshooting table listing common problems, how to recognise each and what to do. How-to guide · Technical template · 12 pages

How to Build a Home Emergency Kit

A step-by-step guide with a skill level, a materials list, safety notes, numbered steps and a troubleshooting table, grounded in the Ready.gov, FEMA and American Red Cross pages it cites.

The brief Quill was given

Write a practical how-to guide for a household building an emergency supplies kit. Explain what the kit is for, how to decide what to include, where to store it, how to keep it current, and what to add for children, older adults and pets. Ground the guidance in Ready.gov and the American Red Cross, and cite those pages. Do not state quantities, time estimates or any other figure unless a cited page gives it.

PDF · Word

A page of the pre-launch checklist: pre-task preparation and main checklist items, each with a checkbox and a High or Medium priority tag. Checklist · Newsletter template · 7 pages

Pre-Launch Checklist for a New Business Website

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.

The brief Quill was given

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.

PDF · Word

A page of the comparison: a criterion table for static site generator and headless CMS with a category-winners paragraph, above the start of the performance and hosting section. Comparison · Executive template · 12 pages

Static Site Generator or Headless CMS for a Marketing Website?

A balanced comparison with a feature-by-feature table, pros and cons, lock-in and migration risks, and a plain statement of which situations favour each option.

The brief Quill was given

Write a balanced comparison of building a marketing website with a static site generator and building it with a headless content management system. Compare authoring workflow, who can publish without a developer, performance and hosting, preview and review, cost of ownership, and the lock-in and migration risks. Say plainly which situations favour each option. Describe the approaches rather than ranking named products, and cite documentation from MDN Web Docs, web.dev and the Jamstack site, plus the platforms' own documentation pages, rather than third-party blog posts.

PDF · Word

The first page of the food waste article: the title, an introduction that names EPA, USDA and FoodSafety.gov, and the start of a ranked table of nine strategies. Listicle · Magazine editorial template · 9 pages

9 Practical Ways to Reduce Food Waste at Home

Nine numbered tips, each saying what to do, why it works and how to start, with a ranked summary table and EPA, USDA and FoodSafety.gov guidance linked in the text.

The brief Quill was given

Write a numbered article of nine practical ways a household can reduce the food it throws away. Each item should say what to do, why it works and how to start. Include how to plan meals, store food, read date labels, use leftovers and handle scraps. Ground the advice in guidance published by the U.S. Environmental Protection Agency, the U.S. Department of Agriculture and FoodSafety.gov, and cite those agency pages. Cite no other organisation. Do not quote statistics, percentages or dollar amounts; give practical advice and attribute each piece of guidance to the agency page it comes from.

PDF · Word

Responsive HTML outputs

Inspect the blog layout and the webpage outside the editor.

These two authored sources were exported with Quill's production HTML helpers, styles and embedded fonts. They demonstrate presentation and file delivery; they are not AI-generated customer work or proof of publishing to an external CMS.

Guide blog layout with Botanical colors, section navigation and a comparison table Blog / article · Guide + Botanical

Choose a blog layout for the reader's job

A worked explanation of the six article layouts, independent theme selection and HTML delivery. Try the section navigation and read the layout table at phone width.

Open HTML · Download HTML · Mobile 390px preview · Source JSON

Bento webpage composition with Heritage typography and a fictional workshop outline Webpage · Bento + Heritage

Fieldnote Workshop

A fictional workshop page with an opening, three exercises and expandable questions. The button moves to the session outline; no booking or submission service is connected.

Open HTML · Download HTML · Mobile 390px preview · Source JSON

Follow the blog and webpage export walkthrough or compare Quill's blog layouts and web design options. Downloading HTML gives you a file; hosting, domain configuration, analytics and a destination sitemap are separate tasks.

Compare the authored source revision against the downloaded HTML, PDF and Word files

An output sample is most useful when you can inspect the exact input alongside the finished file. For web publication, compare the structured source record with the rendered desktop and mobile HTML views; for document exports, compare the imported Markdown manuscript with the paginated PDF and editable Word file.

Compare the authored source revision against the downloaded HTML, PDF and Word files
ArtifactWhat to inspect
Supplied web source JSONContains the exact sections, comparison table rows, FAQ items, layout key and theme key passed to the HTML renderer.
Blog HTML (Guide + Botanical)Sticky section navigation, responsive comparison table and phone-width reflow at 390×844 without horizontal scroll.
Webpage HTML (Bento + Heritage)Bento grid cards, session outline anchor jump and expandable details blocks opened directly in the browser.
Document PDF & DOCXPreserved headings, inserted Tip block, Power Edit paragraph replacement and Image Studio illustration across fixed A4 pages and Word styles.

The two HTML files are deterministic exports from authored instructional inputs, not unreviewed AI customer pages or live third-party websites.

A worked workflow

Import, selected-text editing and a structured handoff

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.

Follow the imported guide and web source into the saved HTML, PDF and Word exports

The fictional field-service guide was imported with headings, a table and a checklist, edited with a Pro Tip block, a Power Edit revision of the escalation-protocol paragraph and an Image Studio illustration, and exported to PDF and Word. Alongside it, two authored web sources were rendered through Quill's responsive HTML designer (Guide + Botanical blog layout and Bento + Heritage webpage composition) and inspected at desktop (1440×1050) and mobile (390×844) widths.

Desktop view of the downloaded Guide + Botanical blog HTML
Actual HTML article export at 1440×1050 showing section navigation and comparison table. Open full size ↗
Mobile view of the downloaded Guide + Botanical blog HTML at 390×844
Same portable HTML file opened independently at phone width (390×844). Open full size ↗
Desktop view of the downloaded Bento + Heritage webpage HTML
Actual HTML webpage export at 1440×1050 for the fictional Fieldnote Workshop. Open full size ↗
Mobile view of the downloaded Bento + Heritage webpage HTML at 390×844
Same portable webpage HTML reflowing at phone width (390×844). Open full size ↗
First page of the actual exported Quill field-service guide
Actual PDF export from the captured import, edit and save workflow. Open full size ↗
Second page of the actual Quill export showing the retained table and checklist
The original exported file remains available for inspecting structure and the applied passage. Open full size ↗

The HTML files are deterministic exports from the authored source JSON using Quill's production HTML helpers, embedded CSS and font links; hosted images keep their URLs and no external CMS or form backend is implied.

The supplied brief

Source structure
One heading, a three-step list, a two-column table and a caption with attribution.
Edit boundary
Select only the unclear paragraph and request a shorter explanation for a first-time reader.
Block requirement
Insert a structured comparison block with supplied item names and criteria.
Image requirement
Use an approved image or a clearly identified new result, with appropriate attribution and alternative text.
  1. Inspect the imported structure

    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.

  2. Edit only the intended selection

    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.

  3. Build the structured block

    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.

  4. Review an image revision

    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.

  5. Compare the exported formats

    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.

Before approving the result

  • Compare the selected paragraph and untouched surrounding text.
  • Read the inserted block and image alternative text.
  • Inspect the actual downloaded file after changing export settings.

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.

Guided product tour

Follow one document from source choice to delivery.

Open each step to inspect the controls Quill keeps around the draft. This tour uses current product screens; it does not simulate generation or invent a customer outcome.

  1. 01 Bring in source material Start from what the team already knows.

    Paste existing text, upload a document, import Markdown, transcribe media, or bring in a URL before moving into the writing workflow.

    • Paste or upload source material
    • Import from a URL or Markdown
    • Keep the imported material editable
    Current Gixo import screen with paste, file, Markdown, URL, OCR, and transcription entry paths for Quill
  2. 02 Choose a structured format Match the document shape to the reader's job.

    Select the content format before generation so the first draft arrives with a useful information hierarchy rather than an undifferentiated text block.

    • Select the publishing job
    • Review the format structure
    • Keep the draft editable after generation
    Gixo Quill format picker with structured content starting points
  3. 03 Inspect captured sources Keep provenance beside the document.

    Review the web sources captured during generation, their retrieval dates, and citation labels while editing. Quill keeps the grounding material attached; it does not re-verify it after the artifact is written.

    • Inspect captured sources
    • Review source type and retrieval date
    • Keep grounding separate from factual verification
    Current Gixo Quill Sources panel with three captured web sources and the provenance boundary
  4. 04 Run content and SEO checks Surface concrete signals before delivery.

    Use the current Writing Help checks to inspect content health, SEO, readability, headings, images, and specific findings. These checks guide editorial work; they do not guarantee rankings.

    • Review the health summary
    • Open the relevant check family
    • Resolve useful findings in the draft
    Current Gixo Quill checks panel beside a sample draft, with a draft-health score and the specific findings to review
  5. 05 Edit a passage in context Keep formatting and AI actions beside selected text.

    This current console shows the real sample opening selected with the toolbar and writing brief visible. Quick AI offers preset actions; Power Edit takes your own instruction. No text edit was requested for this screen.

    • Select the passage
    • Inspect the formatting and AI controls
    • Keep the writing brief beside the draft
    Current Quill editing console with selected sample text, formatting and AI controls, and Writing help Brief
  6. 06 Describe an article-level change Ask Quill keeps the current article scope visible.

    The instruction shown was prepared and left unsubmitted. In the working flow, Ask Quill proposes changes for you to inspect and select before applying them; this capture demonstrates the request controls rather than a generated proposal.

    • Check the current article scope
    • Describe the change you want
    • Review a proposal before application
    Ask Quill instruction dialog with current article scope, prepared request and Suggest changes
  7. 07 Prepare threaded review Keep ownership and feedback attached to the artifact.

    Set review state, assignment, due date, teammate notification, and anchored feedback in the same workspace. The request shown here was typed but not sent.

    • Set the review state
    • Choose an owner and due date
    • Anchor feedback before submission
    Current Gixo Quill review composer with an unsent request, review state, assignment, due date, and notification controls
  8. 08 Choose the delivery path Carry the approved artifact into publishing metadata.

    Prepare metadata and choose an available delivery path. In the current saved-article form, Medium is draft-only and scheduling or queueing belongs to Gixo Blog. Connected WordPress and Ghost can receive a draft or an immediate publication; schedule external drafts inside the CMS. The earlier capture shows the publishing workspace, rather than proving every destination offers every mode.

    • Choose an available delivery destination
    • Complete SEO metadata
    • Check the modes offered for that destination
    Current Gixo Quill Publish Content dialog with destinations and SEO title, slug, meta description and focus keyword fields

Product evidence

Browse Quill output samples and workflow screenshots.

Filter existing public Quill assets by workflow stage, open any screen at its original size, and use the inspection notes to evaluate it. Output specimens demonstrate structure and presentation—not verified subject-matter advice or a customer result.

Evaluation checklist

What to check before you start.

Grounding

Can a reviewer trace important claims?

Look for visible source scope, evidence, references, and a clear distinction between drafting assistance and source authority.

Structure

Does the output survive scanning?

Check heading hierarchy, callouts, lists, section length, and whether the exported artifact remains readable outside the editor.

Review

Can a team finish the work in context?

Inspect comments, status, assignment, due dates, and the path from editing to export or publishing.

Self-service from first draft to delivery

Bring a source, choose a format, and keep the review trail attached.

Start a 14-day, no-card trial to use Quill's generation and review workflow. Prefer to inspect first? The Content Health Check stays free and anonymous.