Folders and files
| Name | Name | Last commit date | ||
|---|---|---|---|---|
Β | Β | |||
Β | Β | |||
Β | Β | |||
Repository files navigation
### π§° Frontend Boilerplates & Reusable Component Toolbox
Welcome to my personal, high-performance frontend component library. This repository serves as an engineered, modular toolbox containing production-ready, native HTML and CSS building blocks designed to accelerate web development workflows without the overhead of heavy JavaScript frameworks.Β
### π― Core Architectural Pillars
Every layout and component in this toolbox is strictly audited and engineered to satisfy five non-negotiable architectural principles:Β
1. **High-Performance Automation:** Built using native web browser APIs and hardware-accelerated CSS properties (transform, opacity) to guarantee fluid, organic micro-interactions at 60 FPS while keeping the processing footprint at 0ms of JavaScript wherever possible.
2. **True Mobile-First Strategy:** Layouts are written from the ground up optimized for compact viewports. Media queries are restricted to progressive enhancement (min-width) to ensure rapid page delivery and lower cellular data footprints on mobile devices.
3. **Adaptive Native Dark Mode:** Engineered with a unified system of custom CSS properties (variables) that automatically respond to the user's system preferences (prefers-color-scheme). Features custom dark UX principles like soft image/brand dimming to prevent eye strain.
4. **Fluid Typography & Responsive Layouts:** Implements modern CSS functions (clamp()) to scale text and spacing organically between screen boundaries, completely eliminating abrupt layout breaks or jagged breakpoints.
5. **Strict Accessibility Standards (A11y) & Modern SEO:** Fully compliant with WCAG AA guidelines. Features comprehensive semantic markup (<main>, <nav>), logical CSS properties for cross-cultural reading directions, screen-reader utilities (.sr-only), and aria-hidden filters on purely decorative iconography.
### π Repository Structure
To eliminate cognitive load and maintain clean code isolation, components are organized by scope and contained within their own micro-directories:Β
text
frontend-boilerplates/
β
βββ π project-templates/ # Full layout starters and configuration bases
β βββ π modern-css-base/ # Core starter with reset, fluid text & theme variables
β βββ π index.html
β βββ π base-reset-theme.css
β
βββ π global-components/ # Structural components used across multiple views
β βββ π css-pure/
β βββ π visually-hidden/ # Utility snippet for accessibility
β βββ π whatsapp-floating-button/ # Isolated fixed contact trigger
β
βββ π ecommerce-components/ # High-conversion transactional UI elements
βββ π hero-banner/ # Lightweight, responsive entry section
### π How to Reuse (The Component Philosophy)
These components are designed like independent Lego blocks. To implement any boilerplate into a live project:Β
1. Open the specific template or component directory.
2. Copy the semantic HTML layout into your view.
3. Link or append the modular CSS rules into your style sheet.
The changes will propagate instantly, inheriting optimized layout performance, responsive flexibility, and standard web accessibility configurations by default.