This is a demo application showcasing ActiveAdmin functionality for Ruby on Rails. It provides an admin interface for managing AdminUser records with Devise authentication, featuring CRUD operations, a customizable dashboard, and proper error handling. The application follows standard Rails MVC architecture with ActiveAdmin as an engine/plugin, uses Importmap for JavaScript bundling, and CSS Bundling with TailwindCSS for styling. It includes comprehensive test coverage and is actively maintained with CI/CD pipelines.
Formvuelar is a Vue 3 form component library designed for backend-driven form workflows, with first-class support for Laravel-style validation responses. The source defines 19+ Fvl* components (input, textarea, select, search select, tag select, checkboxes, radio, switches, sliders, color/date pickers, file uploads, dropzone) and a root FvlForm component that coordinates submission, error display, dirty-state tracking, and upload progress. The core architecture uses provide/inject plus mixins: FvlForm creates a form context object and child controls inject it via formControl.js to read backend errors, clear errors on input, and expose loading and upload state. Submission is handled by Axios with per-form instances and interceptors; the library expects Laravel's 422 { message, errors } payload by default but can be adapted through global $formvuelar configuration.
This is a monorepo containing starter templates and final code for the official Next.js Learn courses. It includes multiple independent Next.js applications demonstrating the Pages Router, App Router, data fetching, authentication, SEO optimization, and more. The code is educational, well-structured, and follows modern Next.js patterns (server actions, streaming, suspense, etc.). It is not a production application but serves as a reference implementation for learning. The dashboard example includes a full CRUD invoice management system with PostgreSQL, NextAuth authentication, and Tailwind CSS styling. The basics examples cover static generation, dynamic routes, API routes, and TypeScript. The SEO example demonstrates performance optimization techniques like dynamic imports and lazy loading.
Lowkey is a Hugo static-site theme for personal blogs, implemented entirely as Go templates, partials, shortcodes, Tailwind CSS styling, and i18n dictionaries. It renders a single-column blog with a homepage, paginated post lists, article pages with optional table of contents and comments (Disqus/giscus), category/tag taxonomies, a 404 page, robots.txt, and a client-side dark-mode toggle. There is no executable application, API, or service; the theme is consumed by Hugo's static site generator and produces static HTML/CSS output. The architecture follows conventional Hugo theme design: `_default/baseof.html` provides the shell, `_default/list.html` and `_default/single.html` define the main page types, and `partials/` separate concerns like header, footer, metadata, and asset loading. Tailwind CSS is compiled through Hugo Pipes and PostCSS, with minification and fingerprinting enabled in production. Content flows from Markdown files and site configuration (params, menus, translations) into these templates. External services include MathJax for math rendering, Google Analytics, Disqus, and giscus for comments. The codebase is clean and idiomatic for its domain. Standout reusable pieces include the SVG icon partial, the alert and image shortcodes, active-navigation handling, and the Hugo Pipes/Tailwind asset pipeline. Weaknesses are the absence of tests and CI, no lockfile, reliance on the outdated MathJax 2.7.1 CDN, and a hardcoded `dark` class in the base template that can cause a flash of dark mode before JavaScript runs. It is a solid, maintainable theme that does what it claims, but not an exceptional engineering artifact.
This is a production-ready, multi-tenant SaaS starter kit built with Next.js (Pages Router), NextAuth.js, Prisma ORM (PostgreSQL), and Tailwind CSS. The system provides comprehensive enterprise features: email/password authentication, magic link, OAuth (Google, GitHub), SAML/SSO via BoxyHQ Jackson, directory sync (SCIM), webhooks via Svix, audit logging via Retraced, Stripe billing, API keys, and team-based role management (RBAC). The architecture follows a monolith with API routes under /pages/api, middleware for session validation, and a component-based frontend. Data flows center around team creation and management: users register (or SSO), create or join teams via invitations, then configure team-level SSO, directory sync, webhooks, billing, and API keys. The codebase demonstrates solid engineering practices with Zod validation, reusable UI components, and a clear separation of concerns, but shows signs of feature creep and some legacy patterns (e.g., Pages Router). It is well-suited for developers building a SaaS platform who need a jump-start on authentication, team management, and enterprise integrations.
This repository is a modern, minimalist portfolio template built with Astro and Tailwind CSS v4. It provides a single-page static site with sections for hero, about, projects, experience, education, and footer, all driven by a centralized configuration file (`src/config.ts`). The architecture is straightforward: Astro components render data from the config, with conditional section visibility based on data presence. The template uses TypeScript for type safety, Tabler Icons for social links, and IBM Plex Mono font. It is designed for easy customization by editing the config file, making it suitable for developers who want a quick, professional portfolio site. The codebase is clean and follows Astro best practices, but it is essentially a boilerplate template with no complex logic or reusable components beyond the template itself. It is not a production application but a static site generator template.
Notty is a full-stack, cross-platform notes application (an Apple Notes-style clone) built with a React 19 + Vite + Tailwind 4 frontend, a Hono API running on Cloudflare Workers, and per-user Durable Objects that each own a SQLite database. Clients include a web app, a Tauri 2 desktop app (with local SQLite, markdown export/import, cloud sync, deep-link auth, and a quick-note hot corner), and a mobile variant. Realtime collaboration is powered by Yjs with three persistence paths (Durable Object SQLite, browser IndexedDB, and Cloudflare R2), and authentication uses Better Auth with passkeys, Google/GitHub/Apple social login, and anonymous sessions. The backend also serves server-rendered public pages generated from TipTap JSON with URL sanitization and RSS 2.0 feeds, and integrates Supermemory for AI-powered note indexing. File storage and full version-history snapshots live in R2, with branch management (create/checkout/merge/delete), diff views, and restore-with-auto-backup. The architecture is notable for its platform adapter pattern (web/desktop/mobile adapters abstracting storage and sync) and per-user Durable Object isolation, but the codebase carries meaningful baggage: dead code from an earlier NextAuth-based iteration (src/lib/auth.ts, old NotesContext, DarkModeSwitch, search-results.tsx), no visible unit tests beyond a race-condition QA script, a non-standard FNV-1a-based lock token instead of a real HMAC, and a merge operation that is actually a replace. Optimistic update logic in the notes context is fragile and can diverge from server state under rapid tab switches. Despite these issues, the core architecture is sound and the adapter pattern is genuinely reusable.
This repository provides a minimal, opinionated starter template for building React applications with Vite. It includes a pre-configured setup with TypeScript, Tailwind CSS v4, Biome for linting and formatting, Lefthook for git hooks, Turbo for task orchestration, and Renovate for automated dependency updates. The actual application code is trivial: a single-page app shell with lazy-loaded routes for an index page and a 404 page, wrapped in React Router's BrowserRouter. The template prioritizes modern tooling and developer experience but does not implement any business logic, custom components, or complex architecture. It is intended to be cloned and used as a starting point for new React projects, rather than as a standalone application.
Hayroo is a full-stack MERN e-commerce application built as a tutorial/demo project. It enables product browsing, cart management, checkout with Braintree sandbox payment, user authentication (JWT), and an admin dashboard for managing categories, products, orders, and slider images. The frontend uses React with Context API and useReducer for state management, while the backend is an Express.js REST API with MongoDB/Mongoose. The code follows standard patterns for a teaching project but lacks tests, CI/CD, and advanced optimizations. It is a functional, unremarkable implementation suitable for learning MERN stack concepts.
This repository implements a personal link-in-bio web application (moure.dev) built with Reflex, a Python web framework that compiles to a React frontend with a FastAPI backend. The application serves as a central hub for Brais Moure's social media profiles, programming courses, newsletter subscription, and sponsor showcases. It features two main pages: an index page with social links and a courses page listing educational resources. The architecture follows a modular pattern with separate components for UI elements (buttons, icons, headers, footers), a state management class for asynchronous data fetching, and a FastAPI sub-app that exposes REST endpoints for live Twitch status, featured content from Supabase, and event schedules from ConfigCat feature flags. The frontend is rendered using Radix UI primitives and includes client-side theming, analytics tracking (Google Analytics, Facebook Pixel), and a newsletter integration via Beehiiv. The codebase is primarily educational, accompanying a 13-hour video course on web development with Python. It demonstrates how to build a full-stack application using Reflex, integrate external APIs (Twitch, Supabase, ConfigCat), manage application state, and deploy via Docker or static export. The project includes CI/CD via GitHub Actions for automated static builds. While the application is functional and well-structured for its scope, it lacks automated tests and contains some commented-out code. The generated frontend assets are tightly coupled to specific Reflex and React versions, posing potential maintenance challenges during upgrades. External dependencies on Twitch, Supabase, and ConfigCat require valid credentials via environment variables, limiting out-of-the-box reproducibility.