LEFT TEXT
_library/index-include.md.cms
_library/sitemap-include.md.cms
Composer (Templates)
site.solar-dark)prefers-color-scheme color selection)html)
prefers-color-scheme color selection)site)
prefers-color-scheme color selection)prefers-color-scheme color selection)
#WORK metainfo page description text
| Top Bar | brand (homepage) |
nav-top |
info-top / search.* |
| Main Page | nav-left |
c_list |
nav-right |
| Bottom Bar | copyright |
nav-bottom |
info-bottom / (composer) |
<!-- composer >> fold-begin 3 . 0 Open Fold -->
<!-- composer >> fold-begin 3 0 0 Closed Fold -->
<!-- composer >> fold-end -->
<!-- composer >> fold-end -->
<!-- composer >> fold-begin 0 . 0 Generic Fold -->
Generic Fold
<!-- composer >> fold-end -->
<!-- composer >> box-begin 3 Box -->
<!-- composer >> box-begin 3 Nested Box -->
<!-- composer >> box-end -->
<!-- composer >> box-end -->
<!-- composer >> box-begin 0 Generic Box -->
Generic Box
<!-- composer >> box-end -->
<!-- composer >> row-begin -->
<!-- composer >> column-begin col-6 -->
#WORK # some clever content goes here
<!-- composer >> column-end -->
#WORK # introduction
| Top Bar | brand (homepage) |
nav-top |
info-top / search.* |
| Main Page | nav-left |
c_list |
nav-right |
| Bottom Bar | copyright |
nav-bottom |
info-bottom / (composer) |
The entire list of pages in this test site can be found in the main sitemap. To understand how the site is configured, and to see demonstrations of all the features, visit the following pages. This list can be found in the PAGES menu on the top bar throughout the site.
This is a default page, where all menus and settings are empty. All aspects of c_site pages are configurable using .composer.yml files.
| Top Bar | brand (homepage) |
nav-top |
info-top / search.* |
| Main Page | nav-left |
c_list |
nav-right |
| Bottom Bar | copyright |
nav-bottom |
info-bottom / (composer) |
In the layout, this page column is c_list, and the default cols.size for the center column is 7 and cols.resize for the mobile view is 12. Since nav-left and nav-right are both empty, this column is positioned at the left edge.
In the absence of the PAGES menu, use the list below to navigate to the other example pages.
#WORK
<!-- composer >> metainfo -->
| site-config | defaults | values |
|---|---|---|
brand null |
null |
|
homepage null |
null |
|
search.name null |
null |
|
search.site null |
null |
|
search.call null |
null |
|
search.form null |
null |
|
copyright null |
null |
|
composer 1 |
1 |
|
header null |
`../config/_h | eader.md.cms` |
footer null |
`../config/_f | ooter.md.cms` |
css_overlay dark |
null |
|
copy_protect null |
1 |
|
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 ] | |
]` |
| metainfo.display ` |
itle><|> – <author|; > |
; ( – <author| – > . <tags| . >` |
metainfo.null *(none)* |
null |
|
metalist.author.title Author |
Creator |
|
| metalist.author.display `*Authors: <| | >, <|>* |
/li> |
metalist.tags.title Tag |
Mark |
|
| metalist.tags.display `*Tags: <|>, | <|>* |
/li> |
| readtime.display `*Reading tim | e: |
d> / Minutes: |
readtime.wpm 220 |
200 |
|
redirect.title Moved To |
Redirecting |
|
| redirect.display `**This link | has been permanently moved to: |
g: **` |
redirect.match * |
* |
|
redirect.time 5 |
0 |
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:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf 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
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:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf 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
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:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf 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
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:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf 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
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:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf 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
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:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf 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
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:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf 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
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:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf 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
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:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf 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
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:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf 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
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:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf 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
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:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf 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
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:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf 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
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:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf 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
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:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf 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
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:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf 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
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:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf 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
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:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf 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
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:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf 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
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:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf 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
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:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf 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
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:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf 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
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:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf 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
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:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf 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
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:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf 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
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:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf 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
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:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf 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
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:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf 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
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:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf 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
#WORK metainfo file description text
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:
make -f .../Makefile initThe directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):
make -f .Composer/Makefile install-all
make all-allIf 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):