Skip to main content

Overleaf Export Guide

This guide explains how to move LMR documents from Overleaf into the public website structure.

It is a practical workflow page. It does not define LMR theory.

Core Rule​

Overleaf is the writing environment.

The website is the public distribution environment.

Do not use Overleaf project links as permanent public download links.

Public PDFs should be exported, renamed, placed in public/pdfs/, and linked from the website.

Export Workflow​

For each document:

  1. Compile the document in Overleaf.
  2. Download the compiled PDF.
  3. Rename the PDF using the public naming convention.
  4. Place the renamed PDF in public/pdfs/.
  5. Update the Downloads page.
  6. Update the Release Registry.
  7. Confirm the file path works.
  8. Run a link audit.

Public PDF Folder​

Store public PDFs here:

public/pdfs/

Example:

public/pdfs/lmr_paper_i_codex_v1.0.pdf

The public site link should then be:

/pdfs/lmr_paper_i_codex_v1.0.pdf

File Naming Rule​

Use lowercase file names with underscores.

Use this pattern:

lmr_[document_type][identifier][short_title]_[version].pdf

Examples:

  • lmr_paper_i_codex_v1.0.pdf
  • lmr_paper_ii_lattice_v1.0.pdf
  • lmr_paper_iii_emergence_structure_v1.0.pdf
  • lmr_s1_routing_modes_v0.1.pdf
  • lmr_s2_hourglass_walkthrough_v0.1.pdf

Do Not Use Private Names Publicly​

Do not publish links using private working names such as:

  • Paper_Vv.016.pdf
  • Paper_IVv.18.pdf
  • Paper I - Codex.pdf.pdf
  • final.pdf
  • final_final.pdf
  • latest.pdf
  • updated_real.pdf

Private names are fine during drafting.

Public names should be stable.

Overleaf Source Files​

The website does not need to expose Overleaf source files.

Public readers should see:

  • paper title
  • document status
  • version
  • date
  • citation
  • PDF download link

They do not need access to:

  • private Overleaf project links
  • TeX source files
  • build logs
  • temporary exports
  • draft folder structure

Version Labels​

Use clear version labels.

Recommended labels:

  • v0.1 for early public drafts
  • v0.9 for final consolidation manuscripts
  • v1.0 for first published release
  • v1.1 for minor corrected release
  • v2.0 for major revision

Do not use unclear labels such as:

  • final
  • latest
  • real
  • current
  • new
  • fixed

Release Registry Update​

After adding a PDF, update:

content/reference/release-registry.md

Each entry should include:

  • document title
  • status
  • version
  • release state
  • citation
  • public PDF path

Example:

Paper I — Codex and Foundational Grammar
Status: Published Paper
Version: v1.0
Release State: Published
Citation: DOI / official link TBD
PDF: /pdfs/lmr_paper_i_codex_v1.0.pdf

Downloads Update​

After adding a PDF, update:

content/downloads.md

Each document should include a direct public PDF link.

Example:

PDF path example: /pdfs/lmr_paper_i_codex_v1.0.pdf

DOI Update​

When a DOI exists, add it to:

  • the paper page
  • Downloads
  • Release Registry
  • Citation
  • any relevant public announcement page

Do not leave DOI information scattered in only one place.

Codex Use​

Codex can help verify Overleaf exports after the PDFs are placed in the site folder.

Codex should check:

  • whether every PDF in Downloads exists
  • whether every PDF in Release Registry exists
  • whether filenames match the naming guide
  • whether any private Overleaf file names remain
  • whether any private local paths remain
  • whether any links are broken

Codex should not rewrite theory during this task.

Codex Prompt​

Use this prompt after exporting PDFs:

Scan the project for PDF references.

Verify that all public PDF links point to files inside public/pdfs/.

Check Downloads, Release Registry, paper pages, and Reference pages.

For public PDF assets, enforce lowercase names with underscores.

Do not rewrite theoretical content.

Do not change LMR definitions.

Report:

  1. missing PDF files
  2. broken PDF links
  3. private filenames still used publicly
  4. inconsistent version labels
  5. mismatches between Downloads and Release Registry

Only fix mechanical file-path issues after reporting them.

Final Export Checklist​

Before treating a PDF as public, confirm:

  • the PDF compiles cleanly
  • the PDF has the correct title
  • the PDF has the correct author
  • the PDF has the correct version
  • the PDF has the correct date
  • the file name follows the public naming rule
  • the file is in public/pdfs/
  • Downloads links to it
  • Release Registry links to it
  • no private Overleaf path is exposed