My personal blog, hosted at https://blog.dwac.dev/.

This project uses NodeJS and must be installed. You can install it directly or install nvm.

nvm install
npm install -g pnpm@10.11.0
pnpm install --frozen-lockfile

Run a hot-reloading server with pnpm start. Open http://localhost:8080/ to view the local site.

You can make a one-off build with pnpm run build. This is not all that useful for local development, but CI takes advantage of it.

You can debug the build in VSCode with the 11ty Build launch configuration. This will run a build and attach the VSCode debugger to each process as it executes. This should trigger breakpoints in .eleventy.js and any related files.

You can also run pnpm run build:debug to run the build pipeline with --inspect-brk on the relevant command to breakpoint on the 11ty execution.

You can run/build for production by using pnpm run start:prod and pnpm run build:prod. These enable various optimizations for production use. Note that pnpm run start:prod will encounter a CSP error and live reload will not work, as browser sync is not included in prod.

Run all tests once with pnpm test.

There are two sets of tests that are executed:

1. Tests of the NodeJS code used in the 11ty build.
   • Run directly with pnpm run test:11ty.
   • Debug with the 11ty Test launch configuration in VSCode.
2. Tests of the client browser code.
   • Run directly with pnpm run test:browser.
   • Watch with pnpm run test:browser:dev.
   • Debug with pnpm run test:browser:dev and open http://localhost:9876/debug.html. This should include include an HTML reporter, live reloads, and functioning source maps.

This repo deploys with Netlify. The CI GitHub action contains part of the configuration, while the rest is done on Netlify directly.

• The deploy branch is pushed to production immediately after a push to GitHub.
  • Only deployed if CI passes.
  • Hosted at https://blog.dwac.dev/ and https://dwac-blog.netlify.app/.
• The main branch is auto-deployed on GitHub push.
  • Only deployed if CI passes.
  • Hosted at https://main-preview--dwac-blog.netlify.app.
• Any posts/* branches are auto-deployed on GitHub push.
  • These are previews of in-progress posts, so tests are not executed here.
  • Listed at https://blog.dwac.dev/preview/.
  • Hosted at https://post-${branch-name}--dwac-blog.netlify.app.

You can also perform one-off test deployments to verify the Netlify configuration and the real production environment. Build the application first, then use pnpm run deploy-test ${alias} to deploy it to Netlify. This should generate a URL for you to visit and test the site with. It is also an easy way to test on mobile phones without having to run the site locally.

Looking for more documentation about the project? Take a look at our docs!

Resources not stored in source control (like original, uncompressed images) are stored in a DWAC Google Drive folder.

See analytics docs.

The domain is registered with porkbun and uses their default DNS nameservers.

Domains are configured with Netlify via DNS CNAME redirects. blog.dwac.dev redirects to dwac-blog.netlify.app which is updated from the deploy branch.

*.dev domains must use HSTS, so SSL/TLS is required. The certificate is provisioned from Let's Encrypt via Netlify's native integration.

Google Search Console can be accessed here.