add multisite bottleneck post and asset graphics

[shrinkray]

• add new featured post
• add five images
• create huskyrc config so Husky sources NVM when hooking into GUI apps (Github Desktop)

[Copilot]

Pull request overview

This PR adds a new featured blog post about mitigating performance bottlenecks in a high-traffic WordPress Multisite setup, along with supporting assets, and updates the Husky pre-commit hook to better handle Node/NVM path resolution in GUI Git clients.

Changes:

• Add a new featured long-form post: “Taming WordPress Multisite Bottlenecks: Bot Mitigation & Cron Health with a Custom Plugin”.
• Reference new /public/assets/* graphics used by the post.
• Update .husky/pre-commit to source NVM / adjust PATH when npx isn’t available (e.g., GitHub Desktop environments).

Reviewed changes

Copilot reviewed 2 out of 7 changed files in this pull request and generated 2 comments.

File	Description
src/contents/taming-wordpress-multisite-bottlenecks-bot-mitigation-cron-health-with-a-custom-plugin.md	New featured content post with multiple embedded asset images and a CTA section.
.husky/pre-commit	Adds environment bootstrapping for GUI Git clients before running npx lint-staged.

Comments suppressed due to low confidence (2)

src/contents/taming-wordpress-multisite-bottlenecks-bot-mitigation-cron-health-with-a-custom-plugin.md:66

• This alt text is quite vague compared to the more descriptive alt text used elsewhere in the blog content. More specific alt text makes the post more accessible and improves the usefulness of the content when images don’t load.

![IP tracking and management](/assets/perfguard-dashboard.webp)

src/contents/taming-wordpress-multisite-bottlenecks-bot-mitigation-cron-health-with-a-custom-plugin.md:101

• Alt text here is non-descriptive. Using a more specific description (as in other posts) improves accessibility and helps readers understand the image contextually.

![cron health overview](/assets/perfguard-cronhealth.webp)

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[cloudflare-workers-and-pages]

Deploying devcharms with    Cloudflare Pages

Latest commit:	d4075ce
Status:	✅  Deploy successful!
Preview URL:	https://3b7fdbc5.devcharms.pages.dev
Branch Preview URL:	https://write-pluginpost.devcharms.pages.dev

View logs

[shrinkray]

Updated both items requested:

1. Descriptive Alt Text in Markdown Post
   Updated image tags in

2. POSIX Shell Compatibility in Husky Hooks
   Updated

.husky/pre-commit
and ~/.huskyrc to ensure POSIX-sh compliance:

Prepend common Node/Homebrew binary paths (/usr/local/bin, /opt/homebrew/bin, $HOME/Library/pnpm, and $HOME/.nvm/versions/node//bin) directly to PATH.
Restrict nvm.sh sourcing to shells running bash or zsh (BASH_VERSION / ZSH_VERSION), avoiding syntax errors on Linux distributions where /bin/sh maps to dash.
Verified execution under POSIX sh with restricted PATH (PATH="/usr/bin:/bin:/usr/sbin:/sbin").

[Copilot]

Pull request overview

Copilot reviewed 2 out of 7 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (1)

.husky/pre-commit:15

• latest_nvm_bin is derived via ls ... | tail -n 1, which picks the lexicographically-last entry, not the newest/active Node version (e.g., v9.* sorts after v10.*). Also, if the glob produces no matches, latest_nvm_dir can be empty and the logic can accidentally add /bin to PATH. Prefer selecting by mtime and guard against an empty result.

  if [ -d "$HOME/.nvm/versions/node" ]; then
    latest_nvm_bin="$(ls -d "$HOME/.nvm/versions/node/"* 2>/dev/null | tail -n 1)/bin"
    if [ -d "$latest_nvm_bin" ]; then
      export PATH="$latest_nvm_bin:$PATH"
    fi