Supplemental UI file scanner should not ignore dot (aka hidden) files
The supplemental UI file scanner currently ignores ignores dot (aka hidden) files. However, it's perfectly valid to have UI files that begin with a dot, such as .nojekyll or .htaccess. If the file scanner ignores these files, then they cannot be registered as static files (and those don't get copied to the published site).
Follow these steps to reproduce the problem:
-
Create the supplemental-ui folder in the playbook repository
-
Configure the playbook to instruct Antora to use this directory
ui: supplemental_files: ./supplemental-ui
-
Create the empty file supplemental-ui/.nojekyll
-
Create the file supplemental-ui/ui.yml with the following contents:
static_files: [.nojekyll]
Antora will not copy the .nojekyll file to the published site.
This is the local file-based equivalent of the strategy described at https://docs.antora.org/antora/2.3/publish-to-github-pages/ (which covers the memory file-based solution). This becomes a problem when the local file-based strategy must be used to copy binary files such as a favicon.
We could still consider throwing away dotfiles which are not marked as static files. (In other words, dotfiles which don't get promoted to the site root).