Embedded bibliography data
Keep bibliography content inside the document workflow instead of relying on fragile local filesystem paths.
mdedit.io turns BibTeX- and CSL-style citations from raw syntax into a usable writing workflow: add references, preview output, send review-ready DOCX to supervisors, and export clean PDF from the same document in the browser.
Keep bibliography content inside the document workflow instead of relying on fragile local filesystem paths.
Check citation output before export and use the same source document for review-ready DOCX and final PDF delivery.
Set `reference-section-title`, citation linking, and output behavior in frontmatter rather than hand-editing the final document.
Use citations alongside section numbering, cross-references, and long-document structure in the same editor.
```mdedit-bibliography
[
{
"id": "smith2023",
"title": "My Article",
"author": [{"family": "Smith", "given": "John"}],
"issued": {"date-parts": [[2023]]}
}
]
```
As shown by Smith [@smith2023], structured
citation workflows scale better.
# References
Define citation mode and bibliography behavior in YAML frontmatter.
Store references in an embedded bibliography block so they travel with the document.
Insert citation keys in the document and review them in live preview.
Use the same document for DOCX review handoff and PDF submission instead of maintaining separate reference paths.
No. mdedit.io wraps the syntax in an editor workflow with preview, metadata handling, and export paths.
Yes. The citations path is designed for academic documents where the same source needs both Word-compatible review handoff and structured PDF export.
Not necessarily. mdedit.io supports embedded bibliography data as the document-bound default path.
Use the scientific-documents section in the help page and the thesis reference document for the deeper workflow.