template-library

An organized personal library of web templates, admin dashboards, design assets and UI snippets, sorted by category and technology so anything can be found in seconds.

🚧 This repository is being populated incrementally. The directory layout below describes the planned structure - new templates are added as they are collected and curated.

Purpose

Instead of hunting through old projects and ZIP files every time a new project starts, this repo keeps usable, ready-to-adapt templates in one place:

• Landing pages, marketing sites, portfolios
• Admin dashboards and back-office UIs
• Authentication flows (login, signup, reset)
• Email templates
• Raw design assets (icons, illustrations, fonts, color palettes)

Each template is kept close to its original form so it can be copied into a new project and adapted, rather than being forced into a shared build system.

Planned structure

template-library/
├── web/                # Public-facing web pages
│   ├── landing/
│   ├── portfolio/
│   ├── blog/
│   └── ecommerce/
├── dashboards/         # Admin & back-office UIs
│   ├── analytics/
│   ├── crm/
│   └── saas/
├── auth/               # Login, signup, password reset
├── email/              # Transactional email templates
├── components/         # Isolated UI components
└── assets/             # Icons, illustrations, palettes, fonts

Within each category, templates are grouped by technology - e.g. web/landing/html-tailwind/, web/landing/react/, dashboards/analytics/vue/.

Conventions

• Every template lives in its own folder with a short README.md describing:
  • What it's for (landing page, admin, email, …)
  • The stack (plain HTML, Tailwind, React, Vue, Django templates, …)
  • The license / source of the original template if it's not original work
  • A screenshot (when available)
• No secrets, no API keys, no build artifacts (node_modules/, dist/, …) committed.
• Large binary assets are kept minimal - prefer links to the original source when possible.

Contributing

Suggestions and pull requests are welcome:

• New templates (with clear licensing)
• Better categorization
• Screenshots or preview pages
• A lightweight browser / index generator

Open an issue before submitting a large PR so we can agree on where it fits in the structure.

License

No license file is attached yet. Individual templates keep their original license (noted in each template's own README.md). Please respect those licenses when reusing content from this repo.