The following open source packages are fully or partially included with ACMEdoc.

Package

Jekyll Documentation Theme

License

MIT

Author

Tom Johnson

Website

https://github.com/tomjoht/documentation-theme-jekyll

Package

M+ OUTLINE FONTS (M+ TESTFLIGHT 058)

License

unlimited

Author

M+ Fonts Project

Website

http://mplus-fonts.osdn.jp/about-en.html

Package

Noto Fonts

License

SIL OFL

Author

Google i18n

Website

https://www.google.com/get/noto/

Package

Font Awesome

License

SIL OFL 1.1

Author

Fonticons, Inc

Website

https://fontawesome.com/
How this appendix is sourced

This file is not sourced as YAML but rather as plain text for a couple of reasons. First of all, this file is traditionally named NOTICE and kept prominently in the root directory in open-source projects.

More importantly, since this file must be present in this open-source project where it is distributed (GitHub), we do not want to duplicate the source. So we store it in a very human-readable plaintext format, then we extract data from it during the parsing step of the build routine.

Here is the NOTICE file in its entirety:

ACMEdoc NOTICE file
The following permissively licensed software is packaged with ACMEdoc.

Jekyll Documentation Theme | MIT | (c) Tom Johnson | https://github.com/tomjoht/documentation-theme-jekyll

M+ OUTLINE FONTS (M+ TESTFLIGHT 058) | unlimited | (c) M+ Fonts Project | http://mplus-fonts.osdn.jp/about-en.html

Noto Fonts | SIL OFL (https://github.com/googlei18n/noto-fonts/blob/master/LICENSE) | (c) Google i18n | https://www.google.com/get/noto/

Font Awesome | SIL OFL 1.1 (http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&id=OFL) | (c) Fonticons, Inc | https://fontawesome.com/

And here is the section from _configs/build-docs.yml that instructs the data extraction:

From build-docs.yml
# Generate structured NOTICE output
- action: parse
  data:
    file: NOTICE
    type: regex
    pattern: ^(?<name>.*)\s\|\s(?<license>[a-zA-Z0-9\.\s]+)\s(\(http(?<license_url>.*\))\s)?\|\s\(c\)\s(?<author>.*)\s\|\s(?<package_url>.*)$
  builds:
    - template: _templates/liquid/dependencies.asciidoc
      output: build/includes/built/dependencies_table.adoc
META AF!
Here again we find examples of code listings drawn from their canonical source. The NOTICE file in its entirety, and a segnment of the build configuration YAML using include::../_configs/build-docs.yml[tags=regex-notice].