Directory Tree

The ideal workflow is to put Composer in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central Composer install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a Composer documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

Custom targets can also be defined, using standard GNU Make syntax (see [Custom Targets]).

Important Notes

GNU Make does not support file and directory names with spaces in them, and neither does Composer. Documentation archives which have such files or directories will produce unexpected results. In addtion, all file names must match the regular expression [[:alnum:]+.@_~-]+, and files starting with the regular expression [.+] are skipped by auto-detection (see [Custom Targets]).

It is fully supported for input files to be symbolic links to files that reside outside the documentation archive:

(continued)
pages/2024-01-01+template_0.html

Directory Tree

The ideal workflow is to put Composer in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central Composer install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a Composer documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

Custom targets can also be defined, using standard GNU Make syntax (see [Custom Targets]).

Important Notes

GNU Make does not support file and directory names with spaces in them, and neither does Composer. Documentation archives which have such files or directories will produce unexpected results. In addtion, all file names must match the regular expression [[:alnum:]+.@_~-]+, and files starting with the regular expression [.+] are skipped by auto-detection (see [Custom Targets]).

It is fully supported for input files to be symbolic links to files that reside outside the documentation archive:

(continued)
pages/2024-01-01+template_1.html

Directory Tree

The ideal workflow is to put Composer in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central Composer install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a Composer documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

Custom targets can also be defined, using standard GNU Make syntax (see [Custom Targets]).

Important Notes

GNU Make does not support file and directory names with spaces in them, and neither does Composer. Documentation archives which have such files or directories will produce unexpected results. In addtion, all file names must match the regular expression [[:alnum:]+.@_~-]+, and files starting with the regular expression [.+] are skipped by auto-detection (see [Custom Targets]).

It is fully supported for input files to be symbolic links to files that reside outside the documentation archive:

(continued)
pages/2024-01-01+template_2.html

Directory Tree

The ideal workflow is to put Composer in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central Composer install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a Composer documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

Custom targets can also be defined, using standard GNU Make syntax (see [Custom Targets]).

Important Notes

GNU Make does not support file and directory names with spaces in them, and neither does Composer. Documentation archives which have such files or directories will produce unexpected results. In addtion, all file names must match the regular expression [[:alnum:]+.@_~-]+, and files starting with the regular expression [.+] are skipped by auto-detection (see [Custom Targets]).

It is fully supported for input files to be symbolic links to files that reside outside the documentation archive:

(continued)
pages/2024-01-01+template_3.html

Directory Tree

The ideal workflow is to put Composer in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central Composer install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a Composer documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

Custom targets can also be defined, using standard GNU Make syntax (see [Custom Targets]).

Important Notes

GNU Make does not support file and directory names with spaces in them, and neither does Composer. Documentation archives which have such files or directories will produce unexpected results. In addtion, all file names must match the regular expression [[:alnum:]+.@_~-]+, and files starting with the regular expression [.+] are skipped by auto-detection (see [Custom Targets]).

It is fully supported for input files to be symbolic links to files that reside outside the documentation archive:

(continued)
pages/2024-01-01+template_4.html

Directory Tree

The ideal workflow is to put Composer in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central Composer install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a Composer documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

Custom targets can also be defined, using standard GNU Make syntax (see [Custom Targets]).

Important Notes

GNU Make does not support file and directory names with spaces in them, and neither does Composer. Documentation archives which have such files or directories will produce unexpected results. In addtion, all file names must match the regular expression [[:alnum:]+.@_~-]+, and files starting with the regular expression [.+] are skipped by auto-detection (see [Custom Targets]).

It is fully supported for input files to be symbolic links to files that reside outside the documentation archive:

(continued)
pages/2024-01-01+template_5.html

Directory Tree

The ideal workflow is to put Composer in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central Composer install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a Composer documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

Custom targets can also be defined, using standard GNU Make syntax (see [Custom Targets]).

Important Notes

GNU Make does not support file and directory names with spaces in them, and neither does Composer. Documentation archives which have such files or directories will produce unexpected results. In addtion, all file names must match the regular expression [[:alnum:]+.@_~-]+, and files starting with the regular expression [.+] are skipped by auto-detection (see [Custom Targets]).

It is fully supported for input files to be symbolic links to files that reside outside the documentation archive:

(continued)
pages/2024-01-01+template_6.html

Directory Tree

The ideal workflow is to put Composer in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central Composer install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a Composer documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

Custom targets can also be defined, using standard GNU Make syntax (see [Custom Targets]).

Important Notes

GNU Make does not support file and directory names with spaces in them, and neither does Composer. Documentation archives which have such files or directories will produce unexpected results. In addtion, all file names must match the regular expression [[:alnum:]+.@_~-]+, and files starting with the regular expression [.+] are skipped by auto-detection (see [Custom Targets]).

It is fully supported for input files to be symbolic links to files that reside outside the documentation archive:

(continued)
pages/2024-01-01+template_7.html

Directory Tree

The ideal workflow is to put Composer in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central Composer install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a Composer documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

Custom targets can also be defined, using standard GNU Make syntax (see [Custom Targets]).

Important Notes

GNU Make does not support file and directory names with spaces in them, and neither does Composer. Documentation archives which have such files or directories will produce unexpected results. In addtion, all file names must match the regular expression [[:alnum:]+.@_~-]+, and files starting with the regular expression [.+] are skipped by auto-detection (see [Custom Targets]).

It is fully supported for input files to be symbolic links to files that reside outside the documentation archive:

(continued)
pages/2024-01-01+template_8.html

Directory Tree

The ideal workflow is to put Composer in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central Composer install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a Composer documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

Custom targets can also be defined, using standard GNU Make syntax (see [Custom Targets]).

Important Notes

GNU Make does not support file and directory names with spaces in them, and neither does Composer. Documentation archives which have such files or directories will produce unexpected results. In addtion, all file names must match the regular expression [[:alnum:]+.@_~-]+, and files starting with the regular expression [.+] are skipped by auto-detection (see [Custom Targets]).

It is fully supported for input files to be symbolic links to files that reside outside the documentation archive:

(continued)
pages/2024-01-01+template_9.html

Directory Tree

The ideal workflow is to put Composer in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central Composer install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a Composer documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

Custom targets can also be defined, using standard GNU Make syntax (see [Custom Targets]).

Important Notes

GNU Make does not support file and directory names with spaces in them, and neither does Composer. Documentation archives which have such files or directories will produce unexpected results. In addtion, all file names must match the regular expression [[:alnum:]+.@_~-]+, and files starting with the regular expression [.+] are skipped by auto-detection (see [Custom Targets]).

It is fully supported for input files to be symbolic links to files that reside outside the documentation archive:

(continued)
pages/2023-01-01+template_0.html

Directory Tree

The ideal workflow is to put Composer in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central Composer install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a Composer documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

Custom targets can also be defined, using standard GNU Make syntax (see [Custom Targets]).

Important Notes

GNU Make does not support file and directory names with spaces in them, and neither does Composer. Documentation archives which have such files or directories will produce unexpected results. In addtion, all file names must match the regular expression [[:alnum:]+.@_~-]+, and files starting with the regular expression [.+] are skipped by auto-detection (see [Custom Targets]).

It is fully supported for input files to be symbolic links to files that reside outside the documentation archive:

(continued)
pages/2023-01-01+template_1.html

Directory Tree

The ideal workflow is to put Composer in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central Composer install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a Composer documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

Custom targets can also be defined, using standard GNU Make syntax (see [Custom Targets]).

Important Notes

GNU Make does not support file and directory names with spaces in them, and neither does Composer. Documentation archives which have such files or directories will produce unexpected results. In addtion, all file names must match the regular expression [[:alnum:]+.@_~-]+, and files starting with the regular expression [.+] are skipped by auto-detection (see [Custom Targets]).

It is fully supported for input files to be symbolic links to files that reside outside the documentation archive:

(continued)
pages/2023-01-01+template_2.html

Directory Tree

The ideal workflow is to put Composer in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central Composer install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a Composer documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

Custom targets can also be defined, using standard GNU Make syntax (see [Custom Targets]).

Important Notes

GNU Make does not support file and directory names with spaces in them, and neither does Composer. Documentation archives which have such files or directories will produce unexpected results. In addtion, all file names must match the regular expression [[:alnum:]+.@_~-]+, and files starting with the regular expression [.+] are skipped by auto-detection (see [Custom Targets]).

It is fully supported for input files to be symbolic links to files that reside outside the documentation archive:

(continued)
pages/2023-01-01+template_3.html

Directory Tree

The ideal workflow is to put Composer in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central Composer install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a Composer documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

Custom targets can also be defined, using standard GNU Make syntax (see [Custom Targets]).

Important Notes

GNU Make does not support file and directory names with spaces in them, and neither does Composer. Documentation archives which have such files or directories will produce unexpected results. In addtion, all file names must match the regular expression [[:alnum:]+.@_~-]+, and files starting with the regular expression [.+] are skipped by auto-detection (see [Custom Targets]).

It is fully supported for input files to be symbolic links to files that reside outside the documentation archive:

(continued)
pages/2023-01-01+template_4.html

Directory Tree

The ideal workflow is to put Composer in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central Composer install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a Composer documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

Custom targets can also be defined, using standard GNU Make syntax (see [Custom Targets]).

Important Notes

GNU Make does not support file and directory names with spaces in them, and neither does Composer. Documentation archives which have such files or directories will produce unexpected results. In addtion, all file names must match the regular expression [[:alnum:]+.@_~-]+, and files starting with the regular expression [.+] are skipped by auto-detection (see [Custom Targets]).

It is fully supported for input files to be symbolic links to files that reside outside the documentation archive:

(continued)
pages/2023-01-01+template_5.html

Directory Tree

The ideal workflow is to put Composer in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central Composer install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a Composer documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

Custom targets can also be defined, using standard GNU Make syntax (see [Custom Targets]).

Important Notes

GNU Make does not support file and directory names with spaces in them, and neither does Composer. Documentation archives which have such files or directories will produce unexpected results. In addtion, all file names must match the regular expression [[:alnum:]+.@_~-]+, and files starting with the regular expression [.+] are skipped by auto-detection (see [Custom Targets]).

It is fully supported for input files to be symbolic links to files that reside outside the documentation archive:

(continued)
pages/2023-01-01+template_6.html

Directory Tree

The ideal workflow is to put Composer in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central Composer install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a Composer documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

Custom targets can also be defined, using standard GNU Make syntax (see [Custom Targets]).

Important Notes

GNU Make does not support file and directory names with spaces in them, and neither does Composer. Documentation archives which have such files or directories will produce unexpected results. In addtion, all file names must match the regular expression [[:alnum:]+.@_~-]+, and files starting with the regular expression [.+] are skipped by auto-detection (see [Custom Targets]).

It is fully supported for input files to be symbolic links to files that reside outside the documentation archive:

(continued)
pages/2023-01-01+template_7.html

Directory Tree

The ideal workflow is to put Composer in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central Composer install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a Composer documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

Custom targets can also be defined, using standard GNU Make syntax (see [Custom Targets]).

Important Notes

GNU Make does not support file and directory names with spaces in them, and neither does Composer. Documentation archives which have such files or directories will produce unexpected results. In addtion, all file names must match the regular expression [[:alnum:]+.@_~-]+, and files starting with the regular expression [.+] are skipped by auto-detection (see [Custom Targets]).

It is fully supported for input files to be symbolic links to files that reside outside the documentation archive:

(continued)
pages/2023-01-01+template_8.html

Directory Tree

The ideal workflow is to put Composer in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central Composer install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a Composer documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

Custom targets can also be defined, using standard GNU Make syntax (see [Custom Targets]).

Important Notes

GNU Make does not support file and directory names with spaces in them, and neither does Composer. Documentation archives which have such files or directories will produce unexpected results. In addtion, all file names must match the regular expression [[:alnum:]+.@_~-]+, and files starting with the regular expression [.+] are skipped by auto-detection (see [Custom Targets]).

It is fully supported for input files to be symbolic links to files that reside outside the documentation archive:

(continued)
pages/2023-01-01+template_9.html

Directory Tree

The ideal workflow is to put Composer in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central Composer install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a Composer documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

Custom targets can also be defined, using standard GNU Make syntax (see [Custom Targets]).

Important Notes

GNU Make does not support file and directory names with spaces in them, and neither does Composer. Documentation archives which have such files or directories will produce unexpected results. In addtion, all file names must match the regular expression [[:alnum:]+.@_~-]+, and files starting with the regular expression [.+] are skipped by auto-detection (see [Custom Targets]).

(continued)
pages/2022-01-01+template_0.html

Directory Tree

The ideal workflow is to put Composer in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central Composer install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a Composer documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

Custom targets can also be defined, using standard GNU Make syntax (see [Custom Targets]).

Important Notes

GNU Make does not support file and directory names with spaces in them, and neither does Composer. Documentation archives which have such files or directories will produce unexpected results. In addtion, all file names must match the regular expression [[:alnum:]+.@_~-]+, and files starting with the regular expression [.+] are skipped by auto-detection (see [Custom Targets]).

It is fully supported for input files to be symbolic links to files that reside outside the documentation archive:

(continued)
pages/2022-01-01+template_1.html

Directory Tree

The ideal workflow is to put Composer in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central Composer install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a Composer documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

Custom targets can also be defined, using standard GNU Make syntax (see [Custom Targets]).

Important Notes

GNU Make does not support file and directory names with spaces in them, and neither does Composer. Documentation archives which have such files or directories will produce unexpected results. In addtion, all file names must match the regular expression [[:alnum:]+.@_~-]+, and files starting with the regular expression [.+] are skipped by auto-detection (see [Custom Targets]).

It is fully supported for input files to be symbolic links to files that reside outside the documentation archive:

(continued)
pages/2022-01-01+template_2.html

Directory Tree

The ideal workflow is to put Composer in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central Composer install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a Composer documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

Custom targets can also be defined, using standard GNU Make syntax (see [Custom Targets]).

Important Notes

GNU Make does not support file and directory names with spaces in them, and neither does Composer. Documentation archives which have such files or directories will produce unexpected results. In addtion, all file names must match the regular expression [[:alnum:]+.@_~-]+, and files starting with the regular expression [.+] are skipped by auto-detection (see [Custom Targets]).

It is fully supported for input files to be symbolic links to files that reside outside the documentation archive:

(continued)
pages/2022-01-01+template_3.html

Directory Tree

The ideal workflow is to put Composer in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central Composer install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a Composer documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

Custom targets can also be defined, using standard GNU Make syntax (see [Custom Targets]).

Important Notes

GNU Make does not support file and directory names with spaces in them, and neither does Composer. Documentation archives which have such files or directories will produce unexpected results. In addtion, all file names must match the regular expression [[:alnum:]+.@_~-]+, and files starting with the regular expression [.+] are skipped by auto-detection (see [Custom Targets]).

It is fully supported for input files to be symbolic links to files that reside outside the documentation archive:

(continued)
pages/2022-01-01+template_4.html

Directory Tree

The ideal workflow is to put Composer in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central Composer install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a Composer documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

Custom targets can also be defined, using standard GNU Make syntax (see [Custom Targets]).

Important Notes

GNU Make does not support file and directory names with spaces in them, and neither does Composer. Documentation archives which have such files or directories will produce unexpected results. In addtion, all file names must match the regular expression [[:alnum:]+.@_~-]+, and files starting with the regular expression [.+] are skipped by auto-detection (see [Custom Targets]).

It is fully supported for input files to be symbolic links to files that reside outside the documentation archive:

(continued)
pages/2022-01-01+template_5.html

Directory Tree

The ideal workflow is to put Composer in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central Composer install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a Composer documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

Custom targets can also be defined, using standard GNU Make syntax (see [Custom Targets]).

Important Notes

GNU Make does not support file and directory names with spaces in them, and neither does Composer. Documentation archives which have such files or directories will produce unexpected results. In addtion, all file names must match the regular expression [[:alnum:]+.@_~-]+, and files starting with the regular expression [.+] are skipped by auto-detection (see [Custom Targets]).

It is fully supported for input files to be symbolic links to files that reside outside the documentation archive:

(continued)
pages/2022-01-01+template_6.html

Directory Tree

The ideal workflow is to put Composer in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central Composer install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a Composer documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

Custom targets can also be defined, using standard GNU Make syntax (see [Custom Targets]).

Important Notes

GNU Make does not support file and directory names with spaces in them, and neither does Composer. Documentation archives which have such files or directories will produce unexpected results. In addtion, all file names must match the regular expression [[:alnum:]+.@_~-]+, and files starting with the regular expression [.+] are skipped by auto-detection (see [Custom Targets]).

It is fully supported for input files to be symbolic links to files that reside outside the documentation archive:

(continued)
pages/2022-01-01+template_7.html

Directory Tree

The ideal workflow is to put Composer in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central Composer install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a Composer documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

Custom targets can also be defined, using standard GNU Make syntax (see [Custom Targets]).

Important Notes

GNU Make does not support file and directory names with spaces in them, and neither does Composer. Documentation archives which have such files or directories will produce unexpected results. In addtion, all file names must match the regular expression [[:alnum:]+.@_~-]+, and files starting with the regular expression [.+] are skipped by auto-detection (see [Custom Targets]).

It is fully supported for input files to be symbolic links to files that reside outside the documentation archive:

(continued)
pages/2022-01-01+template_8.html

Directory Tree

The ideal workflow is to put Composer in a top-level .Composer for each directory tree you want to manage, creating a structure similar to this:

.../.Composer
.../
.../tld/
.../tld/sub/

To save on disk space using a central Composer install for multiple directory trees, the [init] target can be used to create a linked .Composer directory, and then the entire directory tree can be converted to a Composer documentation archive ([Quick Start] example):

cd .../documents
make -f .../.Composer/Makefile init
make -f .../.Composer/Makefile install-all
make all-all

Customization

If specific settings need to be used, either globally or per-directory, .composer.mk and .composer.yml files can be created (see [Configuration Settings], [Quick Start] example):

make template >.composer.mk && $EDITOR .composer.mk
make template.yml >.composer.yml && $EDITOR .composer.yml

Custom targets can also be defined, using standard GNU Make syntax (see [Custom Targets]).

Important Notes

GNU Make does not support file and directory names with spaces in them, and neither does Composer. Documentation archives which have such files or directories will produce unexpected results. In addtion, all file names must match the regular expression [[:alnum:]+.@_~-]+, and files starting with the regular expression [.+] are skipped by auto-detection (see [Custom Targets]).

It is fully supported for input files to be symbolic links to files that reside outside the documentation archive:

(continued)
pages/2022-01-01+template_9.html