Files
cv-site/doc
juanatsap 40733034ca feat: comprehensive WCAG 2.1 AA accessibility audit
- Add aria-labels to menu action buttons (PDF, Print, Contact)
- Add aria-labelledby to toggle checkboxes (desktop + mobile)
- Add -webkit-user-select prefix for Safari compatibility
- Add DynamicCacheControl middleware for HTML pages
- Add accessibility test suite (60-accessibility.test.mjs)
- Add comprehensive accessibility documentation (21-ACCESSIBILITY.md)
- Update Modern Web Techniques doc to mark audit complete
2025-12-02 10:46:53 +00:00
..

CV Project Documentation

Complete documentation for the Go + HTMX CV website project.


📚 Quick Navigation

For Developers

Getting Started

Technical Implementation

Contact Form & Security

Deployment & Operations


For Users & Customizers


📖 Documentation Overview

Core Technical Documentation

# Document Purpose Audience
1 ARCHITECTURE.md Go backend architecture, package structure, design patterns Backend developers
2 MODERN-WEB-TECHNIQUES.md HTMX/Hyperscript frontend architecture, component patterns, ADRs Frontend developers
3 API.md Complete API reference with all endpoints API consumers, integrators
4 HYPERSCRIPT-RULES.md Hyperscript coding conventions Frontend developers
5 ZOOM_IMPLEMENTATION.md Zoom feature implementation details Feature developers
12 CSS-ARCHITECTURE.md Modular CSS structure, ITCSS layers, HTMX integration Frontend developers, designers
13 TOAST-NOTIFICATIONS.md Toast notification system, PDF download feedback, user notifications Frontend developers, UX designers
14 BACKEND-HANDLERS.md Handler architecture, type safety, middleware pattern, testing strategy Backend developers
15 SEO.md SEO optimization and best practices Frontend developers
16 CMD-K-API.md CMD+K command palette API, ninja-keys integration Frontend developers
17 CONTACT-FORM.md Contact form quick start guide Backend developers
18 SECURITY-AUDIT.md Comprehensive security audit (OWASP Top 10) Security teams
19 SECURITY-IMPLEMENTATION.md Security controls implementation details Backend developers, Security

User & Operations Documentation

# Document Purpose Audience
6 USER_GUIDE.md End-user feature documentation CV users
7 CUSTOMIZATION.md Content and style customization CV customizers
8 DEPLOYMENT.md Deployment instructions and operations DevOps, site operators
9 SECURITY.md Security policies and reporting Security teams
10 PRIVACY.md Privacy policy and data handling Legal, compliance
11 PDF-EXPORT.md PDF generation architecture and configuration Backend developers

🏗️ Architecture Quick Reference

Backend: Go (Hono-inspired routing)

  • Clean package structure (internal/ pattern)
  • Template caching and rendering
  • JSON-based CV data model
  • Middleware: logging, security headers, CORS

Frontend: HTMX + Hyperscript + Vanilla CSS

  • Hypermedia-driven architecture (minimal JavaScript)
  • Server-side rendering with HTMX partial updates
  • Declarative behaviors with Hyperscript
  • Component-level skeleton loaders
  • Light/dark/auto color themes

Key Features:

  • Custom zoom control (25%-175%)
  • Bilingual support (English/Spanish)
  • Keyboard shortcuts (L/I/V/?)
  • Print-optimized CSS
  • Mobile responsive
  • Accessibility (WCAG AA compliance)

🎯 Common Tasks

"I want to..."

...understand the system architecture → Start with 1-ARCHITECTURE.md (backend) and 2-MODERN-WEB-TECHNIQUES.md (frontend)

...add a new feature → Read 2-MODERN-WEB-TECHNIQUES.md for frontend patterns, 3-API.md for backend APIs

...customize my CV content → Follow 7-CUSTOMIZATION.md for content and styling changes

...deploy to production → Use 8-DEPLOYMENT.md for step-by-step deployment instructions

...understand HTMX patterns → Check 2-MODERN-WEB-TECHNIQUES.md Section 6 (HTMX Patterns)

...write Hyperscript code → Follow conventions in 4-HYPERSCRIPT-RULES.md

...report a security issue → See 9-SECURITY.md for responsible disclosure process


📦 Archive

Historical documentation (bug fixes, testing reports, implementation notes) is stored in archive/ for reference. These documents are not actively maintained but preserved for historical context.


🔗 External Resources


📝 Documentation Standards

All documentation in this project follows these standards:

  • Markdown format with GitHub-flavored syntax
  • Clear structure with table of contents for long documents
  • Code examples with syntax highlighting
  • Up-to-date reflecting current implementation
  • Versioned via Git with meaningful commit messages

Last Updated: 2025-12-01 Documentation Status: Clean, organized, single doc/ folder Total Active Docs: 19 core documents + archive