diff --git a/HYPERSCRIPT-RULES.md b/HYPERSCRIPT-RULES.md deleted file mode 100644 index 6d34280..0000000 --- a/HYPERSCRIPT-RULES.md +++ /dev/null @@ -1,134 +0,0 @@ -# Hyperscript Development Rules - -## MANDATORY RULES - ALWAYS FOLLOW - -### Rule 1: Code Cleanliness -**More than 3 lines of hyperscript → Move to function in file** - -- Inline hyperscript in HTML should be kept minimal (≤3 lines) -- Longer logic MUST be extracted to named functions in .\_hs files -- HTML templates should be clean and readable - -### Rule 2: File Structure - Hyperscript 0.9.12 Limitation -**Maximum 3 `def` statements TOTAL across ALL files** - -⚠️ **CRITICAL**: Hyperscript 0.9.12 has a parser limitation - more than 3 `def` statements **across ALL loaded .\_hs files** causes: -``` -Error: Expected 'end' but found 'def' -``` - -**Solution for Global Reusable Functions**: Use regular JavaScript instead -- `static/js/cv-functions.js` - Global toggle and utility functions - - toggleCVLength(), toggleIcons(), toggleTheme() - - syncPdfHover(), syncPrintHover(), highlightZoomControl() - -**Solution for Hyperscript-Specific Logic**: Keep max 3 defs -- `static/hyperscript/functions._hs` - ONLY hyperscript-specific utilities (printFriendly, initScrollBehavior, handleScroll) - -**Why JavaScript for Global Functions:** -- ✅ No artificial limits -- ✅ Better performance (native JS) -- ✅ Better debugging -- ✅ Can still be called from hyperscript using `call toggleIcons(my.checked)` - -### Rule 3: HTML Structure Cleanliness -**HTML must be as clean as possible regarding hyperscript** - -✅ **GOOD** - Clean, readable: -```html - -``` - -❌ **BAD** - Inline logic nightmare: -```html - -``` - -## File Organization - -``` -static/hyperscript/ -├── functions._hs → Core utilities (3 defs max) -├── toggles._hs → Toggle functions (3 defs max) -└── hover._hs → Hover sync functions (3 defs max) -``` - -### Load Order in templates/index.html: -```html - - - - -``` - -## Required Functions - -### Core Functions (functions._hs) -1. `printFriendly()` - Handle print-friendly view -2. `initScrollBehavior()` - Initialize scroll variables -3. `handleScroll()` - Manage scroll behavior and fixed button positioning - -### Toggle Functions (toggles._hs) -1. `toggleCVLength(isLong)` - Switch between short/long CV -2. `toggleIcons(showIcons)` - Show/hide icons -3. `toggleTheme(isClean)` - Switch between default/clean theme - -### Hover Sync Functions (hover._hs) -1. `syncPdfHover(show)` - Sync hover state across PDF buttons -2. `syncPrintHover(show)` - Sync hover state across print buttons -3. `highlightZoomControl(show)` - Highlight zoom control on hover - -## Why These Rules Exist - -### Maintainability -- Functions with descriptive names are self-documenting -- Easier to test and debug -- Changes in one place instead of scattered across templates - -### Performance -- Browser caches .\_hs files -- Reduces HTML payload size -- Cleaner separation of concerns - -### Hyperscript 0.9.12 Limitation -- Parser breaks with >3 `def` in single file -- MUST split into multiple files -- Each file: ≤3 `def` statements - -## Common Mistakes to Avoid - -❌ **DON'T**: Put all functions in one file if you have >3 defs -❌ **DON'T**: Write long inline hyperscript in HTML -❌ **DON'T**: Delete functions to work around the 3-def limit - -✅ **DO**: Split functions across multiple .\_hs files -✅ **DO**: Keep HTML clean with function calls -✅ **DO**: Maintain all required functions for clean architecture - -## Testing After Changes - -1. Check browser console for parse errors -2. Verify all functions are defined (no "X is null" errors) -3. Test all toggles work correctly -4. Hard refresh browser (Ctrl+Shift+R) to clear cache - ---- - -**Last Updated**: 2025-01-17 -**Hyperscript Version**: 0.9.12 -**Status**: MANDATORY - ALWAYS FOLLOW diff --git a/MODERN-WEB-TECHNIQUES.md b/MODERN-WEB-TECHNIQUES.md deleted file mode 100644 index 61abae7..0000000 --- a/MODERN-WEB-TECHNIQUES.md +++ /dev/null @@ -1,1621 +0,0 @@ -# Modern Web Development Techniques - JavaScript Reduction Guide - -**Project:** CV Interactive Website -**Objective:** Achieve "almost 0 JavaScript" while maintaining modern features -**Philosophy:** Progressive enhancement, native browser APIs, and hypermedia-driven architecture - ---- - -## 📊 Progress Metrics - -| Phase | Lines of JS | Reduction | Percentage | -|-------|-------------|-----------|------------| -| **Original (Baseline)** | 954 | - | 100% | -| **Phase 4A Complete** | 669 | -285 | -29.9% | -| **Phase 5 Complete** | 326 | -343 | -51.3% | -| **Phase 6 Complete** | **239** | **-87** | **-26.7%** | -| **Cumulative Progress** | **239** | **-715** | **-74.9%** | - ---- - -## 🎯 Core Philosophy - -**Modern web development doesn't require mountains of JavaScript.** By leveraging: -- Native HTML5 APIs (``, `
`) -- CSS3 animations and transitions -- HTMX hypermedia patterns -- Hyperscript declarative behaviors -- Progressive enhancement principles - -We achieve rich, interactive experiences with minimal JavaScript footprint. - -**Result:** 74.9% JavaScript reduction (954 → 239 lines) with ALL features preserved + organized hyperscript functions. - ---- - -## 🏗️ Techniques Implemented (8 Major Optimizations) - -### 1. Native `` Element - Modal Management - -**Problem:** Custom modals required 47 lines of JavaScript for open/close logic, backdrop handling, and focus management. - -**Solution:** Native HTML5 `` element with built-in browser features. - -#### Before (JavaScript-heavy approach): -```html - -
-
- - -
-
-``` - -```javascript -// 47 lines of modal management JavaScript -window.openInfoModal = function() { - const modal = document.getElementById('info-modal'); - modal.style.display = 'flex'; - document.body.style.overflow = 'hidden'; - modal.querySelector('.info-modal-close').focus(); -}; - -window.closeInfoModal = function() { - const modal = document.getElementById('info-modal'); - modal.style.display = 'none'; - document.body.style.overflow = ''; -}; - -window.closeInfoModalOnBackdrop = function(event) { - if (event.target === event.currentTarget) { - closeInfoModal(); - } -}; -``` - -#### After (Native HTML5 approach): -```html - - -
- - -
- - - - -``` - -```css -/* Native ::backdrop pseudo-element */ -.info-modal::backdrop { - background: rgba(0, 0, 0, 0.7); - backdrop-filter: blur(10px); -} - -/* Opening animation */ -.info-modal[open] { - animation: modalFadeIn 0.3s ease; -} - -@keyframes modalFadeIn { - from { - opacity: 0; - transform: scale(0.9) translateY(20px); - } - to { - opacity: 1; - transform: scale(1) translateY(0); - } -} -``` - -**Benefits:** -- ✅ **47 lines of JS eliminated** (100% reduction) -- ✅ Built-in ESC key handling (accessibility) -- ✅ Native focus trapping (accessibility) -- ✅ Automatic body scroll prevention -- ✅ Native backdrop with blur effects via CSS -- ✅ Better semantic HTML -- ✅ Works without JavaScript (graceful degradation) - -**Browser Support:** All modern browsers (95%+ global coverage) - ---- - -### 2. CSS Animations - Hardware-Accelerated Lifecycle Management - -**Problem:** JavaScript `setTimeout()` for auto-hiding toast notifications blocks the event loop and isn't hardware-accelerated. - -**Solution:** CSS `@keyframes` animation with complete lifecycle management. - -#### Before (JavaScript timer): -```javascript -// JavaScript-controlled lifecycle -window.showError = function(message) { - const errorToast = document.getElementById('error-toast'); - const errorMessage = document.getElementById('error-message'); - - errorMessage.textContent = message; - errorToast.style.display = 'flex'; - - // Auto-hide after 5 seconds - setTimeout(() => { - errorToast.style.display = 'none'; - }, 5000); -}; -``` - -#### After (CSS-driven animation): -```javascript -// Minimal JS - just add class, CSS handles lifecycle -window.showError = function(message) { - const errorToast = document.getElementById('error-toast'); - const errorMessage = document.getElementById('error-message'); - - errorMessage.textContent = message; - errorToast.classList.remove('show'); // Reset animation - - void errorToast.offsetWidth; // Trigger reflow - - errorToast.classList.add('show'); // CSS animation handles rest -}; -``` - -```css -/* CSS handles entire lifecycle: slide in → stay → fade out */ -.error-toast.show { - display: flex; - animation: toastLifecycle 5.5s ease-out forwards; -} - -@keyframes toastLifecycle { - 0% { - transform: translateX(120%); - opacity: 0; - } - 5.5% { /* 0.3s slide in */ - transform: translateX(0); - opacity: 1; - } - 90.9% { /* 5s visible */ - transform: translateX(0); - opacity: 1; - } - 100% { /* 0.5s fade out */ - transform: translateX(120%); - opacity: 0; - } -} -``` - -**Benefits:** -- ✅ **Hardware-accelerated** (GPU-powered, 60fps) -- ✅ **Non-blocking** (doesn't occupy event loop) -- ✅ **Smoother animations** (CSS transitions are optimized) -- ✅ **Automatic cleanup** (animation ends naturally) -- ✅ **Better performance** (no JS timer overhead) - ---- - -### 3. Native Anchor Links - Smooth Scrolling Without JavaScript - -**Problem:** Back-to-top button required 19 lines of JavaScript for scroll logic. - -**Solution:** Native `` with CSS `scroll-behavior: smooth`. - -#### Before (JavaScript scroll): -```html - -``` - -```javascript -// 19 lines of scroll logic -const backToTopBtn = document.getElementById('back-to-top'); - -backToTopBtn.addEventListener('click', function() { - window.scrollTo({ - top: 0, - behavior: 'smooth' - }); -}); - -// Show/hide logic -window.addEventListener('scroll', function() { - const currentScroll = window.pageYOffset; - backToTopBtn.style.display = currentScroll > 300 ? 'flex' : 'none'; -}); -``` - -#### After (Native anchor link): -```html - - -
- - - - - - - -``` - -```css -/* Global smooth scroll behavior */ -html { - scroll-behavior: smooth; - scroll-padding-top: 70px; /* Account for fixed header */ -} -``` - -```javascript -// Only show/hide logic remains (much simpler) -window.addEventListener('scroll', function() { - const currentScroll = window.pageYOffset; - backToTopBtn.style.display = currentScroll > 300 ? 'flex' : 'none'; -}); -``` - -**Benefits:** -- ✅ **19 lines eliminated** (click handler removed) -- ✅ **Zero JavaScript execution** on click -- ✅ **Works without JavaScript** (jumps to top instantly) -- ✅ **Better accessibility** (native link semantics) -- ✅ **SEO-friendly** (proper anchor structure) -- ✅ **Automatic header offset** with `scroll-padding-top` - ---- - -### 4. HTMX Scroll Preservation - Seamless Content Swaps - -**Problem:** HTMX content swaps caused page to jump to top, disrupting UX. - -**Solution:** HTMX `show:none` modifier preserves scroll position during swaps. - -#### Before (Page jumping on swap): -```html - -``` - -**User Experience:** Page jumps to top on every toggle click, losing context. - -#### After (Scroll-preserving swap): -```html - -``` - -**User Experience:** Changes apply instantly at current scroll position - feels like a SPA. - -**Benefits:** -- ✅ **Instant, smooth updates** (no page jumping) -- ✅ **Preserves user context** (scroll position maintained) -- ✅ **SPA-like feel** with server-side rendering -- ✅ **Better UX** (changes feel natural, not disruptive) -- ✅ **No additional JavaScript** (pure HTMX modifier) - -**Applied to:** All 6 toggle controls (Length, Logos, Theme - desktop & mobile) - ---- - -### 5. Native `
` Element - Accordion Behavior - -**Problem:** Custom accordion implementations require JavaScript for expand/collapse logic. - -**Solution:** Native HTML5 `
` and `` elements. - -#### Implementation: -```html - -
- -

Work Experience

- -
- -
-
-``` - -```css -/* Smooth opening animation */ -details[open] { - animation: detailsOpen 0.3s ease; -} - -@keyframes detailsOpen { - from { - opacity: 0; - transform: translateY(-10px); - } - to { - opacity: 1; - transform: translateY(0); - } -} - -/* Custom marker styling */ -summary::marker { - content: '▶ '; - font-size: 0.8em; -} - -details[open] summary::marker { - content: '▼ '; -} -``` - -**Benefits:** -- ✅ **Zero JavaScript** for basic accordion -- ✅ **Native keyboard support** (Enter/Space to toggle) -- ✅ **Semantic HTML** (proper document structure) -- ✅ **Built-in accessibility** (ARIA roles automatic) -- ✅ **Progressive enhancement** (works everywhere) - -**Utility Functions Added:** -```javascript -// Optional: Global expand/collapse for power users -window.expandAllSections = function(event) { - event.preventDefault(); - document.querySelectorAll('details').forEach(d => d.setAttribute('open', '')); -}; - -window.collapseAllSections = function(event) { - event.preventDefault(); - document.querySelectorAll('details').forEach(d => d.removeAttribute('open')); -}; -``` - ---- - -### 6. Progressive Menu System - CSS-First Approach - -**Problem:** Complex menu hover logic with 82 lines of JavaScript for state management. - -**Solution:** CSS-driven hover states with minimal JavaScript bridging. - -#### Before (JavaScript-heavy): -```javascript -// 82 lines of complex hover management -function toggleMenu() { /* ... */ } -function toggleSubmenu() { /* ... */ } -function initClickOutsideHandler() { /* ... */ } -function handleMenuHover() { /* ... */ } -function handleSubmenuPosition() { /* ... */ } -``` - -#### After (CSS-first with minimal JS): -```javascript -// 28 lines - JS only bridges hamburger to menu -function initMenuSystem() { - const hamburgerBtn = document.querySelector('.hamburger-btn'); - const menu = document.getElementById('navigation-menu'); - - if (!hamburgerBtn || !menu) return; - - // Show menu on hamburger hover - CSS handles the rest - hamburgerBtn.addEventListener('mouseenter', () => menu.classList.add('menu-hover')); - - hamburgerBtn.addEventListener('mouseleave', () => { - setTimeout(() => { - if (!menu.matches(':hover')) menu.classList.remove('menu-hover'); - }, 100); - }); - - menu.addEventListener('mouseleave', () => menu.classList.remove('menu-hover')); - - // Position submenu dynamically (needed for fixed positioning) - const submenuTrigger = document.querySelector('.menu-item-submenu'); - const submenuContent = document.querySelector('.submenu-content'); - if (submenuTrigger && submenuContent) { - submenuTrigger.addEventListener('mouseenter', function() { - submenuContent.style.top = `${this.getBoundingClientRect().top}px`; - }); - } -} -``` - -```css -/* CSS handles most hover logic */ -.navigation-menu.menu-hover { - transform: translateX(0); - visibility: visible; -} - -.menu-item:hover .submenu-content { - display: block; -} - -/* Smooth transitions */ -.navigation-menu { - transition: transform 0.3s ease, visibility 0.3s; -} -``` - -**Benefits:** -- ✅ **63 lines eliminated** (73% reduction) -- ✅ **CSS-driven interactions** (hardware-accelerated) -- ✅ **Modern ES6+ patterns** (arrow functions, optional chaining) -- ✅ **Simplified state management** (mostly handled by CSS) -- ✅ **Better performance** (fewer event listeners) - -**Modern JavaScript Patterns Used:** -- Arrow functions: `() => menu.classList.add('menu-hover')` -- Optional chaining: `menu?.classList.remove('menu-hover')` -- Ternary operators: `display: currentScroll > 300 ? 'flex' : 'none'` -- Template literals: `` `${this.getBoundingClientRect().top}px` `` - ---- - -## 🎨 CSS Techniques Showcase - -### Native Pseudo-Elements - -```css -/* ::backdrop for modal overlays */ -dialog::backdrop { - background: rgba(0, 0, 0, 0.7); - backdrop-filter: blur(10px); -} - -/* ::marker for custom list styling */ -summary::marker { - content: '▶ '; -} - -details[open] summary::marker { - content: '▼ '; -} -``` - -### Hardware-Accelerated Properties - -```css -/* GPU-accelerated transforms */ -.element { - transform: translateX(100%); - /* Better than: left: 100% */ -} - -/* Opacity animations (GPU-powered) */ -.fade { - opacity: 0; - transition: opacity 0.3s; -} - -/* Avoid animating these (CPU-heavy): - - width/height - - top/left - - margin/padding -*/ -``` - -### Scroll Behavior - -```css -/* Smooth scrolling */ -html { - scroll-behavior: smooth; -} - -/* Account for fixed headers */ -html { - scroll-padding-top: 70px; -} - -/* Snap points for carousels */ -.carousel { - scroll-snap-type: x mandatory; -} - -.carousel-item { - scroll-snap-align: start; -} -``` - ---- - -## 🔄 HTMX Patterns - -### Content Swapping - -```html - - - - - - - - -
New Content
-``` - -### Loading States - -```html - - -
Loading...
-``` - -```css -/* HTMX adds .htmx-request class automatically */ -.htmx-indicator { - display: none; -} - -.htmx-request .htmx-indicator { - display: inline-block; -} -``` - -### Error Handling - -```javascript -// Global HTMX error handlers -document.body.addEventListener('htmx:responseError', function(evt) { - console.error('HTMX Response Error:', evt.detail); - window.showError('Failed to load content. Please try again.'); -}); - -document.body.addEventListener('htmx:sendError', function(evt) { - console.error('HTMX Send Error:', evt.detail); - window.showError('Connection error. Please check your internet connection.'); -}); -``` - ---- - -## 📈 Performance Benefits - -### Metrics Comparison - -| Metric | Before | After | Improvement | -|--------|--------|-------|-------------| -| JavaScript Bundle Size | ~35KB | ~25KB | -28.5% | -| Parse/Compile Time | ~45ms | ~32ms | -28.9% | -| Event Listeners | 23 | 14 | -39.1% | -| Memory Usage (JS Heap) | ~2.1MB | ~1.7MB | -19.0% | -| Lighthouse Performance | 94 | 97 | +3 points | - -### Why This Matters - -1. **Faster Page Loads:** Less JavaScript = faster parse/compile time -2. **Better Mobile Performance:** Older devices benefit from reduced JS execution -3. **Lower Memory Usage:** Fewer event listeners = lower memory footprint -4. **Improved Battery Life:** Less CPU/GPU usage on mobile devices -5. **Better SEO:** Faster page loads improve search rankings -6. **Progressive Enhancement:** Core features work without JavaScript - ---- - -## 🌐 Browser Compatibility - -All techniques use widely-supported web standards: - -| Feature | Chrome | Firefox | Safari | Edge | Support | -|---------|--------|---------|--------|------|---------| -| `` | 37+ | 98+ | 15.4+ | 79+ | 95%+ | -| `
` | 12+ | 49+ | 6+ | 79+ | 98%+ | -| CSS `@keyframes` | 43+ | 16+ | 9+ | 12+ | 99%+ | -| `scroll-behavior` | 61+ | 36+ | 15.4+ | 79+ | 94%+ | -| `::backdrop` | 32+ | 98+ | 15.4+ | 79+ | 95%+ | -| HTMX | All modern browsers | All modern browsers | All modern browsers | All modern browsers | 99%+ | - -**Fallback Strategy:** All features degrade gracefully. Without JavaScript: -- Modals still open (native `` or fallback to visible) -- Accordions work (native `
`) -- Scroll to top jumps instantly (native anchor) -- Forms submit normally (HTMX degrades to standard forms) - ---- - -## 🚀 Phase 5: Hyperscript Integration (COMPLETED) - -### What is Hyperscript? - -**Hyperscript** is a declarative, event-driven language that lives directly in HTML attributes. It allows you to write complex interactions inline without separate JavaScript files, making code more maintainable and easier to understand. - -**Philosophy:** "JavaScript's friendly cousin that lives in your markup" - -### 7. Hyperscript - Declarative Event Handling - -**Problem:** Zoom control required 343 lines of imperative JavaScript for state management, event handling, and DOM manipulation. - -**Solution:** Hyperscript attributes directly in HTML elements for declarative behavior. - -#### Before (Imperative JavaScript): -```javascript -// 343 lines of imperative JavaScript -function initZoomControl() { - const slider = document.getElementById('zoom-slider'); - const resetBtn = document.getElementById('zoom-reset'); - - slider.addEventListener('input', function(e) { - const zoomValue = parseInt(e.target.value, 10); - updateZoomDisplay(zoomValue); - applyZoom(zoomValue, true); - }); - - resetBtn.addEventListener('click', function() { - slider.value = 100; - applyZoom(100, true); - slider.focus(); - }); - - // ... 300+ more lines for keyboard shortcuts, dragging, etc. -} - -function applyZoom(zoomValue, saveToStorage) { - // ... 50 lines of zoom logic -} - -function updateZoomDisplay(zoomValue) { - // ... 20 lines of display updates -} - -// ... many more functions -``` - -#### After (Declarative Hyperscript): -```html - - - - - - - - - - -
- -
-``` - -**Benefits:** -- ✅ **343 lines eliminated** (51.3% reduction from Phase 4A) -- ✅ **Declarative syntax** - behavior lives with markup -- ✅ **No separation** - HTML and behavior colocated -- ✅ **Natural language** - `put`, `set`, `send`, `if/else` -- ✅ **Event handling** - `on click`, `on input`, `on keydown` -- ✅ **DOM manipulation** - `set my *property`, `add/remove class` -- ✅ **LocalStorage** - `set/get localStorage.item` -- ✅ **Conditionals** - `if/else/end` blocks -- ✅ **Event targeting** - `from document` for global listeners -- ✅ **Event filtering** - `on keydown[ctrlKey]` for modifiers - -**Hyperscript Language Features:** - -```hyperscript --- DOM Manipulation -put 'text' into #element -- Set textContent -set #element's *property to value -- Set style property -set my @attribute to value -- Set HTML attribute -add .classname to #element -- Add CSS class -remove .classname from #element -- Remove CSS class - --- Event Handling -on click -- Click event -on input -- Input event -on keydown[ctrlKey] from document -- Filtered global event -halt the event -- preventDefault() - --- Control Flow -if condition - -- statements -else - -- statements -end - --- Variables -set myVar to value -- Set variable -set myVar to my value as a Number -- Type conversion - --- LocalStorage -set localStorage.key to value -- Save -get localStorage.key -- Retrieve - --- Sending Events -send input to #element -- Trigger event on element -send focus to #element -- Focus element -``` - -**Browser Support:** All modern browsers (99%+ coverage) - ---- - -## 📊 Phase 5 Results - -### JavaScript Reduction Achieved: - -| Metric | Phase 4A | Phase 5 | Improvement | -|--------|----------|---------|-------------| -| Total Lines | 669 | **326** | **-343 (-51.3%)** | -| Zoom Control | 343 lines JS | ~70 lines hyperscript | **-273 (-79.6%)** | -| Event Listeners | 14 | **8** | **-6 (-42.9%)** | -| Separate Functions | 9 zoom functions | **0** | **-100%** | - -### Cumulative Progress: - -| Phase | Lines | Reduction | % from Baseline | -|-------|-------|-----------|-----------------| -| **Baseline** | 954 | - | - | -| **Phase 4A** | 669 | -285 | -29.9% | -| **Phase 5** | 326 | -343 | -65.8% | -| **Phase 6** | **239** | **-87** | **-74.9%** | - ---- - -## 🚀 Phase 6: Scroll & Print Optimization (COMPLETED) - -### 8. Hyperscript Functions Organization - -**Problem:** While Phase 5 successfully converted zoom control to hyperscript, all behavior was inline in HTML attributes, creating long, hard-to-maintain code blocks in templates. - -**Solution:** Extract hyperscript logic to external `functions._hs` file for clean, reusable, maintainable code. - -#### Scroll Behavior Conversion - -**Before (59 lines of JavaScript):** -```javascript -function initScrollBehavior() { - let lastScrollTop = 0; - let scrollThreshold = 100; - - window.addEventListener('scroll', function() { - const actionBar = document.querySelector('.action-bar'); - const navMenu = document.querySelector('.navigation-menu'); - const backToTopBtn = document.getElementById('back-to-top'); - const currentScroll = window.pageYOffset; - const isMenuOpen = navMenu.classList.contains('menu-open'); - - // Check if at bottom of page - const scrollHeight = document.documentElement.scrollHeight; - const clientHeight = document.documentElement.clientHeight; - const isAtBottom = (scrollHeight - currentScroll - clientHeight) < 50; - - // Hide/show header based on scroll direction - if (currentScroll > scrollThreshold) { - if (currentScroll > lastScrollTop && !keepHeaderVisible) { - actionBar.classList.add('header-hidden'); - if (isMenuOpen) navMenu.classList.add('header-hidden'); - } else { - actionBar.classList.remove('header-hidden'); - if (isMenuOpen) navMenu.classList.remove('header-hidden'); - } - } else { - actionBar.classList.remove('header-hidden'); - if (isMenuOpen) navMenu.classList.remove('header-hidden'); - } - - // Show/hide back to top button - backToTopBtn.style.display = currentScroll > 300 ? 'flex' : 'none'; - backToTopBtn?.classList.toggle('at-bottom', isAtBottom); - - lastScrollTop = currentScroll; - }); -} -``` - -**After (Clean HTML + External Function):** -```html - - -``` - -```hyperscript --- functions._hs - Organized external file -def initScrollBehavior() - set :lastScroll to 0 - set :scrollThreshold to 100 - set :keepHeaderVisible to false -end - -def handleScroll() - set currentScroll to window.pageYOffset - set isMenuOpen to .navigation-menu.classList.contains('menu-open') - - -- Calculate if at bottom (within 50px) - set scrollHeight to document.documentElement.scrollHeight - set clientHeight to document.documentElement.clientHeight - set isAtBottom to (scrollHeight - currentScroll - clientHeight) < 50 - - -- Header visibility based on scroll direction - if currentScroll > :scrollThreshold - if currentScroll > :lastScroll and not :keepHeaderVisible - add .header-hidden to .action-bar - if isMenuOpen then add .header-hidden to .navigation-menu end - else - remove .header-hidden from .action-bar - if isMenuOpen then remove .header-hidden from .navigation-menu end - end - else - remove .header-hidden from .action-bar - if isMenuOpen then remove .header-hidden from .navigation-menu end - end - - -- Back to top button visibility - if currentScroll > 300 - set #back-to-top's *display to 'flex' - else - set #back-to-top's *display to 'none' - end - - -- At-bottom positioning for fixed buttons - if isAtBottom - add .at-bottom to #back-to-top - add .at-bottom to #info-button - else - remove .at-bottom from #back-to-top - remove .at-bottom from #info-button - end - - set :lastScroll to currentScroll -end -``` - ---- - -#### Print Function Conversion - -**Before (44 lines of JavaScript - BROKEN!):** -```javascript -window.printFriendly = function() { - const container = document.querySelector('.cv-container'); - const paper = document.querySelector('.cv-paper'); - const wasClean = container.classList.contains('theme-clean'); - const wasLong = paper.classList.contains('cv-long'); - const currentZoom = localStorage.getItem('cv-zoom') || '100'; - - // Apply clean theme for print - if (!wasClean) container.classList.add('theme-clean'); - paper.classList.remove('cv-long'); - paper.classList.add('cv-short'); - - setTimeout(() => { - window.print(); - - setTimeout(() => { - if (!wasClean) container.classList.remove('theme-clean'); - if (wasLong) { - paper.classList.remove('cv-short'); - paper.classList.add('cv-long'); - } - // BUG: This function was removed in Phase 5! - if (paper && currentZoom !== '100') { - applyZoom(parseInt(currentZoom, 10), false); // ❌ ERROR! - } - }, 100); - }, 50); -}; -``` - -**After (Clean HTML + Fixed Function):** -```html - - - - - -``` - -```hyperscript --- functions._hs - Organized and FIXED -def printFriendly() - -- Store current state - set wasClean to .cv-container.classList.contains('theme-clean') - set wasLong to .cv-paper.classList.contains('cv-long') - set currentZoom to localStorage.getItem('cv-zoom') or '100' - - -- Apply print-friendly settings - if not wasClean then add .theme-clean to .cv-container end - remove .cv-long from .cv-paper - add .cv-short to .cv-paper - set #zoom-wrapper's *zoom to 1 - - -- Print and restore - wait 50ms - call window.print() - wait 100ms - - -- Restore original state - if not wasClean then remove .theme-clean from .cv-container end - if wasLong - remove .cv-short from .cv-paper - add .cv-long to .cv-paper - end - - -- ✅ FIX: Trigger zoom slider to restore zoom properly - if currentZoom !== '100' - set #zoom-slider's value to currentZoom - send input to #zoom-slider - end -end -``` - ---- - -### Hyperscript Organization Benefits: - -**File Structure:** -``` -/static/hyperscript/ -└── functions._hs (110 lines) - ├── printFriendly() - Print with state management - ├── initScrollBehavior() - Initialize scroll state - └── handleScroll() - Handle scroll events -``` - -**Loading Order (Critical):** -```html - - - - - -``` - -**Benefits:** -- ✅ **Clean HTML** - No more 30+ line hyperscript blocks in templates -- ✅ **DRY Principle** - `printFriendly()` called from 2 places without duplication -- ✅ **Maintainable** - All logic in one organized file -- ✅ **Readable** - Clear function names describe behavior -- ✅ **Reusable** - Functions available globally across all templates -- ✅ **Documented** - Comments explain each function's purpose -- ✅ **Bug Fixed** - Print function now properly restores zoom - -**Organization Comparison:** - -| Aspect | Before Phase 6 | After Phase 6 | -|--------|----------------|---------------| -| action-buttons.html | 34 lines inline | 1 line call | -| hamburger-menu.html | 27 lines inline | 1 line call | -| index.html body | 54 lines inline | 2 lines calls | -| **Total inline** | **115 lines** | **4 lines** | -| **External file** | 0 | 110 lines (organized) | -| **Maintainability** | Hard | Easy | -| **Reusability** | Copy/paste | Call function | - ---- - -## 📊 Phase 6 Results - -### JavaScript Reduction Achieved: - -| Metric | Phase 5 | Phase 6 | Improvement | -|--------|---------|---------|-------------| -| Total Lines | 326 | **239** | **-87 (-26.7%)** | -| Scroll Behavior | 59 lines JS | Hyperscript functions | **-59 (-100%)** | -| Print Function | 44 lines JS (broken) | Hyperscript function (fixed) | **-44 (-100%)** | -| Inline Hyperscript | N/A | 115 lines → 4 lines | **-111 (-96.5%)** | - -### Final Cumulative Progress: - -| Phase | Lines | Reduction | % from Baseline | -|-------|-------|-----------|-----------------| -| **Baseline** | 954 | - | - | -| **Phase 4A** | 669 | -285 | -29.9% | -| **Phase 5** | 326 | -343 | -65.8% | -| **Phase 6** | **239** | **-87** | **-74.9%** | - -**Total Reduction: 715 lines eliminated (74.9%)** - ---- - -## 💡 Key Takeaways - -### What We Learned - -1. **Native APIs First:** Always check if there's a native HTML/CSS solution before reaching for JavaScript -2. **CSS is Powerful:** Animations, transitions, pseudo-elements can replace most UI logic -3. **HTMX Patterns:** Hypermedia-driven architecture reduces need for client-side state -4. **Hyperscript Power:** Declarative inline behaviors can replace hundreds of lines of imperative JS -5. **Progressive Enhancement:** Build from HTML up, layer JavaScript as enhancement -6. **Colocation Benefits:** Keep behavior with markup for better maintainability -7. **Modern JavaScript:** When JS is needed, use ES6+ for cleaner, more maintainable code - -### Best Practices - -✅ **DO:** -- Use native HTML5 elements (``, `
`, etc.) -- Leverage CSS for animations and transitions -- Apply HTMX modifiers for better UX (`show:none`) -- Use hyperscript for complex inline behaviors -- Colocate behavior with markup when it makes sense -- Write declarative code when possible -- Test without JavaScript first - -❌ **DON'T:** -- Rebuild native browser features in JavaScript -- Use JavaScript for animations (use CSS) -- Create custom components when native exists -- Separate behavior unnecessarily (consider colocation) -- Sacrifice accessibility for custom solutions -- Assume JavaScript is always available - ---- - -## 🔗 Resources & References - -### Documentation -- [MDN: `` Element](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/dialog) -- [MDN: `
` Element](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/details) -- [MDN: CSS Animations](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Animations) -- [HTMX Documentation](https://htmx.org/docs/) -- [Hyperscript Documentation](https://hyperscript.org/) -- [Hyperscript Examples](https://hyperscript.org/examples/) -- [Web.dev: Progressive Enhancement](https://web.dev/progressive-enhancement/) - -### Tools -- [Can I Use](https://caniuse.com/) - Browser compatibility checker -- [Lighthouse](https://developers.google.com/web/tools/lighthouse) - Performance auditing -- [WebPageTest](https://www.webpagetest.org/) - Real-world performance testing - ---- - -## 📝 Version History - -| Version | Date | Changes | Lines Reduced | -|---------|------|---------|---------------| -| **Baseline** | Pre-Phase 4A | Original JavaScript | 954 lines | -| **v1.0** | Phase 4A-1 | Native `` modals | -47 lines | -| **v1.1** | Phase 4A-2 | Menu system simplification | -63 lines | -| **v1.2** | Phase 4A-3 | CSS toast animations | -2 lines | -| **v1.3** | Phase 4A-4 | Native anchor links | -19 lines | -| **v1.4** | Phase 4A Fix | HTMX scroll preservation | 0 lines (UX fix) | -| **v1.4** | Milestone | Phase 4A Complete | **-285 lines (-29.9%)** | -| **v2.0** | Phase 5 | Hyperscript zoom control | -343 lines | -| **v2.1** | Phase 6 | Scroll & print + organization | -87 lines | -| **Current** | v2.1 | Phase 6 Complete | **-715 lines (-74.9%)** | - ---- - -## 🏆 Achievements - -### Phase 4A Achievements: -- ✅ **285 lines of JavaScript eliminated** (29.9% reduction) -- ✅ **100% modal JavaScript removed** (native ``) -- ✅ **73% menu JavaScript removed** (CSS-first approach) -- ✅ **HTMX scroll preservation** (major UX improvement) - -### Phase 5 Achievements: -- ✅ **343 additional lines eliminated** (51.3% from Phase 4A) -- ✅ **100% zoom control JavaScript removed** (hyperscript) -- ✅ **9 separate functions eliminated** (colocated with markup) -- ✅ **Draggable behavior** declaratively implemented -- ✅ **Keyboard shortcuts** handled inline - -### Phase 6 Achievements: -- ✅ **87 additional lines eliminated** (26.7% from Phase 5) -- ✅ **100% scroll behavior JavaScript removed** (hyperscript) -- ✅ **100% print function JavaScript removed** (hyperscript, fixed bug) -- ✅ **Hyperscript organized** (115 inline lines → 4 function calls) -- ✅ **External functions file** (110 lines in organized `functions._hs`) -- ✅ **DRY principle achieved** (reusable functions across templates) - -### Cumulative Achievements: -- ✅ **715 lines of JavaScript eliminated total** (74.9% reduction) -- ✅ **All modern features preserved** (no functionality loss) -- ✅ **Improved maintainability** (organized external functions) -- ✅ **Better performance** (hardware acceleration, reduced event loop blocking) -- ✅ **Enhanced accessibility** (native browser features, proper semantics) -- ✅ **Smaller bundle size** (~35KB → ~15KB JavaScript) -- ✅ **Clean HTML templates** (no long inline hyperscript blocks) -- ✅ **Professional code organization** (separated concerns) - ---- - -## 🚀 Phase 7-8: Smooth Toggle Animations - Pure Client-Side Pattern (COMPLETED) - -### 9. HTMX `hx-swap="none"` + Inline Hyperscript - Client-First Toggles - -**Problem:** HTMX out-of-band swaps with `outerHTML` completely replaced toggle elements, breaking CSS transitions and causing: -- ❌ "Digital" instant snap instead of "analogical" smooth slide -- ❌ DOM element destruction mid-animation -- ❌ `TypeError: Cannot read properties of null (reading 'insertBefore')` on double-click -- ❌ Conflict between server templates and client-side state - -**Root Cause:** Two incompatible systems fighting each other: -1. **Server templates** returned HTML with `hx-swap="outerHTML"` + `hx-swap-oob="true"` -2. **Client toggles** had inline hyperscript for state management -3. **Result:** HTMX tried to swap destroyed elements, causing null reference errors - -**Solution:** Use `hx-swap="none"` for pure client-side visual updates, with server only saving cookies in background. - -#### Phase 7 Attempt (Failed - Had Bugs): -```html - - - _="on change call toggleLength(...)"> -``` - -```hyperscript --- ❌ This syntax didn't work in hyperscript -def toggleLength(checked, mobileId, desktopId) - set element(mobileId).checked to true -- ❌ No element() function! -end -``` - -**Errors:** -- `Expected 'to' but found '<'` - Hyperscript syntax error -- `htmx:swapError` - Null reference on second toggle click -- Animations only worked on desktop, not mobile menu - -#### Phase 8 Final (Working - Bug-Free): -```html - - -``` - -```html - - -``` - -```html - - - -``` - -```css -/* CSS handles smooth animation - element NEVER destroyed */ -.icon-toggle-slider::before { - transition: transform 0.3s ease; /* GPU-accelerated */ -} - -.icon-toggle input:checked + .icon-toggle-slider::before { - transform: translateX(43px); /* Smooth 300ms slide */ -} -``` - -**Benefits:** -- ✅ **Smooth animations** - CSS transitions never interrupted (element stays in DOM) -- ✅ **Analogical feel** - 300ms smooth slide, not instant snap -- ✅ **Desktop/mobile sync** - Direct ID manipulation (`set #otherToggle's checked to true`) -- ✅ **No server HTML** - Templates return empty response, just save cookie -- ✅ **No swap conflicts** - `hx-swap="none"` prevents all DOM replacement -- ✅ **Bug-free** - No null reference errors on double-click -- ✅ **State persistence** - localStorage + server cookie sync -- ✅ **No scroll jump** - Zero DOM disruption - -**Architecture Pattern:** -1. **User clicks toggle** → Checkbox changes (instant native response) -2. **CSS transition fires** → Smooth 300ms slide animation (GPU, uninterrupted) -3. **Hyperscript inline code runs** → Updates classes, localStorage, syncs other toggle -4. **HTMX sends request** → Background POST to save cookie (`hx-swap="none"`) -5. **Server responds** → Empty template, just cookie saved -6. **Result** → Smooth UX, both toggles synced, state persisted - -**Key Innovation:** Complete separation of concerns: -- **Visual feedback:** Instant CSS transitions (client-only) -- **State management:** Inline hyperscript (client-only) -- **Persistence:** HTMX background request (server cookie only) -- **No HTML swaps:** Templates return empty content - -**Debug Journey:** -1. Started with `outerHTML` swaps → Broke animations -2. Tried hyperscript functions with `element()` → Syntax errors -3. Attempted out-of-band swaps → Null reference on double-click -4. **Final solution:** `hx-swap="none"` + inline hyperscript + empty templates → Perfect! - ---- - -## 📊 Phase 7-8 Results - -### Toggle Architecture Evolution: - -| Aspect | Phase 7 (Broken) | Phase 8 (Working) | Result | -|--------|------------------|-------------------|--------| -| Animation Quality | Snap (digital) | Smooth (analogical) | ✅ Fixed | -| Error on Double-Click | `insertBefore` null error | No errors | ✅ Fixed | -| Desktop/Mobile Sync | Out-of-band swaps | Direct ID sync | ✅ Simpler | -| Server Templates | 50+ lines HTML | Empty comment | ✅ Cleaned | -| CSS Transitions | Broken by swap | Working perfectly | ✅ Fixed | -| Code Pattern | External functions | Inline hyperscript | ✅ Colocated | - -### Implementation Details: - -| Toggle Type | Lines of Code | Pattern | -|-------------|---------------|---------| -| Length Toggle (Desktop) | 18 lines inline HS | `hx-swap="none"` + inline | -| Length Toggle (Mobile) | 18 lines inline HS | Same pattern, syncs desktop | -| Logo Toggle (Desktop) | 16 lines inline HS | Same pattern | -| Logo Toggle (Mobile) | 16 lines inline HS | Same pattern | -| Theme Toggle (Desktop) | 16 lines inline HS | Same pattern | -| Theme Toggle (Mobile) | 16 lines inline HS | Same pattern | -| **Total** | **~100 lines** | **Pure client-side** | - -**Trade-off Analysis:** -- ❌ More inline code vs external functions (but colocated with markup) -- ✅ No syntax errors (direct ID selection works) -- ✅ No null reference bugs (no DOM swaps) -- ✅ Smooth animations (element preserved) -- ✅ Simple mental model (client handles visuals, server saves state) - -### Cumulative Progress: - -| Phase | Total Lines | Key Achievement | -|-------|-------------|-----------------| -| **Baseline** | 954 JS | - | -| **Phase 4A-6** | 239 JS | -715 lines (-74.9%) | -| **Phase 7** | Attempted | ❌ Syntax errors, bugs | -| **Phase 8** | 239 JS + ~100 inline HS | ✅ Bug-free smooth toggles | -| **Net Result** | **239** | **-74.9% + smooth UX** | - -**Note:** Phase 8 kept inline hyperscript for toggles instead of external functions because: -1. Direct ID selection (`#lengthToggle`) works, `element()` function doesn't exist -2. Colocated code is easier to maintain (behavior with markup) -3. No syntax errors with inline approach -4. Each toggle is self-contained and readable - ---- - -## 🐛 Phase 9: Zoom Control Bug Fixes (November 2025) - -### Issue 1: X Button Not Working - -**Problem:** The close button (X) on the zoom control wasn't responding to clicks after HTMX migration. - -**Root Cause:** -- Hyperscript `on click` handler conflicted with parent's `mousedown` event for drag functionality -- The `halt the event` in the drag handler prevented click events from bubbling -- The iconify-icon element inside the button was capturing clicks - -**Solution:** -1. Removed hyperscript `on click` from button to avoid event conflicts -2. Added `pointer-events: none` to iconify-icon element to prevent click interception -3. Implemented JavaScript event listener in `main.js` as reliable fallback - -```javascript -// static/js/main.js -function initZoomControlButtons() { - const closeBtn = document.getElementById('zoom-close'); - const zoomControl = document.getElementById('zoom-control'); - - if (closeBtn && zoomControl) { - closeBtn.addEventListener('click', function(e) { - e.preventDefault(); - e.stopPropagation(); - zoomControl.style.display = 'none'; - localStorage.setItem('cv-zoom-visible', 'false'); - }); - } -} -``` - -**Result:** ✅ X button now works 100% reliably - -### Issue 2: Drag Functionality Not Working - -**Problem:** Couldn't drag the zoom control to reposition it on the page. - -**Root Cause:** -- Variables (`isDragging`, `initialX`, `initialY`) weren't persisting across hyperscript event handlers -- Event target checking wasn't comprehensive enough - -**Solution:** Use hyperscript scope variables (`:variableName`) for state persistence - -```hyperscript -on mousedown(clientX, clientY) - set target to event.target - set targetTag to target.tagName - - -- Exit if clicking on interactive elements - if targetTag is 'INPUT' exit end - if targetTag is 'BUTTON' exit end - if target.classList.contains('zoom-value') exit end - - -- Use scope variables (:) for persistence across events - set :isDragging to true - set my *transition to 'none' - - set rect to my getBoundingClientRect() - set :initialX to clientX - rect.left - set :initialY to clientY - rect.top - - halt the event - -on mousemove(clientX, clientY) from document - if :isDragging is not true exit end - halt the event - - set currentX to clientX - :initialX - set currentY to clientY - :initialY - - set maxX to window.innerWidth - my offsetWidth - set maxY to window.innerHeight - my offsetHeight - - set currentX to Math.max(0, Math.min(currentX, maxX)) - set currentY to Math.max(0, Math.min(currentY, maxY)) - - set my *left to `${currentX}px` - set my *bottom to `${window.innerHeight - currentY - my offsetHeight}px` - set my *transform to 'none' - -on mouseup from document - if :isDragging is not true exit end - - set :isDragging to false - set my *transition to 'all 0.3s ease' - - set position to { bottom: my *bottom, left: my *left } - set localStorage['cv-zoom-position'] to JSON.stringify(position) -``` - -**Key Insight:** Regular hyperscript variables don't persist across events. Use `:variableName` for scope variables that maintain state throughout the element's lifetime. - -**Result:** ✅ Drag functionality works smoothly with 300px+ movement capability - -### Issue 3: Fixed Buttons Resizing with Zoom - -**Problem:** When zooming in/out, fixed buttons (shortcuts, info, back-to-top) were incorrectly changing size - becoming huge when zoomed out and tiny when zoomed in. - -**Root Cause:** -- Code was applying inverse zoom (`1 / zoomLevel`) to buttons **outside** the zoom-wrapper -- The buttons are positioned outside `#zoom-wrapper` div, so they aren't affected by page zoom -- The inverse calculation was backwards: zoom 25% → inverse 4x (huge buttons), zoom 175% → inverse 0.57x (tiny buttons) - -**Incorrect Code:** -```hyperscript --- Counter-zoom fixed buttons (WRONG - causes size issues) -set inverseZoom to 1 / zoomLevel -set #back-to-top's *zoom to inverseZoom -set #info-button's *zoom to inverseZoom -set #shortcuts-button's *zoom to inverseZoom -``` - -**Solution:** Remove inverse zoom entirely - buttons are already outside zoom context - -```html - -
- -
...
-
- - -{{template "back-to-top" .}} -{{template "info-button" .}} -{{template "shortcuts-button" .}} -{{template "zoom-control" .}} -``` - -**Test Results:** -``` -🧪 Testing Fixed Button Sizes at Different Zoom Levels - -📏 Testing at 25% zoom... - Info button: 50px - Shortcuts button: 50px - -📏 Testing at 100% zoom... - Info button: 50px - Shortcuts button: 50px - -📏 Testing at 175% zoom... - Info button: 50px - Shortcuts button: 50px - -✅ SUCCESS: Fixed buttons maintain consistent 50px size at all zoom levels! -``` - -**Result:** ✅ Buttons stay perfectly sized (50px) at all zoom levels (25%-175%) - -### Technical Lessons Learned - -1. **Event Handler Conflicts:** - - JavaScript event listeners have priority over hyperscript - - Use JavaScript for critical interactions (buttons, forms) - - Use hyperscript for declarative transformations - -2. **Hyperscript Scope Variables:** - - Regular variables: `set foo to...` - local to one event handler - - Scope variables: `set :foo to...` - persist across all event handlers on element - - Essential for drag/drop, multi-step interactions - -3. **CSS Zoom Property:** - - Elements outside zoomed container aren't affected - - Don't apply counter-zoom to elements already outside zoom context - - Understand DOM structure before applying transformations - -4. **Event Propagation:** - - `halt the event` stops all propagation - - Can prevent child element handlers from working - - Use `stopPropagation()` in JavaScript for fine control - -### Files Modified - -1. `templates/partials/widgets/zoom-control.html` - - Fixed drag handler with scope variables (`:isDragging`, `:initialX`, `:initialY`) - - Removed inverse zoom code for fixed buttons - - Improved interactive element detection - -2. `static/js/main.js` - - Added `initZoomControlButtons()` function (~30 lines) - - Registered in `DOMContentLoaded` event - -3. `templates/partials/navigation/hamburger-menu.html` - - Removed conflicting hyperscript from show zoom button - -4. `MODERN-WEB-TECHNIQUES.md` - - Updated documentation to reflect fixes - - Added technical lessons learned - -### Phase 9 Summary - -**JavaScript Change:** +30 lines (239 → 269 lines) -- Added for critical button reliability -- Necessary for production-grade interaction -- Still 71.8% reduction from baseline (954 → 269) - -**Bugs Fixed:** 3 critical issues -- ✅ X button click handler -- ✅ Drag functionality -- ✅ Fixed button sizing - -**Test Coverage:** Automated Playwright tests -- Button click verification -- Drag distance measurement (300px movement confirmed) -- Button size consistency across zoom levels - ---- - -**Maintained by:** CV Project Development Team -**Last Updated:** 2025-11-16 -**Status:** Phase 9 Complete ✅ | Zoom Control Fully Functional 🎉 - -**Final Stats:** -- 954 → 269 lines JavaScript (-71.8%) [+30 for zoom button reliability] -- 9 major optimization techniques implemented -- 165 lines organized hyperscript functions (scroll/print) + ~100 lines inline (toggles) -- Smooth "analogical" animations working perfectly -- Zero HTMX swap errors (bug-free double-click) -- All features preserved + improved UX -- **Phase 9:** All zoom control bugs fixed with automated tests ✅ - ---- - -*This document serves as both a technical reference and a demonstration of modern web development practices that prioritize web standards, performance, progressive enhancement, and superior user experience over JavaScript-heavy solutions.* diff --git a/prompts/001-implement-keyboard-shortcuts-help.md b/prompts/001-implement-keyboard-shortcuts-help.md deleted file mode 100644 index dd83e1f..0000000 --- a/prompts/001-implement-keyboard-shortcuts-help.md +++ /dev/null @@ -1,167 +0,0 @@ - -Implement a keyboard shortcuts help feature that displays all available keyboard shortcuts in the CV web application. This feature will help users discover and use keyboard shortcuts efficiently, improving the overall user experience and accessibility. - - - -This is a CV (resume) web application built with: -- Backend: Go with Hono-like routing patterns -- Frontend: HTMX + Hyperscript for interactivity -- Styling: Modern CSS with native HTML5 elements -- Philosophy: Minimal JavaScript, progressive enhancement, native browser APIs - -The app already has: -- An info modal using native `` element (reference pattern) -- Fixed action buttons (info icon, back-to-top, print, etc.) -- Keyboard shortcuts implemented but not documented -- HTMX-driven interactions with server endpoints - -Before starting, read the project documentation to understand the application structure and conventions: -@CLAUDE.md -@MODERN-WEB-TECHNIQUES.md - - - -Use the architecture agent to thoroughly analyze the codebase and identify ALL keyboard shortcuts and user actions: - -1. **Examine documentation** to understand application features and architecture -2. **Review all Go endpoints** to identify available actions (toggles, language switching, etc.) -3. **Search for keyboard event handlers** in hyperscript and JavaScript files -4. **Identify interactive elements** (buttons, toggles, forms) and their functions -5. **Analyze HTMX attributes** (hx-post, hx-get) to understand available actions - -Create a comprehensive list of: -- Existing keyboard shortcuts (Ctrl+P for print, Ctrl+0 for zoom reset, etc.) -- Actions that could benefit from keyboard shortcuts -- Standard browser shortcuts that work in the app (Ctrl+F for find, etc.) - - - -1. **Icon Button**: Create a keyboard shortcuts help button - - Position: Near the existing info icon in the fixed action buttons area - - Icon: Keyboard icon (use iconify-icon like other buttons) - - Behavior: Opens keyboard shortcuts modal on click - - Styling: Consistent with existing action buttons - -2. **Modal Dialog**: Create a keyboard shortcuts help modal - - Use native `` element (follow info modal pattern) - - Display all keyboard shortcuts in organized groups - - Include descriptions of what each shortcut does - - Clean, readable layout with proper spacing - -3. **Shortcuts Organization**: Group shortcuts logically - - Navigation shortcuts (scroll, jump to sections) - - View controls (zoom, toggles) - - Actions (print, download) - - Browser shortcuts (search, refresh) - -4. **Accessibility**: - - Proper ARIA labels for the button - - Keyboard navigation (ESC to close, Tab for focus) - - Screen reader friendly descriptions - -5. **Bilingual Support**: - - Spanish and English translations - - Follow existing i18n patterns in the codebase - - - -Follow the existing architectural patterns in the codebase: - -1. **Modal Pattern**: - - Use native `` element (see existing info modal as reference) - - Include `::backdrop` styling for overlay - - Close button with onclick="this.closest('dialog').close()" - - Simple inline onclick for opening: `onclick="document.getElementById('shortcuts-modal').showModal()"` - -2. **Button Pattern**: - - Follow fixed action button styling - - Use iconify-icon for the keyboard icon (find appropriate icon from mdi: collection) - - Position using existing CSS patterns for action buttons - -3. **File Structure**: - - Create modal template in `./templates/partials/modals/` or similar - - Add button to appropriate location (likely near info button) - - Update CSS if needed for styling - -4. **NO JavaScript required** for basic open/close (use native dialog features) - - Only use inline onclick attributes following existing patterns - - Leverage browser's built-in dialog functionality - -WHY these patterns matter: -- Native `` provides built-in accessibility, focus management, and ESC key handling -- Inline onclick keeps code simple and colocated with markup (following project philosophy) -- Consistent styling ensures professional, cohesive UI -- Minimal JavaScript aligns with project's "almost 0 JavaScript" goal - - - -Based on your research, include shortcuts such as (but not limited to): - -**Zoom Controls:** -- Ctrl/Cmd + Plus: Zoom in -- Ctrl/Cmd + Minus: Zoom out -- Ctrl/Cmd + 0: Reset zoom to 100% - -**Actions:** -- Ctrl/Cmd + P: Print friendly version - -**Browser Shortcuts (mention these too):** -- Ctrl/Cmd + F: Find in page -- Ctrl/Cmd + R: Refresh page - -Add any other shortcuts discovered during research. - -Organize them in a clean table or list format with: -- Shortcut keys (visual representation) -- Description of action -- Bilingual labels (ES/EN) - - - -Create/modify the following files: - -1. `./templates/partials/modals/shortcuts-modal.html` - Keyboard shortcuts modal dialog -2. Modify the appropriate template to add the keyboard shortcuts button (likely where other action buttons are) -3. Update CSS if needed for button positioning and modal styling (follow existing patterns) - -Use relative paths and ensure all changes integrate seamlessly with existing code. - - - -Before declaring complete, verify: - -1. **Research Complete**: - - Run searches to confirm all keyboard shortcuts are identified - - Check that all major user actions are covered - -2. **Functionality**: - - Button appears in correct position near info icon - - Clicking button opens modal - - ESC key closes modal - - Backdrop click closes modal - - Close button works - -3. **Visual Integration**: - - Button styling matches other action buttons - - Modal styling matches info modal - - Layout is clean and readable - -4. **Bilingual**: - - All text has Spanish and English versions - - Language switching works correctly - -5. **Accessibility**: - - ARIA labels present - - Keyboard navigation works - - Focus management is correct - - - -- Keyboard shortcuts help button visible and clickable near info icon -- Modal displays comprehensive list of all keyboard shortcuts -- Modal follows native `` pattern (like info modal) -- All shortcuts organized logically with clear descriptions -- Bilingual support (ES/EN) working correctly -- Zero JavaScript required for basic functionality (native dialog features only) -- Code follows project philosophy and existing patterns -