Repository navigation
Finish plan step 2e and clear the content pass follow-ups - #42
Merged
Merged
Conversation
Plan 2e (Sol): - Every page reads its words from MDX. The database fallbacks are gone, and the ad network pages moved to MDX word for word. - Content sync commands and placeholder preview scripts are retired. update-fields.mjs keeps titles, search text and cards. - The publisher no longer requires markdown fields, and large plans ship as Git blobs with a SHA-256 check instead of inside the GitHub deployment record. - Migration 20261010064142 makes the old columns optional and stops the tool date function reading them. The drop ships next release. Follow-ups: - BreadcrumbList structured data on every indexable page (Sol). - DNS lookup sets the AD bit, so "Authenticated" can show (Sol). - Shortcut records: names, platforms, sources, duplicates, thin records, and the old intro field removed (Luna). - Zigbee platform labels mapped to product names; launch link types normalized and submission evidence filled (Luna). - One <main> per page, no "Registry: Registry", hostnames wrap at dots, plainer tool words, whole code tokens in tables, phone tables (Opus). - Zigbee link and date labels, fair capability filters, source and checked date on shortcut pages (Opus). - The free-without-required-backlink filter only counts checked flows. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…tired script references Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1,395 matched records get Blakadder platform compatibility and provenance, from the same pinned sources. Co-Authored-By: Claude Opus 5.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.
Why
This finishes the charts and content in code plan, step 2e, and fixes the follow-ups found during the content pass. It's release 1 of 2. The migration that drops the old content columns ships alone in release 2, after this one is live, because the old server image still reads them while this release rolls out.
Plan 2e (Sol)
scripts/stack127/directory-pages/update-fields.mjsstill updates titles, search text and cards.20261010064142. It makes the old columns optional and replaces the tool date function, which read them. It is safe for both the old and new server images.Follow-ups
introfield (Luna, with fixes). GNOME, KDE Plasma and Autodesk Fusion now use their owners' own spelling.<main>per page, and no more "Registry: Registry".Checks
npm run quality(TypeScript and 79 tests), the focused Zigbee, launch, publishing, content, breadcrumb and DNS tests, andkeyboard-shortcuts:checkall pass.<main>on DNS, domain, IP ASN and TLD pages;After merge (production data)
🤖 Generated with Claude Code