# Write a thesis

Organize a long manuscript, navigate chapters, and keep a recoverable record of revisions.

A thesis grows over months. Keep its chapters, bibliography, figures, and supporting material in one project, with a history you can return to as the argument changes.

## Begin with the right structure

Choose a **Thesis** research starter or an appropriate [template](/docs/templates/). If your university supplies a class and template, [import that source](/docs/import-project/) and check its compiler requirements.

In LaTeX, keep chapters in separate files and include them from the main document. The project outline and [code intelligence](/docs/code-intelligence/) help you move between sections, labels, and citations.

## Keep the long draft manageable

Fold sections while editing, use the structure view to find your place, and search across project files. The visual prose view can help with a reading pass; switch to source for detailed markup.

Compile the thesis and use [SyncTeX](/docs/synctex/) in supported LaTeX engines to jump between a PDF passage and its source.

## Work through supervisor feedback

Create a [research task](/docs/research-tasks/) for a bounded revision:

> Revise Chapter 2 against feedback.md. Keep the definitions and all equations unchanged. Save a note mapping each feedback point to its change.

Read the result, inspect the diffs, and apply the files you want. Use an ordinary chat when you want to discuss the changes as you make them.

## Save milestones

[Checkpoints](/docs/checkpoints/) capture changed projects after successful compiles. Use [Git commits](/docs/git-history/) for milestones such as a chapter sent to your supervisor or the examination copy.

Before the final export, check references, fonts, metadata, and reading order in [Preflight](/docs/preflight/), alongside your university's submission instructions.
