Managing Large Projects
For a long EasyLaTeX document, separate the main file, chapters, figures, and bibliography. This reduces accidental changes and makes collaboration easier. The platform manages compilation and generated files; maintain the project's source, resources, and settings.
Keep One Main File
Select the complete entry point, such as main.tex, in the platform's main-file selector. It controls the class, packages, global settings, and chapter order:
main.tex
chapters/*.tex
figures/*
references.bib
Continue compiling this main file when editing chapters. Retain the entry point specified by an existing template.
Organize the File Tree by Purpose
chapters/: chapter text.figures/: images and graphics source.tables/: reusable table fragments.data/: data read by the document.bibliography/:.bibfiles.
After creating or uploading files, check relative paths and capitalization. Define chapter order in the main file rather than relying on numbered filenames.
Preview Large Chapters
Keep the complete entry point and inspect recently changed chapters one at a time. \includeonly can limit which chapters are typeset:
\includeonly{chapters/method,chapters/results}
Use this for previews only. References and numbering for skipped chapters depend on auxiliary information that should not be assumed available in every platform job. Remove \includeonly before checking the whole document or downloading the final PDF.
Use Draft Mode for Image-Heavy Previews
Temporarily add draft to the class:
\documentclass[draft,a4paper,12pt]{book}
Or apply it only to graphicx:
\usepackage[draft]{graphicx}
Draft output may contain only image boxes, so it cannot confirm final image quality or layout. Remove draft, compile again, and inspect the PDF before delivery.
Generated Files Are Managed by the Platform
Files such as .aux, .toc, .lof, and .lot support contents and references. Normally you do not create or edit them in the project tree. For incorrect contents or references, check the main file, labels, and first compilation error, then compile again and let the platform complete the necessary passes.
Collaboration and Delivery
Coordinate template changes with collaborators. Before delivery, compile the whole document and inspect contents, figure and table lists, headers, footers, page numbers, and images. Retain source, images, .bib files, and template dependencies. A downloaded PDF is the deliverable, not a replacement for a source backup.
Common Problems
Only Some Chapters Appear
Check the selected main file, any remaining \includeonly, and the paths used by \input or \include.
The Preview Is Not What You Expected
Check save status, project compiler, main file, and the result of the current compilation. PDF fonts come from the template and project configuration, not from your computer's font list.
Necessary Files Were Removed During Cleanup
Do not treat .cls, .sty, images, or .bib files as compiler cache. Check references before removing resources; restore missing dependencies before compiling again.
Complete Main-File Example
Create the referenced chapter files in the project tree, then select this main file and compile:
\documentclass[a4paper,12pt]{book}
\usepackage{graphicx}
\usepackage[colorlinks=true,linkcolor=blue]{hyperref}
% Uncomment the next line to compile only the selected chapter while debugging
% \includeonly{chapters/method}
\begin{document}
\frontmatter
\tableofcontents
\mainmatter
\include{chapters/introduction}
\include{chapters/method}
\include{chapters/results}
\backmatter
\include{chapters/appendix}
\end{document}