Find your next document example

Input

Project scope and milestone data

Output

DOCX + PDF

What to check

The linked C# example generates this file. The runner reopens and validates the DOCX, exports a PDF, and the preview renders that PDF.

Scope

The bookmark is part of the DOCX structure. The PDF preview demonstrates page layout; it does not expose Word bookmark navigation.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example word-project-charter

Input

Volume, unit price, and fixed-cost assumptions

Output

XLSX

What to check

The linked C# example generates this file. The runner reopens and validates the XLSX. The image is a native rendering of the specified worksheet range.

Scope

Contribution here is units multiplied by price minus fixed cost. Variable costs, tax, and cash timing are outside this small model. The calculation is split into cells supported by the native formula engine; more complex expressions may need a spreadsheet application.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example excel-budget-scenarios

Input

Project phases, activities, and decision gates

Output

PPTX + PDF

What to check

The linked C# example generates this file. The runner reopens and validates the PPTX, then exports each slide and a PDF review copy.

Scope

Previews show OfficeIMO's rendering of the generated slides. Fonts and layout can differ in other presentation applications.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example powerpoint-project-roadmap

Input

Workshop objectives, agenda, and exercise prompts

Output

PDF

What to check

The linked C# example generates this file. The page images are rendered from the downloadable PDF with Poppler.

Scope

The writing lines are static page content. This example does not create fillable PDF form fields.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example pdf-workshop-pack

Input

Response steps, ownership, and communication guidance

Output

MD + PDF

What to check

The linked C# example generates this file. The Markdown builder creates the source file. The runner exports a PDF, which is rendered for the preview.

Scope

The content is a sample runbook, not a validated response procedure for your service. PDF export is a separate rendering step.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example markdown-incident-runbook

Input

Meeting details, decisions, and action items

Output

DOCX + PDF

What to check

The linked C# example generates this file. The runner reopens and validates the DOCX, exports a PDF, and the preview renders that PDF.

Scope

The sample is an editable meeting record. It does not create calendar events, send reminders, or synchronize action status.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example word-meeting-minutes

Input

Onboarding stages and assigned tasks

Output

DOCX + PDF

What to check

The linked C# example generates this file. The runner reopens and validates the DOCX, exports a PDF, and the preview renders that PDF.

Scope

Status values are ordinary editable table text. This sample does not implement interactive checkbox controls or an approval workflow.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example word-onboarding-checklist

Input

Working agreements and review ownership

Output

DOCX + PDF

What to check

The linked C# example generates this file. The runner reopens and validates the DOCX, exports a PDF, and the preview renders that PDF.

Scope

This is a formatting and authoring example with fictional workplace content. It does not supply an organization's approved policy or enforce compliance.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example word-policy-brief

Input

Decision context and evaluated options

Output

DOCX + PDF

What to check

The linked C# example generates this file. The runner reopens and validates the DOCX, exports a PDF, and the preview renders that PDF.

Scope

The example records a decision in a document. It does not calculate option scores or collect electronic approvals.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example word-decision-record

Input

Quantity, unit price, and discount rate

Output

XLSX

What to check

The linked C# example generates this file. The runner reopens and validates the XLSX. The image is a native rendering of the specified worksheet range.

Scope

The sample demonstrates one workbook-level calculation. It does not implement a pricing policy, tax engine, or negotiated-price approval process. Each calculation step uses the native formula engine supported by this example.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example excel-named-range-pricing

Input

Planned and used days by workstream

Output

XLSX

What to check

The linked C# example generates this file. The runner reopens and validates the XLSX. The image is a native rendering of the specified worksheet range.

Scope

The image shows the Summary sheet. Open the XLSX to inspect and edit Delivery; the preview is not an interactive workbook.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example excel-project-workbook

Input

Expense dates, categories, amounts, and review status

Output

XLSX

What to check

The linked C# example generates this file. The runner reopens and validates the XLSX. The image is a native rendering of the specified worksheet range.

Scope

Dropdown validation guides entry in a spreadsheet application. It is not a security boundary or an expense approval service.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example excel-expense-register

Input

An array of typed asset records

Output

XLSX

What to check

The linked C# example generates this file. The runner reopens and validates the XLSX. The image is a native rendering of the specified worksheet range.

Scope

The sample uses ten flat records with dates, numbers and text. It is not a benchmark or a demonstration of streaming a large database result.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example excel-object-export

Input

Typed invoice parties, line items, tax, payment, branding, and approval details

Output

Two-page PDF with embedded CII XML

What to check

The example generates the PDF and XML from one captured invoice. The runner reopens the PDF, checks its visible text, and renders both page previews with Poppler.

Scope

Seller identifiers, bank details, and the buyer are non-operational sample data. Approval blocks are visible content, not cryptographic signatures. The showcase does not claim Factur-X or PDF/A conformance without external validation of the exact artifact.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example pdf-branded-invoice

Input

Shipment reference, item rows, and receiving instructions

Output

PDF

What to check

The linked C# example generates this file. The page images are rendered from the downloadable PDF with Poppler.

Scope

The receipt area is printed text, not an interactive form or digital signature field. Sample data does not represent a real shipment.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example pdf-dispatch-note

Input

Three service offerings and their intended use

Output

PDF

What to check

The linked C# example generates this file. The page images are rendered from the downloadable PDF with Poppler.

Scope

The offerings are fictional sample content. The layout demonstrates fixed PDF output rather than a responsive web pricing component.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example pdf-service-catalog

Input

Weekly progress, risks, and next actions

Output

PDF

What to check

The linked C# example generates this file. The page images are rendered from the downloadable PDF with Poppler.

Scope

The numbers and actions are demonstration data. This example formats a report; it does not collect live service telemetry.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example pdf-weekly-brief

Input

A training question, explanation, and discussion prompts

Output

PPTX + PDF

What to check

The linked C# example generates this file. The runner reopens and validates the PPTX, then exports each slide and a PDF review copy.

Scope

This is a static presentation. It does not score answers, record attendance, or implement clickable quiz branching.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example powerpoint-training-quiz

Input

Service ownership and handover tasks

Output

PPTX + PDF

What to check

The linked C# example generates this file. The runner reopens and validates the PPTX, then exports each slide and a PDF review copy.

Scope

The checklist is presentation content. It does not provision a service or transfer operational permissions.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example powerpoint-service-overview

Input

An architectural choice and the reasons behind it

Output

MD + PDF

What to check

The linked C# example generates this file. The Markdown builder creates the source file. The runner exports a PDF, which is rendered for the preview.

Scope

The report-bundle design is illustrative. This example writes the decision record; it does not create or hash a report bundle.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example markdown-decision-record

Input

Request fields, example payloads, and integration notes

Output

MD + PDF

What to check

The linked C# example generates this file. The Markdown builder creates the source file. The runner exports a PDF, which is rendered for the preview.

Scope

The Northwind API is fictional. The example generates documentation and does not make network requests or validate an OpenAPI specification.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example markdown-api-handover

Input

Brand brief + content

Output

PPTX

What to check

The downloadable deck is generated by the linked example and passes Open XML validation. The preview is a rendered slide from that example.

Scope

This proves package structure and the selected rendered slide. It does not promise pixel parity with every PowerPoint desktop version, font set, or theme.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --powerpoint-design-brief

Input

PowerShell objects

Output

DOCX + PDF

What to check

The downloadable DOCX and PDF come from the PowerShell script shown beside them, run against the PSWriteOffice version the command catalog documents. The preview is an independent Poppler render of that PDF.

Scope

The inventory in the script is sample data. The report uses the PSWriteOffice Word cmdlets and its built-in table style; the PDF is the first-party OfficeIMO conversion of the DOCX, so pagination can differ from Microsoft Word.

View code: Patch compliance report from PowerShell: follow the input, calculations and document code in the walkthrough.

Input

Synthetic CSV snapshot

Output

XLSX + DOCX + PDF

What to check

The script and CSV generate all three native files with the PSWriteOffice version documented by the command catalog. The PNG is an independent Poppler render of the PDF.

Scope

The data is synthetic. The Word/PDF review is a dated snapshot; regenerate it after changing the input. Larger inputs can span several pages. Check pagination and fonts before distributing the PDF.

View code: Project delivery and milestones: follow the input, calculations and document code in the walkthrough.

Input

Synthetic CSV snapshot

Output

XLSX + DOCX + PDF

What to check

The script and CSV generate all three native files with the PSWriteOffice version documented by the command catalog. The PNG is an independent Poppler render of the PDF.

Scope

The data is synthetic. The Word/PDF review is a dated snapshot; regenerate it after changing the input. Larger inputs can span several pages. Check pagination and fonts before distributing the PDF.

View code: Budget and forecast review: follow the input, calculations and document code in the walkthrough.

Input

Metrics, monthly volumes and service-line rows

Output

PDF

What to check

The PDF is generated by one runnable example and the page image is an independent Poppler render of that same file.

Scope

Standard PDF fonts are portable but intentionally narrower than arbitrary installed-font typography and full browser layout.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --pdf-showcase

Input

HTML + CSS

Output

PDF / PNG / SVG

What to check

One-page PDF generated from the linked HTML input. PNG and SVG are native renderer outputs.

Scope

These samples cover linear and radial paint. Conic-gradient output has a separate raster seam limitation.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --html-feature-showcase

Input

Typed sales rows + a title object

Output

XLSX + PNG

What to check

The XLSX and PNG come from the same runnable example. The workbook is saved even when a downstream conversion preflight blocks an unsafe claim.

Scope

The bundled diagnostic shows the real boundary: first-party PDF export is blocked while pivot output exists only as pivot metadata instead of materialized cells.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --excel-report-workflow

Input

Project data + decisions

Output

DOCX → PDF

What to check

The downloadable DOCX and PDF are generated from one runnable Word example. The preview is an independent Poppler render of the first-party PDF result.

Scope

The proof covers the generated document and its first PDF page. Exact pagination can still vary when callers opt into different installed fonts or introduce unsupported Word layout features.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-real-world

Input

Topology model

Output

VSDX + PNG

What to check

The VSDX is generated and structurally validated by the premium gallery. The image is the approved native-renderer baseline for the same scenario.

Scope

The native preview is intended for CI and review. Microsoft Visio desktop remains the authority for exact stencil and desktop-rendering parity.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --visio-premium

Input

HTML + CSS + policy

Output

PDF / PNG / SVG

What to check

The HTML, PDF, PNG, and SVG are emitted by one runnable example. The PDF retains searchable text, named page-margin content, vector gradients, MathML, and four AcroForm fields.

Scope

This is a deterministic document renderer, not a JavaScript or browser runtime. Advanced print-production features such as page floats, footnotes, cross-references, and crop or bleed marks remain outside this proof.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --html-renderer-gallery

Input

Purchase data → finalized HTML

Output

PDF / PNG / SVG

What to check

The downloadable searchable PDF spans multiple pages and is generated with the preview PNG from the same data-bound HTML document and options object by the linked runnable example.

Scope

PDF object and completed-page serialization are bounded and forward-only in this example. HTML parsing, cascade, and layout still use the complete static document; scripts are not executed.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --html-invoice

Input

Change record

Output

RTF → PDF

What to check

The downloadable RTF and PDF come from the same OfficeIMO.Rtf model. The preview independently renders the first-party conversion result.

Scope

The memo content is sample data. The RTF model targets documented, portable structures. Desktop-specific RTF extensions, legacy drawing objects, and arbitrary embedded resources remain bounded conversion cases.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-real-world

Input

Release evidence

Output

Markdown → PDF

What to check

The Markdown source and themed PDF are generated from one document model. The preview is an independent render of the first-party PDF.

Scope

The release data is sample content. The PDF path supports OfficeIMO's documented Markdown blocks and themes. Raw browser HTML, arbitrary scripts, and unsupported extensions require an explicit conversion policy.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-real-world

Input

Handover model

Output

ODT → PDF

What to check

The ODT and PDF are generated by the same runnable example. The preview independently renders the first page of the first-party OpenDocument conversion.

Scope

The handover content is sample data. The converter maps the supported OpenDocument text model into the shared Word/PDF layout path. Advanced LibreOffice-only layout and macro behavior are outside this proof.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-real-world

Input

PPTX in this proof

Output

Reader JSON

What to check

The bundled schema-versioned JSON is generated by the OfficeIMO.Tool Reader command from the downloadable PowerPoint deck; the preview lists its four extracted slide headings.

Scope

Extraction preserves useful structure, not every visual placement. OCR and hosted providers are separate, explicitly configured capabilities.

officeimo reader read - --name design-brief.pptx --format json

Input

Page model or ONE

Output

ONE / ONEPKG / PDF

What to check

The preview reproduces the bundled HTML export. The downloadable ONEPKG and PDF are generated from the same in-memory section.

Scope

The offline model targets documented structures and supported page content; it does not claim complete OneNote desktop rendering or cloud-sync behavior.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --onenote

Input

HTML + CSS

Output

PDF / PNG / SVG

What to check

One-page PDF generated from the linked HTML input. PNG and SVG are native renderer outputs.

Scope

A fixed A4 landscape document. This does not demonstrate interactive or responsive browser behavior.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --html-feature-showcase

Input

HTML + CSS

Output

PDF / PNG / SVG

What to check

One-page PDF generated from the linked HTML input. PNG and SVG are native renderer outputs.

Scope

The PDF contains four interactive fields. PNG and SVG are static previews; PDF form behavior depends on the viewer.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --html-feature-showcase

Input

HTML + CSS

Output

PDF / PNG / SVG

What to check

One-page PDF generated from the linked HTML input. PNG and SVG are native renderer outputs.

Scope

Three bounded presentation MathML examples, not full MathML or TeX support.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --html-feature-showcase

Input

HTML + CSS

Output

PDF / PNG / SVG

What to check

One-page PDF generated from the linked HTML input. PNG and SVG are native renderer outputs.

Scope

The example uses Latin text and standard font families. Validate other scripts and font requirements separately.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --html-feature-showcase

Input

HTML + CSS

Output

PDF / PNG / SVG

What to check

One-page PDF generated from the linked HTML input. PNG and SVG are native renderer outputs.

Scope

Static shapes and paths in this fixture. External resources, SVG animation, and script execution are outside its scope.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --html-feature-showcase

Input

HTML + CSS

Output

PDF / PNG / SVG

What to check

One-page PDF generated from the linked HTML input. PNG and SVG are native renderer outputs.

Scope

A single-page table fixture. Check fragmentation separately for longer tables.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --html-feature-showcase

Input

HTML + CSS

Output

PDF / PNG / SVG

What to check

One-page PDF generated from the linked HTML input. PNG and SVG are native renderer outputs.

Scope

Static positioned content. The renderer does not execute JavaScript or animation.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --html-feature-showcase

Input

HTML + CSS

Output

PDF / PNG / SVG

What to check

Two-page PDF with an explicit page break. PNG and SVG are native renderer outputs.

Scope

The PDF has two pages. PNG and SVG downloads show the first page.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --html-feature-showcase

Input

Application data + C#

Output

DOCX / PDF

What to check

The preview is independently rendered from the generated PDF. Open the downloads for the full output.

Scope

A deterministic invoice fixture with three line items. The PDF is a first-party conversion of the DOCX.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-features --showcase-group word

Input

Application data + C#

Output

DOCX / PDF

What to check

The preview is independently rendered from the generated PDF. Open the downloads for the full output.

Scope

The input supplies subtotal values; this example demonstrates grouped row binding, not a calculation engine.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-features --showcase-group word

Input

Application data + C#

Output

DOCX / JSON report

What to check

The preview is independently rendered from the generated PDF. Open the downloads for the full output.

Scope

The preview shows the extracted review report, not Word desktop comment balloons or the source-document layout.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-features --showcase-group word

Input

Application data + C#

Output

Redline DOCX / Original DOCX

What to check

The preview is independently rendered from the generated PDF. Open the downloads for the full output.

Scope

The preview is the comparison report. Open the redline DOCX to inspect tracked edits in a document editor.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-features --showcase-group word

Input

Application data + C#

Output

XLSX

What to check

The example generates and validates the editable document. The preview is its native image export.

Scope

The workbook stores formulas and calculated values. This example uses arithmetic supported by the formula engine.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-features --showcase-group excel

Input

Application data + C#

Output

XLSX

What to check

The example generates and validates the editable document. The preview is its native image export.

Scope

The PNG shows cell contents. Filter controls and frozen panes are interactive workbook features.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-features --showcase-group excel

Input

Application data + C#

Output

XLSX

What to check

The example generates and validates the editable document. The preview is its native image export.

Scope

The native preview demonstrates this column-chart fixture, not every Excel chart type.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-features --showcase-group excel

Input

Application data + C#

Output

XLSX

What to check

The example generates and validates the editable document. The preview is its native image export.

Scope

Color depends on the numeric cell values. The fixture demonstrates a two-color scale.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-features --showcase-group excel

Input

Application data + C#

Output

XLSX

What to check

The example generates and validates the editable document. The preview is its native image export.

Scope

Validation rules live in the XLSX. The PNG is a static preview and cannot demonstrate dropdown interaction.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-features --showcase-group excel

Input

Application data + C#

Output

PPTX / PDF

What to check

The example generates and validates the editable document. The preview is its native image export.

Scope

The deck contains one generated table slide. Cells remain native PowerPoint table content.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-features --showcase-group powerpoint

Input

Application data + C#

Output

PPTX / PDF

What to check

The example generates and validates the editable document. The preview is its native image export.

Scope

The example uses static rectangles and text. No slide animation or image composition is required.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-features --showcase-group powerpoint

Input

Application data + C#

Output

PPTX / PDF

What to check

The example generates and validates the editable document. The preview is its native image export.

Scope

The sample demonstrates these text styles with the available fonts; other font sets can change metrics.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-features --showcase-group powerpoint

Input

Application data + C#

Output

PPTX / PDF

What to check

The example generates and validates the editable document. The preview is its native image export.

Scope

The preview shows slide three. The downloadable deck and PDF contain all three slides.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-features --showcase-group powerpoint

Input

Application data + C#

Output

PDF

What to check

The preview is independently rendered from the generated PDF. Open the downloads for the full output.

Scope

The preview shows page one. Open the PDF to inspect the full statement.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-features --showcase-group pdf

Input

Application data + C#

Output

PDF

What to check

The preview is independently rendered from the generated PDF. Open the downloads for the full output.

Scope

This fixture demonstrates the PDF layout DSL with standard fonts and explicit column widths.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-features --showcase-group pdf

Input

Application data + C#

Output

PDF

What to check

The preview is independently rendered from the generated PDF. Open the downloads for the full output.

Scope

Static drawing primitives in a PDF. The independent PNG preview is a raster view of the vector output.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-features --showcase-group pdf

Input

Application data + C#

Output

PDF

What to check

The preview is independently rendered from the generated PDF. Open the downloads for the full output.

Scope

The preview shows the first page. The PDF includes the complete style gallery.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-features --showcase-group pdf

Input

Application data + C#

Output

PDF / Merged PDF

What to check

The preview is independently rendered from the generated PDF. Open the downloads for the full output.

Scope

Open the merged, extracted, and stamped PDFs to compare the operations. The preview shows the stamped output.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-features --showcase-group pdf

Input

Application data + C#

Output

Markdown / PDF

What to check

The preview is independently rendered from the generated PDF. Open the downloads for the full output.

Scope

The preview is the generated PDF. Markdown remains the editable input.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-features --showcase-group markdown

Input

Research observations and source notes

Output

DOCX + PDF

What to check

The linked C# example generates this file. The runner reopens and validates the DOCX, exports a PDF, and renders every PDF page for review.

Scope

The observations are synthetic. DOCX footnote structure and the generated PDF are checked; behavior in a desktop Word editor is not part of this preview.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example word-research-brief

Input

Template field definitions and request values

Output

DOCX + PDF

What to check

The linked C# example generates this file. The runner reopens and validates the DOCX, exports a PDF, and renders every PDF page for review.

Scope

The PDF shows the completed request. Download the DOCX files to inspect the editable controls; this example does not add signatures, workflow approval or field locking.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example word-service-intake

Input

Evaluation narrative and a five-column evidence matrix

Output

DOCX + PDF

What to check

The linked C# example generates this file. The runner reopens and validates the DOCX, exports a PDF, and renders every PDF page for review.

Scope

The source and PDF demonstrate mixed page orientation. The sample comparison is illustrative and is not an endorsement of a supplier.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example word-mixed-orientation-report

Input

On-hand quantities, target stock and unit costs

Output

XLSX

What to check

The linked C# example generates this file. The runner reopens and validates the XLSX and checks supported formulas, cached results and dependencies. The PNG is a native worksheet-range export.

Scope

The calculation is a target-stock proposal using synthetic data. It does not submit purchases or account for delivery schedules.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example excel-inventory-reorder

Input

People, required modules and completion states

Output

XLSX

What to check

The linked C# example generates this file. The runner reopens and validates the XLSX and checks supported formulas, cached results and dependencies. The PNG is a native worksheet-range export.

Scope

The example records completion states, not accredited certification. The preview does not exercise Excel's interactive validation dropdown.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example excel-training-matrix

Input

Six weekly received and resolved counts

Output

XLSX

What to check

The linked C# example generates this file. The runner reopens and validates the XLSX and checks supported formulas, cached results and dependencies. The PNG is a native worksheet-range export.

Scope

The values are synthetic. The image is OfficeIMO's native worksheet rendering; desktop Excel chart appearance can differ.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example excel-operational-trends

Input

Inspection labels, a sample asset identifier and allowed dispositions

Output

PDF

What to check

The linked C# example generates this file. The page images are rendered from the downloadable PDF with Poppler. Interactive structures are inspected separately from the static preview.

Scope

This sample is not a safety certification. The PNG is a static preview; use a PDF viewer that supports AcroForm fields to complete the form.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example pdf-equipment-inspection

Input

Resource names, destinations and usage notes

Output

PDF

What to check

The linked C# example generates this file. The page images are rendered from the downloadable PDF with Poppler. Interactive structures are inspected separately from the static preview.

Scope

The PDF contains external link annotations. The image shows their labels and layout; it does not demonstrate navigation or guarantee future availability of external pages.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example pdf-linked-resource-guide

Input

Workshop stages, timings and follow-up guidance

Output

PDF

What to check

The linked C# example generates this file. The page images are rendered from the downloadable PDF with Poppler. Interactive structures are inspected separately from the static preview.

Scope

The generated PDF contains the navigation structure. Static page images show the layout; viewer-specific bookmark panels are not pictured.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example pdf-navigable-handbook

Input

Baseline and pilot response times plus decision notes

Output

PPTX + PDF

What to check

The linked C# example generates this file. The runner reopens and validates the PPTX, then exports each slide and a PDF review copy.

Scope

The data is invented. The PPTX preserves the chart and notes; PNG and PDF previews show slides rather than presenter mode.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example powerpoint-results-briefing

Input

Two support scenarios and their checklists

Output

PPTX + PDF

What to check

The linked C# example generates this file. The runner reopens and validates the PPTX, then exports each slide and a PDF review copy.

Scope

The PPTX contains internal slide relationships. The static previews do not prove presentation-mode interaction in Microsoft PowerPoint.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example powerpoint-branching-playbook

Input

An illustrative configuration change and its migration rules

Output

MD + PDF

What to check

The linked C# example generates this file. The Markdown source is reloaded and exported to PDF. Each PDF page is rendered for review.

Scope

The settings are a fictional application example, not OfficeIMO configuration. The PDF is a readable review copy of the Markdown.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example markdown-migration-guide

Input

A structured field catalog for a service request export

Output

MD + PDF

What to check

The linked C# example generates this file. The Markdown source is reloaded and exported to PDF. Each PDF page is rendered for review.

Scope

The export schema is fictional. The example generates documentation; it does not implement a JSON schema validator.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example markdown-data-dictionary

Input

Learner name, course title and completion details

Output

HTML + PDF

What to check

The linked C# example generates this file. The HTML document is exported through OfficeIMO.Html to PDF with a required successful save. Each PDF page is rendered for review.

Scope

This is an illustrative completion record, not professional accreditation or a digitally signed certificate. The preview is rendered from the PDF.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example html-course-certificate

Input

Measured values, targets, units and comparison direction

Output

HTML + PDF

What to check

The linked C# example generates this file. The HTML document is exported through OfficeIMO.Html to PDF with a required successful save. Each PDF page is rendered for review.

Scope

The values are synthetic. The report evaluates supplied numbers; it does not independently collect or verify service telemetry.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example html-service-level-report

Input

Proposed outcome, deliverables and acceptance conditions

Output

ODT + PDF

What to check

The linked C# example generates this file. The runner reopens the ODT and exports a PDF review copy. Each PDF page is rendered for review.

Scope

The ODT is reopened and converted by OfficeIMO for review. The preview does not certify identical pagination in every OpenDocument editor.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example opendocument-service-proposal

Input

Workshop timings, activities, outputs and preparation notes

Output

ODT + PDF

What to check

The linked C# example generates this file. The runner reopens the ODT and exports a PDF review copy. Each PDF page is rendered for review.

Scope

The sample demonstrates both serializations. It does not claim that text diffs are free of generated style changes or that all editors render them identically.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example opendocument-workshop-agenda

Input

A support symptom, diagnostic steps and evidence fields

Output

RTF + PDF

What to check

The linked C# example generates this file. The runner reloads the saved RTF and exports it to PDF. Each PDF page is rendered for review.

Scope

The example is an illustrative support procedure. PDF conversion demonstrates the supported RTF content in this file, not every RTF feature.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example rtf-support-bulletin

Input

Approval roles, process steps and labeled transitions

Output

VSDX + SVG

What to check

The linked C# example generates this file. The runner reloads the VSDX, checks the authoring model and renders the saved diagram to PNG and SVG.

Scope

The VSDX is validated and rendered by OfficeIMO. The preview does not demonstrate editing or routing behavior in desktop Visio.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example visio-approval-swimlane

Input

People, roles, reporting relationships and open positions

Output

VSDX + SVG

What to check

The linked C# example generates this file. The runner reloads the VSDX, checks the authoring model and renders the saved diagram to PNG and SVG.

Scope

The names and structure are fictional. Image evidence comes from OfficeIMO's renderer and does not establish identical layout in desktop Visio.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example visio-team-organisation

Input

Task durations, dependencies, and actual duration

Output

XML + PNG + SVG + PDF + DOCX

What to check

The complete C# example generates these exports. The runner reopens and validates the Project XML and any Office documents, and verifies the PDF page count. The preview is the actual 300-DPI PNG export.

Scope

Calculated report views do not reconstruct saved native Project view styles. Charts in Word and PowerPoint are images; accompanying data tables remain editable. PNG has a fixed pixel resolution; use SVG for vector zoom.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example project-delivery-gantt

Input

A fork-and-join dependency graph

Output

XML + PNG + SVG + PDF

What to check

The complete C# example generates these exports. The runner reopens and validates the Project XML and any Office documents, and verifies the PDF page count. The preview is the actual 300-DPI PNG export.

Scope

Calculated report views do not reconstruct saved native Project view styles. Charts in Word and PowerPoint are images; accompanying data tables remain editable. PNG has a fixed pixel resolution; use SVG for vector zoom.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example project-dependency-network

Input

Release phases and decision milestones

Output

XML + PNG + SVG + PDF + PPTX + XLSX

What to check

The complete C# example generates these exports. The runner reopens and validates the Project XML and any Office documents, and verifies the PDF page count. The preview is the actual 300-DPI PNG export.

Scope

Calculated report views do not reconstruct saved native Project view styles. Charts in Word and PowerPoint are images; accompanying data tables remain editable. PNG has a fixed pixel resolution; use SVG for vector zoom.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example project-milestone-timeline

Input

Options, estimated cost and expected saving

Output

DOCX + PDF

What to check

The C# source generates the downloadable file. The runner reopens the editable document, validates Open XML where applicable and exports a PDF. Page previews come from the generated output.

Scope

Replace sample amounts with an approved cost model; include ongoing support, tax and financing when relevant.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example word-business-case

Input

Service commitments and proposed commercial terms

Output

DOCX + PDF

What to check

The C# source generates the downloadable file. The runner reopens the editable document, validates Open XML where applicable and exports a PDF. Page previews come from the generated output.

Scope

Use agreed commercial terms and obtain the appropriate review before treating the proposal as a commitment.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example word-renewal-proposal

Input

Incident events and corrective actions

Output

DOCX + PDF

What to check

The C# source generates the downloadable file. The runner reopens the editable document, validates Open XML where applicable and exports a PDF. Page previews come from the generated output.

Scope

Replace the fictional timeline with verified events and distinguish observations from unconfirmed causes.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example word-post-incident-review

Input

Deliverables and acceptance criteria

Output

DOCX + PDF

What to check

The C# source generates the downloadable file. The runner reopens the editable document, validates Open XML where applicable and exports a PDF. Page previews come from the generated output.

Scope

Adapt the scope and acceptance criteria to the engagement; the sample is not a legal agreement.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example word-statement-of-work

Input

Opening cash, receipts and payments

Output

XLSX

What to check

The C# source generates the downloadable file. The runner validates the workbook and supported formulas, cached results and dependencies. The PNG is a native range export.

Scope

Use actual forecast assumptions and reconcile separately; this sample excludes tax and financing.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example excel-cash-flow-forecast

Input

Asset cost, residual value and useful life

Output

XLSX

What to check

The C# source generates the downloadable file. The runner validates the workbook and supported formulas, cached results and dependencies. The PNG is a native range export.

Scope

Confirm accounting policy separately. The sample assumes a full first year and cost above residual value.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example excel-asset-depreciation

Input

Criterion scores and agreed weights

Output

XLSX

What to check

The C# source generates the downloadable file. The runner validates the workbook and supported formulas, cached results and dependencies. The PNG is a native range export.

Scope

Agree criteria and weights before scoring, retain the supporting evidence and review conflicts of interest.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example excel-vendor-comparison

Input

Team members and daily shift codes

Output

XLSX

What to check

The C# source generates the downloadable file. The runner validates the workbook and supported formulas, cached results and dependencies. The PNG is a native range export.

Scope

Use your actual shift codes and staffing rules; this example does not validate working-time or leave policies.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example excel-workforce-rota

Input

Travel plan and workshop arrangements

Output

PDF

What to check

The C# source generates the downloadable file. The runner checks PDF text and pages; Poppler renders the page previews.

Scope

Confirm bookings and current transport information; keep personal references in a private copy.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example pdf-travel-itinerary

Input

Participant names, roles and event details

Output

PDF

What to check

The C# source generates the downloadable file. The runner checks PDF text and pages; Poppler renders the page previews.

Scope

Set the page size to the intended stock and check a physical print before producing a batch.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example pdf-event-badges

Input

Work order and completion record

Output

PDF

What to check

The C# source generates the downloadable file. The runner checks PDF text and pages; Poppler renders the page previews.

Scope

Replace the fields with your approved process; this example does not authorise work or define safety procedures.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example pdf-maintenance-job-card

Input

Delivery risks and proposed controls

Output

PDF

What to check

The C# source generates the downloadable file. The runner checks PDF text and pages; Poppler renders the page previews.

Scope

Replace illustrative judgments with evidence. This is a project review, not a workplace safety certification.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example pdf-risk-assessment

Input

Investment options and approval conditions

Output

PPTX + PDF

What to check

The C# source generates the downloadable file. The runner reopens the editable document, validates Open XML where applicable and exports a PDF. Page previews come from the generated output.

Scope

Use validated amounts and keep approval conditions in the actual governance record.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example powerpoint-board-decision

Input

Opportunity value by current stage

Output

PPTX + PDF

What to check

The C# source generates the downloadable file. The runner reopens the editable document, validates Open XML where applicable and exports a PDF. Page previews come from the generated output.

Scope

Use a dated CRM snapshot and a consistent currency; do not present the synthetic values as a forecast.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example powerpoint-sales-pipeline

Input

Team observations and proposed experiments

Output

PPTX + PDF

What to check

The C# source generates the downloadable file. The runner reopens the editable document, validates Open XML where applicable and exports a PDF. Page previews come from the generated output.

Scope

Use specific observations, agree owners and dates, and avoid treating an assigned action as completed work.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example powerpoint-retrospective

Input

Support states and acceptance decision

Output

VSDX

What to check

The C# source generates the downloadable file. The runner validates the diagram and exports native PNG and SVG previews.

Scope

Adapt the states and escalation rules to the service; the diagram does not execute tickets or changes.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example visio-triage-flow

Input

Starter milestones and team handovers

Output

VSDX

What to check

The C# source generates the downloadable file. The runner validates the diagram and exports native PNG and SVG previews.

Scope

Use approved onboarding steps; the example neither provisions accounts nor changes access.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example visio-onboarding-journey

Input

Readiness checks and release ownership

Output

MD + PDF

What to check

The C# source generates the downloadable file. The runner reopens the editable document, validates Open XML where applicable and exports a PDF. Page previews come from the generated output.

Scope

Use your release process and exact artifact identities; this document performs no publishing or deployment.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example markdown-release-checklist

Input

Recipient, appointment and preparation details

Output

ODT + PDF

What to check

The C# source generates the downloadable file. The runner reopens the editable document, validates Open XML where applicable and exports a PDF. Page previews come from the generated output.

Scope

Replace the invented appointment and contact route with confirmed arrangements.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example opendocument-client-letter

Input

Handover fields and communication guidance

Output

RTF + PDF

What to check

The C# source generates the downloadable file. The runner reopens the editable document, validates Open XML where applicable and exports a PDF. Page previews come from the generated output.

Scope

Adapt the fields and response promise to the service and keep personal data out of public examples.

dotnet run --project OfficeIMO.Examples -f net10.0 -- --showcase-workflows --showcase-example rtf-desk-reference