| 25 | | |
| 26 | | === txt.conf |
| 27 | | |
| 28 | | * Id: A random, unique, alphanumeric string for distinguishing the repository (at least 6 characters of Crockford's [https://en.wikipedia.org/wiki/Base32 Base32] recommended) |
| 29 | | * Title: A human-friendly title |
| 30 | | * Authors: Comma-separated list of names (and optionally, addresses in the {{{ <name@domain> }}} format |
| 31 | | * Topics: Topics the repository aims to cover (comma-separated) |
| 32 | | * Locations: List of [https://en.wikipedia.org/wiki/URI URIs] where the repository can be accessed |
| 33 | | * Peers: List of peer URIs |
| 34 | | |
| 35 | | === HTML |
| 36 | | There are some special settings for HTML publication: |
| 37 | | |
| 38 | | * HTM-style: path to a CSS style. It will be inserted in every .htm file. To link to a single CSS consider using `@import` |
| 39 | | * HTM-header: path to a file, inserted in every .htm file, right after the `<body>` tag |
| 40 | | * HTM-footer: path to a file, inserted in every .htm file, right before the `</body>` tag |
| 41 | | * HTM-index: if defined, determines the filename for the index files. Left undefined, defaults to `index.html` |
| 42 | | * HTM-feed: if defined, this will overrite the feed URI used in HTML files. If left undefined the default `feed.atom` is used |
| 43 | | |
| 44 | | === Gemtext |
| 45 | | Likewise, there are settings for publishing on the Gemini protocol: |
| 46 | | |
| 47 | | * Gemini-index: same as `HTM-index` |
| 48 | | * Gemini-feed: same as `HTM-feed`, except `gmi.atom` is used |
