1
edit
Changes
m
<i><b>Note</b>: 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 {{cmd|startdocument}} (perhaps in combination with {{cmd|usemodule}} or {{cmd|environment}} and {{cmd|startcomponent}} as explained below) and ignore the elaborate project and product setups.</i>
Change link to mag-1101.pdf to https
ConTeXt knows no document classes (as LaTeX does). You can define your [[Layout|layout]] yourself.
:<i><b>Note</b>: 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 {{cmd|startdocument}} (perhaps in combination with {{cmd|usemodule}} or {{cmd|environment}} and {{cmd|startcomponent}} as explained below) and ignore the elaborate project and product setups.</i>
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.
* env_foo
There's a Python script <tt>contextproject.py</tt> at Hraban's [http://githubcodeberg.comorg/fiee/context-tools/blob/master/contextproject.py github 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==
general_img/logo.pdf
...
With directories, the 'c_' prefix becomes obsolete.
'''Environment'''
=See also=
Hans Hagen (2011) [httphttps://pragma-ade.comnl/general/magazines/mag-1101.pdf Project Structure], ConTeXt magazine #1101.
[[Category:Basics]]
[[Category:Tools]]