Updated docs build to use cog

README.md

@@ -304,7 +304,7 @@ The osxphotos template system also allows for limited conditional logic of the t
                   Value immediately following comma will be used if <──────┘
                   template field is False or blank (null); in this case
                   no value is specified so a blank string "" will be used
-    
+
 Like with `--directory`, using a multi-valued template field such as `{keyword}` may result in more than one copy of a photo being exported.  For example, if `IMG_1234.JPG` has keywords `Travel`, and `Vacation` and you run the following command:
 
 `osxphotos export /path/to/export --filename "{keyword}-{original_name}"`
@@ -385,7 +385,7 @@ This will write basic metadata such as keywords, persons, and GPS location to th
                            if photo is in Folder1/Folder2/Album, (>) produces
                            "Folder1>Folder2>Album" which some programs, such as
                            Lightroom Classic, treat as hierarchal keywords
-    
+
 The above command will write all the regular metadata that `--exiftool` normally writes to the file upon export but will also add an additional keyword in the exported metadata in the form "Folder1>Folder2>Album".  If you did not include the `(>)` in the template string (e.g. `{folder_album}`), folder_album would render in form "Folder1/Folder2/Album".
 
 A powerful feature of Photos is that it uses machine learning algorithms to automatically classify or label photos.  These labels are used when you search for images in Photos but are not otherwise available to the user.  osxphotos is able to read all the labels associated with a photo and makes those available through the template system via the `{label}`.  Think of these as automatic keywords as opposed to the keywords you assign manually in Photos.  One common use case is to use the automatic labels to create new keywords when exporting images so that these labels are embedded in the image's metadata:
@@ -1440,7 +1440,7 @@ characters.  The "|" character cannot be used in a find/replace pair.
 
 conditional: optional conditional expression that is evaluated as boolean     
 (True/False) for use with the ?bool_value modifier.  Conditional expressions  
-take the form ' not operator value' where not is an optional modifier that    
+take the form 'not operator value' where not is an optional modifier that     
 negates the operator.  Note: the space before the conditional expression is   
 required if you use a conditional expression.  Valid comparison operators are:
 
@@ -3495,7 +3495,9 @@ To get the path of every raw photo, whether it's a single raw photo or a raw+JPE
 ### Template System 
 
 <!-- OSXPHOTOS-TEMPLATE-HELP:START - Do not remove or modify this section -->
-The templating system converts one or template statements, written in osxphotos metadata templating language, to one or more rendered values using information from the photo being processed. 
+<!-- Generated by cog: see phototemplate.cog.md -->
+
+The templating system converts one or template statements, written in osxphotos metadata templating language, to one or more rendered values using information from the photo being processed.
 
 In its simplest form, a template statement has the form: `"{template_field}"`, for example `"{title}"` which would resolve to the title of the photo.
 
@@ -3507,7 +3509,6 @@ Template statements are white-space sensitive meaning that white space (spaces,
 
 `pretext` and `posttext` are free form text.  For example, if a photo has title "My Photo Title" the template statement `"The title of the photo is {title}"`, resolves to `"The title of the photo is My Photo Title"`.  The `pretext` in this example is `"The title if the photo is "` and the template_field is `{title}`.
 
-
 `delim`: optional delimiter string to use when expanding multi-valued template values in-place
 
 `+`: If present before template `name`, expands the template in place.  If `delim` not provided, values are joined with no delimiter.
@@ -3519,7 +3520,7 @@ e.g. if Photo keywords are `["foo","bar"]`:
 - `"{; +keyword}"` renders to: `"foo; bar"`
 - `"{+keyword}"` renders to `"foobar"`
 
-`template_field`: The template field to resolve.  See [Template Substitutions](#template-substitutions) for full list of template fields. 
+`template_field`: The template field to resolve.  See [Template Substitutions](#template-substitutions) for full list of template fields.
 
 `:subfield`: Some templates have sub-fields, For example, `{exiftool:IPTC:Make}`; the template_field is `exiftool` and the sub-field is `IPTC:Make`.
 
@@ -3527,7 +3528,6 @@ e.g. if Photo keywords are `["foo","bar"]`:
 
 Valid filters are:
 
-<!-- OSXPHOTOS-FILTER-TABLE:START - Do not remove or modify this section -->
 - `lower`: Convert value to lower case, e.g. 'Value' => 'value'.
 - `upper`: Convert value to upper case, e.g. 'Value' => 'VALUE'.
 - `strip`: Strip whitespace from beginning/end of value, e.g. ' Value ' => 'Value'.
@@ -3538,7 +3538,6 @@ Valid filters are:
 - `brackets`: Enclose value in brackets, e.g. 'value' => '[value]'
 - `shell_quote`: Quotes the value for safe usage in the shell, e.g. My file.jpeg => 'My file.jpeg'; only adds quotes if needed.
 - `function`: Run custom python function to filter value; use in format 'function:/path/to/file.py::function_name'. See example at https://github.com/RhetTbull/osxphotos/blob/master/examples/template_filter.py
-<!-- OSXPHOTOS-FILTER-TABLE:END -->
 
 e.g. if Photo keywords are `["FOO","bar"]`:
 
@@ -3561,7 +3560,7 @@ e.g. If Photo is in `Album1` in `Folder1`:
 
 `[find,replace]`: optional text replacement to perform on rendered template value.  For example, to replace "/" in an album name, you could use the template `"{album[/,-]}"`.  Multiple replacements can be made by appending "|" and adding another find|replace pair.  e.g. to replace both "/" and ":" in album name: `"{album[/,-|:,-]}"`.  find/replace pairs are not limited to single characters.  The "|" character cannot be used in a find/replace pair.
 
-`conditional`: optional conditional expression that is evaluated as boolean (True/False) for use with the `?bool_value` modifier.  Conditional expressions take the form '` not operator value`' where `not` is an optional modifier that negates the `operator`.  Note: the space before the conditional expression is required if you use a conditional expression.  Valid comparison operators are:
+`conditional`: optional conditional expression that is evaluated as boolean (True/False) for use with the `?bool_value` modifier.  Conditional expressions take the form '`not operator value`' where `not` is an optional modifier that negates the `operator`.  Note: the space before the conditional expression is required if you use a conditional expression.  Valid comparison operators are:
 
 - `contains`: template field contains value, similar to python's `in`
 - `matches`: template field contains exactly value, unlike `contains`: does not match partial matches
@@ -3605,7 +3604,7 @@ and if it is not an HDR image,
 
 - `"{hdr?ISHDR,NOTHDR}"` renders to `"NOTHDR"`
 
-`,default`: optional default value to use if the template name has no value.  This modifier is also used for the value if False for boolean-type fields (see above) as well as to hold a sub-template for values like `{created.strftime}`.  If no default value provided, "_" is used. 
+`,default`: optional default value to use if the template name has no value.  This modifier is also used for the value if False for boolean-type fields (see above) as well as to hold a sub-template for values like `{created.strftime}`.  If no default value provided, "_" is used.
 
 e.g., if photo has no title set,
 
@@ -3618,19 +3617,20 @@ e.g., if photo date is 4 February 2020, 19:07:38,
 
 - `"{created.strftime,%Y-%m-%d-%H%M%S}"` renders to `"2020-02-04-190738"`
 
-Some template fields such as `"{media_type}"` use the default value to allow customization of the output. For example, `"{media_type}"` resolves to the special media type of the photo such as `panorama` or `selfie`.  You may use the default value to override these in form: `"{media_type,video=vidéo;time_lapse=vidéo_accélérée}"`. In this example, if photo was a time_lapse photo, `media_type` would resolve to `vidéo_accélérée` instead of `time_lapse`. 
+Some template fields such as `"{media_type}"` use the default value to allow customization of the output. For example, `"{media_type}"` resolves to the special media type of the photo such as `panorama` or `selfie`.  You may use the default value to override these in form: `"{media_type,video=vidéo;time_lapse=vidéo_accélérée}"`. In this example, if photo was a time_lapse photo, `media_type` would resolve to `vidéo_accélérée` instead of `time_lapse`.
 
 Either or both bool_value or default (False value) may be empty which would result in empty string `""` when rendered.
 
 If you want to include "{" or "}" in the output, use "{openbrace}" or "{closebrace}" template substitution.
 
 e.g. `"{created.year}/{openbrace}{title}{closebrace}"` would result in `"2020/{Photo Title}"`.
+
 <!-- OSXPHOTOS-TEMPLATE-HELP:END -->
 
 The following template field substitutions are availabe for use the templating system.
 
 <!-- OSXPHOTOS-TEMPLATE-TABLE:START - Do not remove or modify this section -->
-| Substitution | Description |
+| Field | Description |
 |--------------|-------------|
 |{name}|Current filename of the photo|
 |{original_name}|Photo's original filename when imported to Photos|