Joakim
eabb7b16e8
- Remove obsolete cmd/auto_enhance.go command (replaced by unified enhance) - Implement EnhanceInPlace method using unified pipeline - Remove generated demo files from git tracking - Verify all functionality works after cleanup: * go build successful * enhance command working correctly * unified pipeline (discovery → ID generation → content injection) verified * clean command structure (only enhance, serve, restore commands) The codebase is now clean with no legacy auto-enhance references or stub implementations. All functionality consolidated into the unified Discoverer + Enhancer architecture.
Test Sites Collection
This directory contains a collection of real-world websites for testing insertr CMS functionality across different site types, CSS frameworks, and complexity levels.
Directory Structure
simple/- Simple sites with vanilla CSS and minimal layoutsframework-based/- Sites using CSS frameworks (Bootstrap, Tailwind, etc.)complex/- Complex layouts with advanced interactionstemplates/- Template files for new test sitesscripts/- Automation utilities for downloading and enhancing sitesresults/- Testing results, reports, and documentation
Site Categories
Simple Sites
- dan-eden-portfolio - Clean personal portfolio with minimal styling
- github-pages-simple - Basic GitHub Pages site with standard layout
Framework-Based Sites
- bootstrap-docs - Bootstrap documentation sections
- tailwind-landing - Tailwind CSS marketing pages
Complex Sites
- stripe-product - Enterprise product pages with rich content
- linear-features - Modern SaaS feature pages
Testing Process
- Download - Use scripts to fetch HTML and assets
- Enhance - Add insertr classes to content sections
- Test - Verify functionality across different layouts
- Document - Record results and compatibility notes
Each Site Includes
- Original HTML files
assets/directory with CSS, JS, and imagesREADME.mdwith site-specific testing notesinsertr-config.jsonwith enhancement configuration