Project structure

From Wiki
Revision as of 10:47, 25 May 2023 by Guenter (talk | contribs) (Change link to mag-1101.pdf to https)
Jump to navigation Jump to search


ConTeXt knows no document classes (as LaTeX does). You can define your layout yourself.

Note: the project structure explained on this page is not the only way to handle complex documents. If you are working on a project with a single output file, it may be simpler to use \startdocument (perhaps in combination with \usemodule or \environment and \startcomponent as explained below) and ignore the elaborate project and product setups.

If you use the same layout for several related products, it may make sense to use the project support in ConTeXt. You then save your layout settings as an environment file, and you can reuse various document parts in multiple products.

How to split up a large project, say a collection of books, in several handy parts? – Use ConTeXt's project management facilities.

  • a project links one or more products to their environment
  • a product contains several components
  • an environment defines the common layout (etc.) of a project

The environment could also contain different versions of the layout, e.g. print and screen (like Pragma's manuals) or final and correction etc.

Example 1: Magazine

  • project: magazine
  • product: one volume of the magazine
  • component: a single article

Example 2: Book

  • project: a series of books
  • product: one book
  • component: part or chapter


If you tex (compile) one single component (e.g. a chapter of a book) or product (e.g. one volume of a magazine), the environment file of the project is used.

In addition, you have to keep in mind that when compiling a product or component file, ConTeXt goes "up" to the project file and compiles everything it finds in there that is not a \product (e.g. table of content, sectioning commands, text, \component etc.). So all the things on project level have to be put inside a \product, otherwise they will show up in the individual components (or products), too. That also makes it problematic to use \component directly inside a project file, i.e. you have to use \product, you can't skip it.

While you can compile ("tex") products and single components, the project is not intended for compiling; trying might lead to infinite inclusion loops and the error message "TeX capacity exceeded".

File and directory setup

Naming conventions

Hraban uses and suggests the following naming conventions

  • project_foo
  • prd_foo
  • c_foo
  • env_foo

There's a Python script at Hraban's Codeberg repository to help creating the files (.ini files can be used for initial content). This functionality would be nice to be integrated in any editor supporting ConTeXt...

Example files


\startproject project_mymag
\environment env_mymag % only mentioned here!

\product prd_year2004-01
\product prd_year2004-02
\product prd_year2004-03
\product prd_year2004-04



\startenvironment env_mymag

% all setups...



\startproduct prd_year2004-01
\project project_mymag

\component c_editorial
\component c_article01
\component c_article_by_me
% ...



\startcomponent c_editorial
\product prd_year2004-01 % but you can use it in other products anyway


Dear reader...



If you keep all files in one directory, it tends to get confusing. Here’s a structured example where we keep all parts of one product together:


With directories, the 'c_' prefix becomes obsolete.


\startenvironment env_mymag
\project project_mymag


% where \product and \component look for TeX input files

% where to look for images
 {\setupexternalfigures[directory={../general_img, img}]}



\startproduct prd_issue2011-01
\project project_mymag
\environment env_mymag

\component c_editorial
\component c_article1


ConTeXt automatically looks into parent directories.

Command behaviour

Within a \start...\stop... environment, project, product, and environment definition files are loaded only once, while component files are loaded at every mention. In addition, certain loading commands are ignored inside certain environments -- for example, it makes no sense to load a \component inside a \startenvironment block. The table below gives an overview.

\project \environment \product \component
\starttext once at every mention
\startproject once once
\startenvironment once
\startproduct once once at every mention
\startcomponent once once at every mention

See also

Hans Hagen (2011) Project Structure, ConTeXt magazine #1101.