A home for the software details
The new developer project hub separates software reference material from the broader Work & Skills portfolio. Projects are grouped into web diagnostics, streaming tools and editor integrations.
- SEO-INDEX VariScripts covers diagnostic workflows, the local workbench and the distinction between toolkit heuristics and search-engine outcomes.
- PearConnect Song Requests documents the reviewed beta, the source setup path and the player-queue compatibility caveat.
- TikCord Presence explains the TikTok LIVE bridge, local Discord requirements and unofficial connector limitations.
- UnityCord Presence records the Windows Unity Editor/VCC integration and distinguishes its README license declaration from a standalone license file.
- Rank Math for Next.js identifies the independent derivative port, upstream attribution and production-adapter requirements.
Evidence and page organization
Each guide includes a problem statement, current status, features, setup steps, repository and documentation links, licensing, release history, author identity and an explicit last-reviewed date. Documentation links pin the source revision used for review. Review dates do not update automatically on deployment.
PearConnect and TikCord use screenshots supplied in their repositories. The SEO toolkit uses a capture of its hosted workbench. The Next.js port uses an actual locally launched dashboard capture with account services disconnected. UnityCord has a source-based integration diagram, explicitly not a runtime screenshot. No live account state or measured results were invented. All five images are local WebP assets with intrinsic dimensions and build-generated responsive variants.
The primary navigation now consistently exposes Work and Projects as separate destinations. Blog and Changelog remain reachable through the footer, and the original portfolio cards link directly to their project guides. Existing public routes and authored portfolio descriptions remain intact. The newer Press page, its media downloads and its release history are preserved in the combined build; Press and Projects are both reachable through the site footer.
Discovery and regression protection
The six project routes have static HTML, self-canonicals, matching crawler meta directives and Worker response policies, ordered breadcrumbs and structured source-code entities. Sitemap generation, the release audit and browser route inventory now cover the expanded site. The supplied robots.txt remains unchanged. The LLM-readable directory also links to the project references.
New regression checks cover required sections, reviewed commits, source links, local images, navigation, schema relationships and unknown project routes. Project content and screenshots do not require a live GitHub request, client-only rendering, an entrance animation or a new browser media handler.
Before publication, the combined 24-page release passed the build, release audit, Worker tests and delivery tests. Chrome checks found no failures across the 24-page inventory, with separate project reflow and direct-section navigation checks at six viewport widths. These are regression checks, not a promise of search-engine indexing or identical performance on every visitor’s device.
After deployment, all 24 canonical pages passed the live browser regression suite. The 364-request HTTP/cache matrix passed, including cached responses; HTML and HTTP crawler directives agree. The supplied robots policy remains unchanged.
Production mobile Lighthouse measured 98–100 Performance on the six new project routes, with 100 Accessibility, Best Practices and SEO and zero layout shift. The homepage’s first performance sample was 83; two unchanged-build confirmation runs were 99 and 96. All samples and the remaining image-delivery suggestions are retained in the repository regression log rather than presented as a universal 100-score guarantee.
These pages provide specific references people can choose to cite. They do not promise backlinks, domain-authority scores, rankings or indexing. No external repository descriptions, accounts or outreach messages were changed for this release.