#WORK
#WORK

_library/index-include.md.cms

_library/sitemap-include.md.cms

#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.

site-config defaults
brand null
homepage null
search :: name null
search :: site null
search :: call null
search :: form null
copyright null
composer 1
header null
footer null
css_overlay dark
copy_protect null
cols_break lg
cols_scroll 1
cols_order [ 1, 2, 3 ]
cols_reorder [ 1, 3, 2 ]
cols_size [ 3, 7, 2 ]
cols_resize `[ 6, 12, 6 ] `
metainfo ` :: <t itle><|> – <author|; >`
metainfo_null *(none)*
metalist :: author title: `Aut hor
{=html} *display:*Authors: <|>, <|>`
metalist :: tags title: `Tag
{=html} *display:*Tags: <|>, <|>`
readtime `*Reading tim e: words,
readtime_wpm 220

[…]

(permalink to full text)

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.

[…]

(permalink to full text)

#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 ] [ 12, 12, 0 ]`
metainfo ` :: <t itle><|> – <author|; > ()<|>
– <author| – >
. <tags| . >`
metainfo_null *(none)* null
metalist :: author title: `Aut hor
{=html} *display:*Authors: <|>, <|>title:Creat
or
{=html} display:
metalist :: tags title: `Tag
{=html} *display:*Tags: <|>, <|>title:Mark`

display: <ul><li><|></li><li><|></li></ul>
readtime `*Reading tim e: words, d> / Minutes:
readtime_wpm 220 200

[…]

(permalink to full text)

2024 Lorem Ipsum #9

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:

make -f .../Makefile init

The directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):

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]).

[…]

(permalink to full text)

2024 Lorem Ipsum #8

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:

make -f .../Makefile init

The directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):

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]).

[…]

(permalink to full text)

2024 Lorem Ipsum #7

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:

make -f .../Makefile init

The directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):

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]).

[…]

(permalink to full text)

2024 Lorem Ipsum #6

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:

make -f .../Makefile init

The directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):

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]).

[…]

(permalink to full text)

2024 Lorem Ipsum #5

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:

make -f .../Makefile init

The directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):

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]).

[…]

(permalink to full text)

2024 Lorem Ipsum #4

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:

make -f .../Makefile init

The directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):

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]).

[…]

(permalink to full text)

2024 Lorem Ipsum #3

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:

make -f .../Makefile init

The directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):

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]).

[…]

(permalink to full text)

2024 Lorem Ipsum #2

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:

make -f .../Makefile init

The directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):

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]).

[…]

(permalink to full text)

2024 Lorem Ipsum #1

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:

make -f .../Makefile init

The directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):

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]).

[…]

(permalink to full text)

2024 Lorem Ipsum #0

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:

make -f .../Makefile init

The directory tree can then be converted to a [Composer] documentation archive ([Quick Start] example):

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]).

[…]

(permalink to full text)

  • ITEM 1
  • ITEM 2
  • ITEM 3

RIGHT BOX

RIGHT TEXT