Adds /feed/sas-special-missings/ - "28 Ways to Be Missing in SAS".
Why a feed post, not a blog post
The special missings material was originally added to content/blog/v4-0-formats-special-missings/. That article is the v4.0 release announcement, so teaching copy does not belong in it. This revision reverts those blog edits and publishes the content as its own feed post instead - the branch is now a single commit adding the feed post, with no blog changes.
What the post covers
What special missings are: 28 numeric missing values, why they exist, and how they behave as numbers (arithmetic, PROC MEANS, sort order, NMISS/CMISS, CATS)
How Data Controller carries them between the browser and SAS: the SASjs Adapter's type inference, the explicit-format path for columns whose type cannot be inferred, and the values it refuses
What the validation rules do with them: NOTNULL passes, MINVAL fails, MAXVAL passes, CASE compares as text, and HARDREGEX/SOFTREGEX apply rather than exempting them
The "Managing Special Missing Values with Data Controller for SAS" recording
Verified
npm run build succeeds; the page renders at /sas-special-missings/ with the video iframe, it appears in the feed listing and in /rss.xml, and the blog post is back to its original content.
Notes
No cover image yet. The image prompt is recorded in a comment at the foot of the file - drop the generated image in as ./cover.jpeg and add previewImg: './cover.jpeg' to the front matter.
Reverting the blog edits also drops the one-line video label fix that was in the earlier revision of this PR. The blog post still labels the special missings video as "Retain Formulas when Loading Excel to SAS", which is the wrong video title - worth a separate one-line PR if you want it corrected.
Adds `/feed/sas-special-missings/` - "28 Ways to Be Missing in SAS".
### Why a feed post, not a blog post
The special missings material was originally added to `content/blog/v4-0-formats-special-missings/`. That article is the v4.0 **release announcement**, so teaching copy does not belong in it. This revision reverts those blog edits and publishes the content as its own feed post instead - the branch is now a single commit adding the feed post, with no blog changes.
### What the post covers
- What special missings are: 28 numeric missing values, why they exist, and how they behave as numbers (arithmetic, PROC MEANS, sort order, NMISS/CMISS, CATS)
- How Data Controller carries them between the browser and SAS: the SASjs Adapter's type inference, the explicit-format path for columns whose type cannot be inferred, and the values it refuses
- What the validation rules do with them: NOTNULL passes, MINVAL fails, MAXVAL passes, CASE compares as text, and HARDREGEX/SOFTREGEX apply rather than exempting them
- The "Managing Special Missing Values with Data Controller for SAS" recording
### Verified
`npm run build` succeeds; the page renders at `/sas-special-missings/` with the video iframe, it appears in the feed listing and in `/rss.xml`, and the blog post is back to its original content.
### Notes
- No cover image yet. The image prompt is recorded in a comment at the foot of the file - drop the generated image in as `./cover.jpeg` and add `previewImg: './cover.jpeg'` to the front matter.
- Reverting the blog edits also drops the one-line video label fix that was in the earlier revision of this PR. The blog post still labels the special missings video as "Retain Formulas when Loading Excel to SAS", which is the wrong video title - worth a separate one-line PR if you want it corrected.
The special missings material that was added to the v4.0 blog post belongs in
its own post: that article is a release announcement for v4.0, not a teaching
piece. This reverts the blog change and publishes the content under /feed/.
The new post covers what SAS special missings are, how the SASjs Adapter
carries them between the browser and SAS, and how Data Controller's validation
rules treat them - NOTNULL passes, MINVAL fails, MAXVAL passes, and the regex
rules apply as they would to any other value.
The LinkedIn version of the copy, and the image prompt for the cover, are
recorded in a comment at the foot of the file.
hermes
changed title from blog: teach special missings properly, and fix the video label to feed: add a special missings post2026-09-22 17:54:12 +00:00
The special missings video was labelled "Retain Formulas when Loading Excel
to SAS", which is a different video. Restores the one-line correction that
was in the earlier revision of this branch, kept separate from the feed post.
Reviewed the full base-to-head diff (new feed post plus the blog video-label fix) and repo-level hardening at this head.
content/feed/sas-special-missings/index.md:1-10 - front matter carries no previewImg and the post directory contains only index.md, no cover image. The file's own instructions at index.md:93 say to save the generated cover as ./cover.jpeg and set previewImg: './cover.jpeg' in the front matter. The templates tolerate the omission (src/templates/postpreview/index.tsx:50 renders the image conditionally), so the build stays green, but the post ships into the feed list and social shares with no image; 14 of the 16 existing feed posts carry a cover. Generate the cover and add previewImg before merge, or drop the prompt comment if the image is landing separately.
Repo-level, standing (not introduced by this PR): no .pre-commit-config.yaml and no gitleaks hook anywhere in this repo, so no staged-content secret scan exists at commit time. Add .pre-commit-config.yaml with repo: https://github.com/gitleaks/gitleaks, rev pinned to the exact current release tag (v8.30.1 at time of review), hooks: - id: gitleaks.
CI (.gitea/workflows/publish.yml and .github/workflows/publish.yml): npm ci + build + publish on push to main only. No npm audit step exists in any workflow and no pipeline runs on pull requests, so nothing gates dependency vulnerabilities or a broken build before merge. Add a strict audit step (default audit level, hard failure, no continue-on-error) and run at least the build on pull_request.
Pre-existing (not from this PR): all 37 entries across dependencies and devDependencies in package.json are ^ ranges, contradicting the committed .npmrc save-exact=true; the lockfile holds the line today but the ranges invite drift on the next dependency touch. Also .gitignore has no .env or .env.* entry, although Gatsby conventionally loads configuration from .env files.
No semantic-release or conventional-commit tooling in this repo, so the non-conventional commit subjects (feed:, blog:) have no release effect.
4 findings above for review.
Reviewed the full base-to-head diff (new feed post plus the blog video-label fix) and repo-level hardening at this head.
- content/feed/sas-special-missings/index.md:1-10 - front matter carries no previewImg and the post directory contains only index.md, no cover image. The file's own instructions at index.md:93 say to save the generated cover as ./cover.jpeg and set previewImg: './cover.jpeg' in the front matter. The templates tolerate the omission (src/templates/postpreview/index.tsx:50 renders the image conditionally), so the build stays green, but the post ships into the feed list and social shares with no image; 14 of the 16 existing feed posts carry a cover. Generate the cover and add previewImg before merge, or drop the prompt comment if the image is landing separately.
- Repo-level, standing (not introduced by this PR): no .pre-commit-config.yaml and no gitleaks hook anywhere in this repo, so no staged-content secret scan exists at commit time. Add .pre-commit-config.yaml with repo: https://github.com/gitleaks/gitleaks, rev pinned to the exact current release tag (v8.30.1 at time of review), hooks: - id: gitleaks.
- CI (.gitea/workflows/publish.yml and .github/workflows/publish.yml): npm ci + build + publish on push to main only. No npm audit step exists in any workflow and no pipeline runs on pull requests, so nothing gates dependency vulnerabilities or a broken build before merge. Add a strict audit step (default audit level, hard failure, no continue-on-error) and run at least the build on pull_request.
- Pre-existing (not from this PR): all 37 entries across dependencies and devDependencies in package.json are ^ ranges, contradicting the committed .npmrc save-exact=true; the lockfile holds the line today but the ranges invite drift on the next dependency touch. Also .gitignore has no .env or .env.* entry, although Gatsby conventionally loads configuration from .env files.
No semantic-release or conventional-commit tooling in this repo, so the non-conventional commit subjects (feed:, blog:) have no release effect.
4 findings above for review.
Replaces the placeholder one-liner with the prompt actually intended for the
cover: the pack of wolves on a snow plain at dusk with one animal standing
apart, plus the negative constraints, the output spec (./cover.jpeg at
1200x627, previewImg in front matter) and a fallback single-subject variant.
Two deliberate choices are recorded so they are not lost on a regenerate:
- No text, letters or numbers anywhere in the image. The subject is letters
standing in for numbers, so a stray glyph undercuts the cover.
- No exact head count of 28. Generators cannot count, and a crowded pack reads
worse than a dozen clear animals; the number belongs in the headline.
Links to the full prompt and variants on paste.4gl.io.
Cover art for "28 Ways to Be Missing in SAS": a pack of wolves on a snow plain
at dusk with one animal standing apart, carrying the post's opening line - a
numeric missing is not a lone wolf, there are 28 of them.
Source image was 4:3, so it is cropped to 1.91:1 (1200x627) to match the other
feed covers and double as the LinkedIn share card. The crop was chosen to keep
both the lone wolf on the left and the full pack on the right in frame, losing
only sky above the clouds and foreground snow.
Sets previewImg in the front matter; the template renders it, so it is not
embedded in the body as well. Verified through gatsby build - the image
pipeline emits 300/600/1200-wide variants.
You are not authorized to merge this pull request.
This pull request can be merged automatically.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
hermes
Adds
/feed/sas-special-missings/- "28 Ways to Be Missing in SAS".Why a feed post, not a blog post
The special missings material was originally added to
content/blog/v4-0-formats-special-missings/. That article is the v4.0 release announcement, so teaching copy does not belong in it. This revision reverts those blog edits and publishes the content as its own feed post instead - the branch is now a single commit adding the feed post, with no blog changes.What the post covers
Verified
npm run buildsucceeds; the page renders at/sas-special-missings/with the video iframe, it appears in the feed listing and in/rss.xml, and the blog post is back to its original content.Notes
./cover.jpegand addpreviewImg: './cover.jpeg'to the front matter.d059b72f6bto4937edd7f4blog: teach special missings properly, and fix the video labelto feed: add a special missings postReviewed the full base-to-head diff (new feed post plus the blog video-label fix) and repo-level hardening at this head.
content/feed/sas-special-missings/index.md:1-10 - front matter carries no previewImg and the post directory contains only index.md, no cover image. The file's own instructions at index.md:93 say to save the generated cover as ./cover.jpeg and set previewImg: './cover.jpeg' in the front matter. The templates tolerate the omission (src/templates/postpreview/index.tsx:50 renders the image conditionally), so the build stays green, but the post ships into the feed list and social shares with no image; 14 of the 16 existing feed posts carry a cover. Generate the cover and add previewImg before merge, or drop the prompt comment if the image is landing separately.
Repo-level, standing (not introduced by this PR): no .pre-commit-config.yaml and no gitleaks hook anywhere in this repo, so no staged-content secret scan exists at commit time. Add .pre-commit-config.yaml with repo: https://github.com/gitleaks/gitleaks, rev pinned to the exact current release tag (v8.30.1 at time of review), hooks: - id: gitleaks.
CI (.gitea/workflows/publish.yml and .github/workflows/publish.yml): npm ci + build + publish on push to main only. No npm audit step exists in any workflow and no pipeline runs on pull requests, so nothing gates dependency vulnerabilities or a broken build before merge. Add a strict audit step (default audit level, hard failure, no continue-on-error) and run at least the build on pull_request.
Pre-existing (not from this PR): all 37 entries across dependencies and devDependencies in package.json are ^ ranges, contradicting the committed .npmrc save-exact=true; the lockfile holds the line today but the ranges invite drift on the next dependency touch. Also .gitignore has no .env or .env.* entry, although Gatsby conventionally loads configuration from .env files.
No semantic-release or conventional-commit tooling in this repo, so the non-conventional commit subjects (feed:, blog:) have no release effect.
4 findings above for review.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.