Upgrade /yotam personal project case studies with verifiable engineering evidence

[yotamon]

What changed

This is a full credibility and consistency pass across the personal project portfolio under /yotam.

Portfolio structure

• Show all five personal projects in one canonical order
• Make Ensemblis visible instead of indexed-but-hidden
• Route commercial client work to /work
• Route project “Portfolio / All projects” navigation directly back to /yotam#work
• Align the project order with the “Next project” sequence

Case-study proof

• Add a consistent project snapshot with status, period, ownership, scope and stack
• Add project-specific architecture / workflow evidence to all five projects
• Expose StarLinker’s graph/sync/permissioned-AI architecture
• Expose WakeMyWay’s reliability boundary between the alarm kernel and adaptive runtime
• Add a traceable review pipeline for RightFlow
• Make Ensemblis explicitly transparent about what is still in development
• Show CartShift’s real lead → proposal → payment → portal → delivery operating flow
• Correct CartShift ownership to Co-founder / Lead engineer

Accessibility and implementation quality

• Restore focus after closing project media
• Focus and trap the lightbox close control while the dialog is open
• Localize the media control accessible name by using the media alt text
• Replace accent-color substring CSS selectors with explicit data-project selectors

SEO / discovery

• Add per-project dynamic Open Graph cards
• Add SoftwareApplication structured data
• Track real per-project updatedAt values
• Stop marking every project as modified on every sitemap build

Content accuracy

• Replace over-strong “defensible finding” wording with “traceable finding”
• Use more concrete, repository-backed StarLinker and WakeMyWay capability language
• Keep Ensemblis claims scoped to the product currently being built

The visual language is intentionally preserved; this pass strengthens evidence, trust, navigation, accessibility and technical credibility rather than redesigning the portfolio.

Regression coverage

• Ensure counters render meaningful values before animation/intersection
• Lock the canonical personal-project order
• Require status, ownership, three scope highlights, a concrete stack and parseable update dates for every personal project
• Keep Ensemblis explicitly marked as in development

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
cart-shift-studio	Ready	Preview	Sep 20, 2026 11:05am UTC