#WORK
#WORK

config/_library-config/index-include.md.cms

config/_library-config/sitemap-include.md.cms

#WORK

#WORK

<!-- composer >> metainfo -->

Configuration Settings

site-config defaults values
navbars.brand null null
navbars.homepage null null
navbars.search.name null null
navbars.search.site null null
navbars.search.call null null
navbars.search.form null null
navbars.copyright null null
navbars.composer 1 1
pages.css_overlay dark null
pages.copy_protect null 1
pages.header `[ “null” ][ “../../ config/_header.md.cms” ]`
pages.footer `[ “null” ][ “../../ config/_footer.md.cms” ]`
cols.break lg md
cols.scroll 1 null
cols.order `[ 1, 2, 3 ][ 1, 3, 2 ]`
cols.reorder `[ 1, 3, 2 ][ 2, 3, 1 ]`
cols.size `[ 3, 7, 2 ][ 12, 9, 3 ]`
cols.resize `[ 6, 12, 6 ][ 12, 12, 0 ]`
dates.parse *(see [dat es.parse](../../../index.html#datesparse) and .composer.yml)* *(see [dates.parse]( ../../../index.html#datesparse) and .composer.yml)*
dates.display `2006-01-0 22006-01-0 2 03:04 PM MST`
dates.library 2006 2006-01
dates.timezone -08:00 -07:00

(continued)
index.html

#WORK # metainfo page description text

(continued)
pages.html

Page #0 in 2024  (2024-01-01 12:00 AM -0700)
– Gary B. Genett – Author 1 – Author 2 – Author 3
. Tag 0 . Tag 1 . Tag 2 . Tag 3

Lorem Ipsum #0 in 2024

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.

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

cd .../tld
ln -rs .../README.md ./
make README.html

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

Page #1 in 2024  (2024-01-01 12:00 AM -0700)
– Gary B. Genett – Author 1 – Author 2 – Author 3
. Tag 1 . Tag 1 . Tag 2 . Tag 3

Lorem Ipsum #1 in 2024

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.

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

cd .../tld
ln -rs .../README.md ./
make README.html

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

Page #2 in 2024  (2024-01-01 12:00 AM -0700)
– Gary B. Genett – Author 1 – Author 2 – Author 3
. Tag 2 . Tag 1 . Tag 2 . Tag 3

Lorem Ipsum #2 in 2024

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.

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

cd .../tld
ln -rs .../README.md ./
make README.html

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

Page #3 in 2024  (2024-01-01 12:00 AM -0700)
– Gary B. Genett – Author 1 – Author 2 – Author 3
. Tag 3 . Tag 1 . Tag 2 . Tag 3

Lorem Ipsum #3 in 2024

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.

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

cd .../tld
ln -rs .../README.md ./
make README.html

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

Page #4 in 2024  (2024-01-01 12:00 AM -0700)
– Gary B. Genett – Author 1 – Author 2 – Author 3
. Tag 4 . Tag 1 . Tag 2 . Tag 3

Lorem Ipsum #4 in 2024

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.

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

cd .../tld
ln -rs .../README.md ./
make README.html

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

Page #5 in 2024  (2024-01-01 12:00 AM -0700)
– Gary B. Genett – Author 1 – Author 2 – Author 3
. Tag 5 . Tag 1 . Tag 2 . Tag 3

Lorem Ipsum #5 in 2024

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.

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

cd .../tld
ln -rs .../README.md ./
make README.html

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

Page #6 in 2024  (2024-01-01 12:00 AM -0700)
– Gary B. Genett – Author 1 – Author 2 – Author 3
. Tag 6 . Tag 1 . Tag 2 . Tag 3

Lorem Ipsum #6 in 2024

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.

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

cd .../tld
ln -rs .../README.md ./
make README.html

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

Page #7 in 2024  (2024-01-01 12:00 AM -0700)
– Gary B. Genett – Author 1 – Author 2 – Author 3
. Tag 7 . Tag 1 . Tag 2 . Tag 3

Lorem Ipsum #7 in 2024

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.

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

cd .../tld
ln -rs .../README.md ./
make README.html

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

Page #8 in 2024  (2024-01-01 12:00 AM -0700)
– Gary B. Genett – Author 1 – Author 2 – Author 3
. Tag 8 . Tag 1 . Tag 2 . Tag 3

Lorem Ipsum #8 in 2024

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.

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

cd .../tld
ln -rs .../README.md ./
make README.html

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

Page #9 in 2024  (2024-01-01 12:00 AM -0700)
– Gary B. Genett – Author 1 – Author 2 – Author 3
. Tag 9 . Tag 1 . Tag 2 . Tag 3

Lorem Ipsum #9 in 2024

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.

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

cd .../tld
ln -rs .../README.md ./
make README.html

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

Page #0 in 2023  (2023-01-01 12:00 AM -0700)
– Gary B. Genett – Author 1 – Author 2 – Author 3
. Tag 0 . Tag 1 . Tag 2 . Tag 3

Lorem Ipsum #0 in 2023

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.

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

cd .../tld
ln -rs .../README.md ./
make README.html

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

Page #1 in 2023  (2023-01-01 12:00 AM -0700)
– Gary B. Genett – Author 1 – Author 2 – Author 3
. Tag 1 . Tag 1 . Tag 2 . Tag 3

Lorem Ipsum #1 in 2023

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.

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

cd .../tld
ln -rs .../README.md ./
make README.html

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

Page #2 in 2023  (2023-01-01 12:00 AM -0700)
– Gary B. Genett – Author 1 – Author 2 – Author 3
. Tag 2 . Tag 1 . Tag 2 . Tag 3

Lorem Ipsum #2 in 2023

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.

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

cd .../tld
ln -rs .../README.md ./
make README.html

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

Page #3 in 2023  (2023-01-01 12:00 AM -0700)
– Gary B. Genett – Author 1 – Author 2 – Author 3
. Tag 3 . Tag 1 . Tag 2 . Tag 3

Lorem Ipsum #3 in 2023

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.

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

cd .../tld
ln -rs .../README.md ./
make README.html

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

Page #4 in 2023  (2023-01-01 12:00 AM -0700)
– Gary B. Genett – Author 1 – Author 2 – Author 3
. Tag 4 . Tag 1 . Tag 2 . Tag 3

Lorem Ipsum #4 in 2023

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.

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

cd .../tld
ln -rs .../README.md ./
make README.html

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

Page #5 in 2023  (2023-01-01 12:00 AM -0700)
– Gary B. Genett – Author 1 – Author 2 – Author 3
. Tag 5 . Tag 1 . Tag 2 . Tag 3

Lorem Ipsum #5 in 2023

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.

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

cd .../tld
ln -rs .../README.md ./
make README.html

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

Page #6 in 2023  (2023-01-01 12:00 AM -0700)
– Gary B. Genett – Author 1 – Author 2 – Author 3
. Tag 6 . Tag 1 . Tag 2 . Tag 3

Lorem Ipsum #6 in 2023

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.

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

cd .../tld
ln -rs .../README.md ./
make README.html

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

Page #7 in 2023  (2023-01-01 12:00 AM -0700)
– Gary B. Genett – Author 1 – Author 2 – Author 3
. Tag 7 . Tag 1 . Tag 2 . Tag 3

Lorem Ipsum #7 in 2023

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.

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

cd .../tld
ln -rs .../README.md ./
make README.html

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

  • ITEM 1
  • ITEM 2
  • ITEM 3

RIGHT BOX

RIGHT TEXT

Main 2
Tag 0 3
Tag 1 30
Tag 2 30
Tag 3 30
Tag 4 3
Tag 5 3
Tag 6 3
Tag 7 3
Tag 8 3
Tag 9 3

CHAINED