This is a Next.js 16 starter template that combines Nextra 4 for documentation, Tailwind CSS 4 for styling, and comprehensive internationalization support. It provides a foundation for building documentation sites, blogs, and marketing landing pages with features like dark/light theme switching, responsive design, SEO optimizations, and pre-built UI components. The architecture centers around Next.js App Router with language-specific routing ([lang] segment), MDX-driven content in src/content/{lang}/, and a modular component system. Key strengths include a type-safe i18n system with compile-time checking, high-performance UI components like ScrollProgressBar (which uses requestAnimationFrame and lerp for smooth animation) and LinkPreview (which combines Radix UI hover cards with Framer Motion physics-based animations), and thoughtful separation of concerns between content, presentation, and logic. The template is actively maintained and stays current with modern web technologies.
HugoBlox Kit is a modular static site framework built on Hugo, providing a block-based page builder for academic, portfolio, documentation, and marketing websites. It uses Hugo's template system with Preact for interactive components, Tailwind CSS v4 for styling, and supports various third-party services (analytics, comments, search). The architecture is a monorepo with core modules (blox, analytics, slides, integrations) and multiple starter templates. Key entry points include the block system (blox/), layouts, shortcodes, and partials. Data flows from Markdown content and YAML configuration through Hugo's build pipeline, with client-side hydration via Preact. External dependencies include Hugo Extended, Node.js, pnpm, and various CDN-hosted libraries (Reveal.js, Mermaid, KaTeX, etc.). The framework is heavily oriented toward academic and research use cases, with features like BibTeX import, publication pages, and author profiles, but also serves general-purpose sites like SaaS landing pages and documentation.
This repository provides a comprehensive AI-assisted UI/UX design system toolkit, primarily packaged as a skill for AI coding assistants (Claude Code, Cursor, Windsurf, Copilot, etc.) and distributed via the 'ui-ux-pro-max-cli' npm package. Its core functionality includes a curated knowledge base of 79 UI styles, 192 product color palettes, 74 font pairings, 119 UX guidelines, 22 tech stacks, and 192 reasoning rules – all stored as structured CSV files. A BM25 search engine (implemented in Python) enables domain‑aware retrieval, while a design system generator aggregates search results and applies reasoning rules to output complete design system recommendations (colors, typography, style, layout patterns, motion, anti‑patterns). The gallery Next.js app provides a browsable, filterable interface for the style catalog. Architecturally, the project is a hybrid of data curation and application delivery. The canonical source of truth lives in `src/ui-ux-pro-max/`, which is synchronised to `cli/assets/` and `.claude/skills/` via a CI‑enforced sync script. It includes sub‑skills for brand management, slide/presentation generation, banner design, icon/logo generation, and UI styling (with shadcn/ui and Tailwind integration). The CLI tool installs these skills into the appropriate AI assistant configuration directories, with platform‑specific templates for 20+ assistants. Automated workflows refresh Google Fonts and Phosphor icon catalogs weekly, and a suite of Python tests validates data contracts, stack freshness, and search relevance. Despite its active maintenance and rich functionality, the codebase suffers from significant file duplication across three directory trees, hardcoded version pins for frameworks, and test brittleness tied to exact data row counts. The design system generator and search engine are well‑crafted and reusable, but the overall project is tightly coupled to its curated CSV schema and the ecosystem of AI coding assistants. It represents a mature, production‑grade toolkit for developers who want AI‑assisted design generation, but the heavy duplication and external API dependencies (Gemini, Atlas Cloud, MuAPI) introduce moderate technical drift risk.
This repository is a curated collection of design system analyses for over 70 brands, each documented in a standardized DESIGN.md file. The analyses reverse-engineer public websites to extract design tokens (colors, typography, spacing, components) and present them in a machine-readable YAML front matter format alongside human-readable prose sections. The repo serves as a reference dataset for design system research, AI-assisted UI generation, and cross-brand comparison. It is not a software application or a traditional data pipeline; rather, it is a hybrid content repository that blends design research with structured data extraction. The project is maintained by VoltAgent and includes a commercial layer for requesting new analyses. While the data is well-structured and consistent, the analyses are static snapshots that may drift from live sites, and some files contain placeholder markers or typos.
This repository hosts the landing page for ClawSweeper, a conservative maintenance bot for OpenClaw repositories. It is a single-page static site built with handcrafted HTML and CSS, deployed on Vercel. The page describes the bot's purpose, operating lanes, guardrails, and watched repositories. The codebase is minimal but exhibits high craftsmanship in its editorial dark theme, responsive design, and accessibility features. The included GitHub Actions workflow dispatches events to the actual ClawSweeper bot repository, enabling automated review triggers. This is not the bot itself; the bot lives in a separate repository (openclaw/clawsweeper). The landing page is well-maintained and serves as a polished informational site.
This repository serves as a landing page for the Letta project, directing users to the current implementation in the `letta-ai/letta-code` repository. It contains policy files (contributing, privacy, security, terms), an AI usage policy, citation metadata, and GitHub workflows to enforce contribution guidelines. The main branch holds static markdown files, while the retired Letta V1 server code is preserved in the `archive` branch. The repository does not contain runnable application code but serves as an informational hub.