Skip to content

Repository files navigation

Dev Wiki — visual reference map

Dev Wiki

See it. Understand it. Copy it.
A visual developer reference — layouts, API auth, HTTP codes, security headers, performance, and accessibility.
Live demos, practical context, and copy-ready examples built with shadcn/ui.

By Luke-official React 19 shadcn/ui Tailwind v4 MIT License

Topics · Features · Run locally · Structure · Add a topic · About


Why this exists

Most dev references are either too dense (specs and RFCs) or too shallow (blog posts that age fast). Dev Wiki sits in the middle: visual, browsable, and practical.

Each topic follows the same rhythm:

  1. Map page — scan all entries at a glance
  2. Detail page — context, tips, warnings, and copy-ready code
  3. Navigate fast — search, filters, breadcrumbs, and related entries

No theory overload. No handoff gap between design and implementation. Just see → understand → copy.


Topics

55 entries across 6 topics, grouped by category on the home page.

Design

Topic Route Entries What you get
Webpage Layouts /layouts 12 Live layout demos, when to use / avoid, real-world examples, shadcn/ui snippets

Layout map in dark mode

# Layout Best when you need…
01 Single Column Reading flow, blogs, docs, mobile-first content
02 Two Column Sidebar navigation + focused main area
03 Grid Portfolios, product cards, image galleries
04 F-Pattern Scannable landing pages (eyes move top → left)
05 Z-Pattern Marketing pages that guide toward a CTA
06 Split Screen Comparisons, dual offerings, bold choices
07 Magazine Editorial hierarchy with a hero story
08 Asymmetrical Creative, dynamic, brand-forward compositions
09 Holy Grail Classic app shell: header · sidebars · footer
10 Masonry Pinterest-style staggered media grids
11 Hero Landing Conversion-focused SaaS / product pages
12 Full-Screen Immersive storytelling with scroll-snap

Backend

Topic Route Entries What you get
API Authentication /api-auth 6 Flow diagrams, security warnings, example requests (API key → mTLS)
HTTP Status Codes /http-status 12 When to use each code, example responses (200 → 503)
Security Headers /security-headers 8 CSP, HSTS, CORS, and copy-ready header configs

Frontend

Topic Route Entries What you get
Performance /performance 9 Optimization checklist with impact levels and Core Web Vitals mapping
Accessibility /accessibility 8 Inclusive practices with practical tips and code examples

Features

Feature Description
Global search ⌘K / Ctrl+K — search all 55 entries across topics
Tag filters Filter map pages by category tag (e.g. images, 2xx success, xss)
Related entries Discover similar items at the bottom of each detail page
Breadcrumbs Always know where you are: Home → Topic → Entry
Topic navigation Header links to every section; mobile hamburger menu
Dark mode Persistent theme toggle
One-click copy Syntax-highlighted code blocks with VS Code themes

Inside each layout demo

Magazine layout with design notes and code

Every layout detail page includes:

What Why it matters
Context Best for, avoid when, real-world examples Pick the right pattern for the job
Live demo Realistic UI with shadcn/ui components Judge spacing, rhythm, and hierarchy
IDE code Syntax-highlighted TSX Read it like your editor
One-click copy Grab the snippet and paste Skip the scaffolding

Hero landing layout with syntax-highlighted code


Design system

Built with a soft pastel palette — warm backgrounds, gentle accent tints, and generous whitespace.

  • Light & dark mode with a persistent theme toggle
  • tweakcn-style CSS variables on Tailwind v4
  • shadcn/ui new-york components
  • Inter typography, rounded cards, subtle borders

The goal: feel curated, not generic.


Quick start

git clone https://github.com/Luke-official/webpage-layouts.git
cd webpage-layouts
npm install
npm run dev

Open http://localhost:5173 and explore.

Scripts

Command Description
npm run dev Start development server
npm run build Type-check + production build
npm run preview Preview production build
npm run lint Run oxlint

Built with

Layer Tech
Framework Vite + React 19 + TypeScript
Styling Tailwind CSS v4
Components shadcn/ui
Routing React Router
Code display react-syntax-highlighter

Project structure

src/
├── components/
│   ├── ui/                  # shadcn/ui primitives
│   ├── site/                # Header, footer, theme toggle
│   ├── wiki/                # Shared wiki shell (layout, search, cards, code block)
│   ├── layouts/             # Layout topic components
│   ├── api-auth/            # API auth topic components
│   ├── performance/         # Performance topic components
│   ├── http-status/         # HTTP status topic components
│   ├── security-headers/    # Security headers topic components
│   └── accessibility/       # Accessibility topic components
├── data/                    # Topic registries, entry definitions, search index
├── hooks/                   # Page title, theme sync
├── layouts/                 # 12 live layout demo components
├── pages/                   # Route pages (map + detail per topic)
└── lib/                     # Brand tokens, wiki utilities

Components outside ui/ are organized by wiki section — adding a topic means adding a folder under components/ and a data file under data/.


Adding a topic

  1. Define entries — create src/data/your-topic.ts with slug, title, tag, description, tips, and optional code
  2. Register the topic — add to src/data/wiki-topics.ts (title, path, category, entry count)
  3. Add to search — register entries in src/data/wiki-search-index.ts
  4. Create componentssrc/components/your-topic/ for previews and detail views
  5. Create pages — map page + detail page in src/pages/
  6. Add routes — register in src/App.tsx

Checklist-style topics can reuse ChecklistItemInfo from components/wiki/. Layout-style topics with live demos follow the pattern in components/layouts/.


About the author

Luke-official on GitHub luke.nexthub.io

Luke (@Luke-official) — Front-end engineer with a product mindset.

Bridging pixel-perfect UI and high-level product vision. Based in Messina, Italy. Building digital experiences that balance business value and end-user delight.

If this project saves you time, consider giving it a star — it helps others discover it too.

GitHub stars


License

MIT — free to use, remix, and share.

Made with intention · Open for everyone

About

A visual developer reference — layouts, API auth, HTTP codes, security headers, performance, and accessibility

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages