update existing entry text for clarity, adds OP

.cspell/custom-dictionary-workspace.txt

@@ -1,10 +1,27 @@
 # Custom Dictionary Words
+Bluesky
 cdaps
+chromeos
+cloudflareinsights
 CTAP
+Descope
+errorf
 geolocation
+gethinode
+getstarted
+Hanko
+hinode
+isset
 Keychain
 lastmod
+nosniff
+opengraph
+reauth
 Reauthentication
+SAMEORIGIN
+unshallow
 upsell
 UVRA
 webauthn
+webshare
+Yubico

.git-hooks/pre-commit

@@ -0,0 +1,4 @@
+#!/bin/bash
+
+echo "Running pre-commit checks..."
+markdownlint-cli2 "*.md" "content/**/*.md"

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,41 @@
+<!--
+     For Work In Progress Pull Requests, please use the Draft PR feature,
+     see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details.
+
+     For a timely review/response, please avoid force-pushing additional
+     commits if your PR already received reviews or comments.
+
+     Before submitting a Pull Request, please ensure you've done the following:
+     - 👷‍♀️ Create small PRs. In most cases this will be possible.
+     - 📝 Use descriptive commit messages.
+
+     NOTE: Pull Requests from forked repositories will need to be reviewed by
+     a passkeys.dev maintainer before any CI builds will run.
+-->
+
+## What type of PR is this? (check all applicable)
+
+- [ ] Minor content update (spelling, grammar)
+- [ ] Substantive content update (changes meaning)
+- [ ] Net new content
+- [ ] Reference content update (platforms, device support, etc)
+- [ ] Core platform updates (Hugo / Hinode / Cloudflare)
+- [ ] Administrivia / chores
+
+## Description, Motivation, and Context
+
+<!--- Describe your changes in detail. Why is this change required? What problem does it solve? -->
+
+## Related Issues
+
+<!--
+For pull requests that relate or close an issue, please include them
+below.  We like to follow [Github's guidance on linking issues to pull requests](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue).
+
+For example having the text: "closes #1234" would connect the current pull
+request to issue 1234.  And when we merge the pull request, Github will
+automatically close the issue.
+-->
+
+- Related Issue #
+- Closes #

.gitignore

@@ -1,5 +1,11 @@
-node_modules
-public
-resources
+/_vendor
+/prebuild
+/public
+resources/
+node_modules/
+
+.DS_store
+.hugo_build.lock
 .netlify
-.hugo_build.lock
+
+hugo

.markdownlint-cli2.jsonc

@@ -4,8 +4,11 @@
     "MD013": false,
     "MD024": false,
     "MD026": false,
-    "MD033": false,
-    "MD034": false
+    "MD034": false,
+    "MD051": false,
+    "MD053": false,
+    "MD055": false,
+    "MD056": false
   },
-  "ignores": ["node_modules", "CHANGELOG.md", "README.md"]
+  "ignores": ["node_modules", "CHANGELOG.md"]
 }