Skip to content
Loom
Menu

Semantic composition

Combine files into one document—not one pile of text.

Arrange chapters, preview the resulting outline, resolve cross-file structure, and generate a reproducible composition without overwriting its editable source entries.

Open the merger Read the merge guide

Product manual

Composition draft

4 files
  1. 01Welcome.mdClean
  2. 02Install.md1 link
  3. 03Configuration.md2 headings
  4. 04Reference.mdClean
14 headings · 22 links · 7 assets · 3 warnings

Composition intelligence

Understand every file boundary before it disappears

A semantic merge parses each source separately, applies a deterministic policy, and attributes each merge diagnostic to its source file.

01

Heading hierarchy

Apply explicit per-file offsets and warn when a heading must be capped at level one or six.

02

Relative links

Rewrite relative document and asset paths into a deterministic per-source namespace.

03

Reference labels

Detect duplicate reference definitions and namespace generated labels by source.

04

Footnotes

Detect colliding identifiers and namespace them in the generated result.

05

Front matter

Choose one document policy instead of concatenating metadata blocks.

06

Assets

Validate local files, detect missing paths, and carry safe media into a bundle.

Rearrange safely

File order and document outline, side by side.

Move sources with accessible up/down buttons or drag-and-drop, then inspect the merged preview and preflight diagnostics. Source edits and composition settings remain separate fields in the workbench.

Open the merger

Source order

  1. 1overview.md
  2. 2workflow.md
  3. 3api.md
  4. 4appendix.md

Resulting outline

  1. Product manual
  2. Overview
  3. Workflow
  4. Daily use
  5. API reference
  6. Appendix
1 heading jump needs review

Questions

Before you combine important source

Does merging change my original files?

No. The workbench keeps source entries, order, inclusion, heading offsets, separator policy, and output settings separate from the generated Markdown. Downloading the result or bundle does not overwrite an imported file.

What happens to duplicate headings and anchors?

MDLoom reports duplicate generated heading anchors. The shared renderer numbers repeated anchors deterministically, while reference and footnote identifiers are namespaced in generated Markdown.

Can the merged result include images?

Yes, after you attach local asset files to the relevant source. Captured files are copied into that source's bundle namespace; unresolved relative images remain warnings. Remote assets are not fetched.

Which outputs can a composition create?

The merger downloads merged Markdown, standalone HTML, or a portable ZIP containing generated Markdown, source entries, attached assets, a manifest, and diagnostics. When the connected isolated worker reports the format ready, the same merged snapshot can also produce canonical PDF, DOCX, ODT, or EPUB.

How do images in Markdown files work?

Use Add files and select the Markdown together with the image files it references. The file picker only receives what you choose, so a picture next to the .md on disk is not included unless you pick that picture too.