TL;DR — Use page breaks when a new section should start on a fresh page,
and add page numbers when the exported file will be reviewed, printed, or
referenced outside the editor. In depapel, both controls are opt-in Markdown
directives: <depapel-page-break/> starts a new page, and
<depapel-page-numbering/> turns page numbers on for PDF and DOCX output.
Markdown is best when the source stays readable.
That is why most layout controls should stay out of the way. You should not need
to write a full template system just to send a project brief, client handoff,
README export, or internal proposal.
But some documents do need a few page-level decisions. A title page should not
run into the first section. A handoff note might need a clean appendix. A PDF
that people review in a meeting is easier to discuss when every page has a
number.
The useful rule is simple: keep the document in Markdown, but make the few page
layout decisions explicit.
When a page break is worth adding
Add a page break when the reader benefits from a hard section boundary.
Good cases include:
- starting an appendix after the main brief,
- separating a cover or summary from the detailed notes,
- keeping a client-ready handoff section visually clean,
- or forcing a checklist, sign-off block, or references section onto a new page.
Do not add page breaks just because the preview looks a little cramped today.
That usually makes the source harder to maintain. The best page breaks describe
real document structure, not one temporary rendering accident.
When page numbers are worth adding
Page numbers are useful when the exported document will be discussed outside the
Markdown editor.
They help when someone says:
- "look at page 4,"
- "the appendix starts after the checklist,"
- or "send the numbered version to the client."
They are less useful for short one-page notes, quick drafts, or content that
will mostly be copied into another system. That is why depapel keeps page
numbering opt-in instead of adding it to every export.
The Markdown source stays small
Here is the raw Markdown source pattern:
# Product Launch Brief
<depapel-page-numbering/>
## Summary
This short brief needs page numbers because it will be reviewed as a PDF and a
DOCX file.
## Checklist
- [x] Confirm the source Markdown is readable.
- [x] Render the PDF from the same source.
- [ ] Review the artifact before sending it externally.
<depapel-page-break/>
## Handoff Notes
This section starts on a fresh page.
The tags are deliberately standalone lines. They are not inline styling. They
are document controls that say something concrete about the exported file.
A proof-backed example
The proof gallery includes a tracked sample called layout-brief that uses both
directives from the same Markdown source:
That sample is intentionally small. It combines a table, checklist, page
numbering, and one deliberate page break so you can inspect the actual output
without trusting a screenshot or marketing claim.
Where depapel fits
If you need a shareable file, depapel turns the same Markdown source into
PDF or DOCX. The page-break directive
works across those document outputs, and page numbering is enabled only when the
source asks for it.
That matters for handoff documents because the Markdown remains the source of
truth. You can keep editing the brief in text form, then export a numbered PDF
for reading or a DOCX for comments and edits.
What this does not mean
These directives are not a full page-layout template system.
They do not promise:
- custom Word templates,
- automatic chapter styling,
- arbitrary headers and footers,
- or desktop publishing controls.
They solve the narrow problem that comes up often in real Markdown documents:
where should a new page start, and should the exported file show page numbers?
Practical rule
Use page breaks for meaningful section boundaries. Use page numbers when the
exported file will be reviewed, printed, or referenced by page.
If neither of those is true, leave the Markdown alone. The best document control
is the one that makes the final file clearer without making the source harder to
read.
Please enable JavaScript to use depapel.