From 84164b6c65bf589b3a18dee946f8ac57c26a5034 Mon Sep 17 00:00:00 2001 From: Greg Albers Date: Wed, 11 Feb 2026 14:51:28 -0800 Subject: [PATCH 1/3] Update possible contributor formats for bylineFormat --- content/docs-v1/metadata-configuration.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/docs-v1/metadata-configuration.md b/content/docs-v1/metadata-configuration.md index 65a0514b..a617484c 100644 --- a/content/docs-v1/metadata-configuration.md +++ b/content/docs-v1/metadata-configuration.md @@ -46,10 +46,10 @@ analytics: ### Bylines -Set how [contributor](/docs-v1/contributors/) names are listed in page headers: by name only (`name`); by name with their title and affiliation (`name-title`); or with no listing at all (`false`). +Set how [contributor](/docs-v1/contributors/) names are listed in page headers: by a list of initials concatenated into a string with commas (`initials`); a line-by-line list of names only (`name`); a line-by-line list of names with their title and affiliation (`name-title`); the names concatenated into a string with commas (`string`); or with no listing at all (`false`). ```yaml -bylineFormat: name-title # name | name-title | false +bylineFormat: name-title # initials | name | name-title | string | false ``` ### Bibliography From 8b55b60b10caef1f7f773ad73c5f334b925887a9 Mon Sep 17 00:00:00 2001 From: Greg Albers Date: Wed, 11 Feb 2026 14:52:40 -0800 Subject: [PATCH 2/3] Ensure github pages deploy branch naming is consistent --- content/docs-v1/site-deploy.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/docs-v1/site-deploy.md b/content/docs-v1/site-deploy.md index 6af0ccde..e4250e95 100644 --- a/content/docs-v1/site-deploy.md +++ b/content/docs-v1/site-deploy.md @@ -126,7 +126,7 @@ GitHub enables you to not only host your project code, but you can also use it t 2. Update the `url` in `content/_data/publication.yaml` to correspond to your own GitHub site. It will follow the pattern: https://YOUR-USERNAME.github.io/YOUR-PROJECT-DIRECTORY-NAME/. So, if your GitHub username is bonjovi and your project file is blaze-of-glory, your `baseURL` would be https://bonjovi.github.io/blaze-of-glory/. (Note: your GitHub username can also be your organization name if that is how your account is set up in GitHub.) Be sure to commit this update and push to origin. -3. In your command-line shell, make sure you are in your project folder and run `git checkout -b gh-deploy`, which creates a new temporary branch called `gh-deploy` to work in. This command will automatically switch you to that branch. +3. In your command-line shell, make sure you are in your project folder and run `git checkout -b gh-pages`, which creates a new temporary branch called `gh-pages` to work in. This command will automatically switch you to that branch. 4. Next, run `quire build`. Check to make sure there are no errors mentioned in the Terminal before proceeding. @@ -140,7 +140,7 @@ GitHub enables you to not only host your project code, but you can also use it t If prompted to sign in, do so with your GitHub username and password. If you have two-factor authentication enabled, you'll use a [personal access token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens) in place of a password. Remember, you will not be able to see your username or password as you type them. Hit enter once you are done typing to advance. -9. In your command-line shell, run `git checkout main && git branch -D gh-deploy` to delete the temporary deploy branch and to switch back to your `main` branch. If you were publishing from a branch other than `main`, use that name in here instead, like `git checkout YOUR-BRANCH-NAME && git branch -D gh-deploy`. +9. In your command-line shell, run `git checkout main && git branch -D gh-pages` to delete the temporary deploy branch and to switch back to your `main` branch. If you were publishing from a branch other than `main`, use that name in here instead, like `git checkout YOUR-BRANCH-NAME && git branch -D gh-pages`. 10. If your repository is private, you will need to navigate to your repository's settings page. Scroll down to the "Danger Zone," click "Change repository visibility," and change the visibility to public. From 60a3533c48625d9a389a12ac26d3dc04a9eb75b1 Mon Sep 17 00:00:00 2001 From: Greg Albers Date: Wed, 11 Feb 2026 15:58:19 -0800 Subject: [PATCH 3/3] Better describe bylineFormat options --- content/docs-v1/metadata-configuration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs-v1/metadata-configuration.md b/content/docs-v1/metadata-configuration.md index a617484c..1e2e2bed 100644 --- a/content/docs-v1/metadata-configuration.md +++ b/content/docs-v1/metadata-configuration.md @@ -46,7 +46,7 @@ analytics: ### Bylines -Set how [contributor](/docs-v1/contributors/) names are listed in page headers: by a list of initials concatenated into a string with commas (`initials`); a line-by-line list of names only (`name`); a line-by-line list of names with their title and affiliation (`name-title`); the names concatenated into a string with commas (`string`); or with no listing at all (`false`). +Set how [contributor](/docs-v1/contributors/) names are listed in page headers: each contributor’s initials concatenated into a string with commas (`initials`); each contributor’sname on its own line (`name`); each contributor’s name on its own line along with their title and affiliation (`name-title`); contributor’s name concatenated into a string with commas (`string`); or with no listing at all (`false`). ```yaml bylineFormat: name-title # initials | name | name-title | string | false