Redesign: terminal-native mono/cream UI

[0xliam627]

Description

Implements a new design direction for endgit-web based on DESIGN.md: a terminal/manpage-inspired aesthetic built on a monospace (Geist Mono) type system, warm cream/ink palette in light mode, and a derived monochrome near-black dark mode. Chrome is mostly monochrome while semantic colors (verified/featured/pre-release/heat/status) are preserved for meaningful signals.

Key changes:

• Foundation: switched to local Geist Mono, rewrote design tokens, removed shadows/gradients, 4px radius system.
• Navigation & footer: flat mono/cream treatment, original logo and footer content preserved.
• Home page: simplified hero, removed search form, accent colors kept for hot/featured/top signals.
• Plugins listing: upgraded cards (quick-copy install, subtle purple hover glow, stronger hierarchy), grid/list toggle (desktop), accordion + pill filters, ergonomic scroll/pagination.
• Plugin detail/README: improved markdown typography, horizontal-only tables, One Dark code blocks with copy button, section tabs.
• Top Plugins: redesigned from podium into a developer-style ranked leaderboard.
• Builds & dashboard: aligned to the new card/accent system.
• Submission rules: simplified and softened into guidelines.
• Mobile responsive pass across redesigned surfaces.

Related Issue

Fixes #

Motivation and Context

The previous UI used a sky-blue/Inter sans aesthetic. This redesign aligns the marketplace with the DESIGN.md terminal-native direction, improving visual identity, developer ergonomics (copy commands, leaderboard, readable docs), and consistency across pages.

How Has This Been Tested?

• pnpm type-check passes after each change.
• pnpm prettier --write applied to all touched files.
• Manual visual review of home, plugins listing, plugin detail/README, top plugins, builds, dashboard, and rules pages, including mobile breakpoints.

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update
• Refactoring / Chore

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
endgit-web	Ready	Preview, Comment	Jun 9, 2026 5:05pm