feat: capture bodies from every feed, rename to Read More, anchor the button

[craigthackerx]

Three changes: bodies for every source, the button renamed, and the button pinned to the bottom left of the card.

Bodies from every feed

Answering the question behind this: nothing else had a Read More button because RSS articles carried no body field at all, not because a body was being truncated. The 300 character cap applies to summary, which is a different field.

Which turned out to be a missed opportunity, because the pipeline was already reading far more than it kept:

Source	summary	content:encoded
Microsoft Security Blog	695	62,233
Threat Intelligence	700	62,389
CISA	52,691	-
Tech Community (Sentinel)	35,891	-
Tech Community (Defender XDR)	24,236	-
AWS	2,086	-
Google Cloud	2,040	2,040
MSRC	22	-
NCSC	154	-

Bodies now come from content:encoded where the feed populates it, falling back to the summary.

Result: 100 of 150 articles get a Read More button, up from 12.

	articles	with body
gcp_security	25	22
cisa_security	20	20
mssecurity	10	10
core_infra_security	10	10
sentinel	7	7
aws_security	8	7
defender_xdr	4	4
...others
azure_updates	13	0
ncsc_security	7	0
msrc	20	0

The three zeroes are correct: MIN_BODY_LENGTH keeps the button off anything whose feed carries barely more than a headline, so Read More never opens to the same text the card already shows.

Size

feeds.json goes from 205 KB to 431 KB at a 2500 character cap, roughly 470 KB once Message Center is included. Acceptable in one file for now; if it becomes uncomfortable the next step is splitting bodies into a second JSON the dialog fetches lazily on expand.

Message Center keeps a 6000 cap, because it is the only source whose link does not work for a reader. Anything cut there is unreachable, whereas every RSS article keeps a working link to its full text.

Read More

Renamed everywhere, including Message Center, per the request.

Button anchoring

The buttons floated at different heights because the card was a plain block, so the button sat wherever the summary happened to end.

Cards in a grid row already stretch to equal height, so the fix is to make the card a column flexbox and give the button margin-top: auto. That eats the leftover space and lands every button on the same baseline. align-self: flex-start keeps it bottom left rather than stretched to the card width, and .article-summary gets an explicit margin-bottom so a full card (where auto resolves to zero) still keeps the text clear of the button.

Verification

Bodies stay plain text and links keep their scheme check at both ends, unchanged from the previous PR.

jsdom against the real index.html, app.js and styles.css, 19 checks passing. New ones:

PASS button reads "Read More"
PASS button is the card's last child, so margin-top:auto anchors it to the bottom
PASS card is a column flexbox
PASS button uses margin-top:auto
PASS button aligned to the left, not stretched

jsdom does not do layout, so the three layout assertions check the CSS rules that produce the anchoring rather than the rendered geometry. Worth an eyeball on the deployed site.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None