docs: add curated highlights to 2026 Cloud release notes - #2764
Draft
claudiacodacy wants to merge 8 commits into
Draft
claudiacodacy wants to merge 8 commits into
claudiacodacy wants to merge 8 commits into
Conversation
Opens each 2026 monthly Cloud roundup with a short headline feature and "why it matters" framing, then bundles the rest of the month's changes in one sentence, inspired by the Claude Code "What's new" digest. Mirrors the same highlight as a one-line summary next to each 2026 entry in the release notes index. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Contributor
|
Overall readability score: 54.13 (🔴 -0.01)
View detailed metrics🟢 - Shows an increase in readability
Averages:
View metric targets
|
Contributor
Up to standards ✅🟢 Issues
|
Replaces the hand-duplicated one-line summary in the index with a transcluded snippet from each monthly page's own opening paragraph, marked with <!--highlight--> / <!--/highlight--> comments. Uses the include-markdown plugin already installed in this repo (previously only used for docs/assets/includes/ boilerplate, not page-to-page), so the highlight text lives in exactly one place and can't drift. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Wraps each highlighted entry's body in a release-digest__body span and extends the existing #codacy-release-notes list styling in home.css with a two-column grid (period label, then digest content) for rows that carry a highlight, inspired by the Claude Code "What's new" page. Entries without a highlight (single-topic announcements, older years) are untouched and keep rendering as plain rows. Verified in the browser: light and dark color schemes at desktop width, and dark scheme at mobile width where the grid collapses to a single column via the new responsive.css rule. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Adds a <!--highlight--> snippet to the 7 remaining 2026 single-topic release notes (Oxlint, Shellcheck config, PHP CS Fixer/Checkov config, PHP_CodeSniffer upgrade, GitHub integration changes, Semgrep/Opengrep, GolangCI-Lint client-side) and wires them into index.md the same way as the monthly roundups, so every 2026 entry uses the same two-column digest treatment instead of only the 8 monthly ones. Verified in the browser: all 15 entries transclude and render correctly, the list transitions cleanly into the untouched 2025 section, and long titles (PHP CS Fixer/Checkov) wrap without breaking the grid. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Replaces each 2026 entry's link text (previously the page's own title, ranging from a plain "Cloud August 2026" to a full sentence like "PHP_CodeSniffer Upgrade and Legacy Package Deprecations July, 2026") with just its "Month Year". The topic already lives in the transcluded highlight's bold lead-in, so the old title was duplicating it while also making the label column wildly inconsistent in length. Every row now has a uniform, single-line label, closer to how the Claude Code "What's new" page separates the period from the content. Verified in the browser: light and dark schemes, full list scroll including the four same-month July rows and the 2026/2025 boundary. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Replaces the {% include-markdown %} calls in index.md with the same
highlight text written directly in the list — simpler than keeping a
build-time dependency between 15 source files and the index for a
page that, once published, rarely changes. The <!--highlight--> /
<!--/highlight--> markers are removed from all 15 source pages; the
sentence itself stays as a plain intro paragraph on each page.
Also:
- Drops the leading em dash before each digest body — the two-column
grid already separates the date from the content, so it was
redundant.
- Fixes the bullet dot's vertical alignment on digest rows: it was
centered for the old single-line row height and sat visibly above
the label once rows grew to 2-4 lines.
Verified in the browser: rebuilt getComputedStyle numbers show the dot
is now centered on the label's first line (0.26px off, previously
~5px), and checked light/dark rendering of the full 2026 list.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
- Removes the ::before bullet dot from the release notes list entirely (both plain and digest rows) instead of re-tuning its position, and tightens the now-unneeded left padding that made room for it. - Replaces "Month Year" labels with the actual day, pulled from git history (the commit that first added each file) rather than invented. Flagging one anomaly in the handoff: the January roundup's git date falls inside the month it summarizes rather than after it, unlike every other monthly roundup. - For months with more than one main feature, names all of them instead of just the headline one, while leaving bug fixes and minor improvements out — matches the Features/Improvements split already used on the June/July/August pages, applied by judgment on the earlier months that only have a flat "Product enhancements" list. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
For months with more than one main feature, each now gets its own bold-led paragraph (separated by a blank line) using the wording from that page's own Features/Product enhancements section, rather than being paraphrased into one run-on "Also new: ..." sentence. Dropped internal ticket references (OD-xxx, CF-xxx, TCE-xxx) since they're not meaningful to an external reader, and the one instance of "robust" (banned by voice.md) in the January entry. Also removes the bold weight from the date label — it now matches the rest of the list's link styling, just distinguished by color. Verified in the browser: all 15 entries render with clean paragraph spacing at the row heights this produces (August and July now run 4 paragraphs each), and confirmed via get_page_text/screenshots that content earlier screenshots seemed to cut off was a scroll-timing artifact, not a rendering bug — the full HTML output was always complete. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
cloud-2026-01.mdthroughcloud-2026-08.md) with a short headline paragraph naming the month's most notable feature and why it matters, followed by a one-sentence "Also this month" round-up of the rest — inspired by the Claude Code "What's new" digest.docs/release-notes/index.md, so scanning the index gives the same at-a-glance value.This is the smallest version of a larger proposal to bring a Claude-style curated digest to our release notes; see conversation for the full write-up and what was deliberately left alone (the monthly Features/Improvements/Tool versions structure, which stays the "full changelog" layer).
Test plan
mkdocs build --strict— passes with no new warnings or errorsvaleon all 9 changed files — flags pre-existing, already-accepted patterns in this content type (spaced em dashes, product names like Semgrep/Opengrep, "walkthrough"), consistent with unedited text elsewhere in the same files; no new categories of finding introduced🤖 Generated with Claude Code