LEFT TEXT
_library/index-include.md.cms
_library/sitemap-include.md.cms
#WORK
<!-- composer >> metainfo -->
| 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 ] | |
]` |
| dates.parse *(see [dates. | parse](../../index.html#datesparse) and .composer.yml)* *(see [dates.parse](../../ |
index.html#datesparse) and .composer.yml)* |
dates.display 2006-01-02 |
`2006-01-02 0 | 3:04 PM MST` |
dates.library 2006 |
2006-01 |
|
dates.timezone -08:00 |
-07:00 |
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, the main page contents are in c_list. Since nav-left and nav-right are both empty, this column is positioned at the left edge.
Due to the absence of the PAGES menu, use the list below to navigate to the other example pages.
#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.
| 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 # metainfo page description text
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)
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-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):
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-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):
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-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):
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-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):
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-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):
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-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):
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-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):
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-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):
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-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):
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-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):