11ty

[edthedev]

• Adds 11ty configuration files.
• Adds a GitHub Action to publish converted HTML output to the gh-pages branch each the main branch changes.
• Converts main page and github-actions pages to Markdown.
• Adds an eleventy page that describes this setup.
• Moves examples to root so that 11ty knows not to modify them.
• MISSING: Does not do breadcrumb navigation. This is doable, but deserves a separate pull request.

[edthedev]

UPDATE: The latest version of the GitHub action can use an on-the-fly generated token, so I have deleted both halves of the key pair from the repository.

Note that the GitHub Action requires GitHub to store a public and private key pair. I generated a new pair, and added them to this repository.

Public key is stored here to allow deployment to the gh-pages branch:

Private key is stored here to allow the GitHub action to do the deployment to the gh-pages branch:

Note pull requests that originate in forks outside this organization do not have access to the private key (GitHub enforces this), since that would allow a malicious user to fork and update without permission.

As a security nerd, naturally I threw away my copies of these 2 files. If we need to update them, we can just regenerate and replace them.

[edthedev]

@jtgorman Sounds good. It works when testing locally. Unless anyone else has comments, I will plan to merge this early some morning this week, when I have some time after to either revert or correct any issues.

[edthedev]

The site is being served from the gh-pages branch now. Updating any markdown files and either pushing to the master branch or merging a pull request into the master branch will kick off the GitHub action which will regenerate the HTML and push it to the gh-pages branch.

[edthedev]

Note that doing a quick live edit on the Mardown files in master via the GitHub web interface also works fine.