Files
insertr/test-sites
Joakim d877366be0 Consolidate type definitions and fix API contract
- Move all ContentItem, ContentClient, ContentResponse types to engine/types.go as single source of truth
- Remove duplicate type definitions from content/types.go
- Update all imports across codebase to use engine types
- Enhance engine to extract existing data-content-id from HTML markup
- Simplify frontend to always send html_markup, let server handle ID extraction/generation
- Fix contentId reference errors in frontend error handling
- Add getAttribute helper method to engine for ID extraction
- Add GetAllContent method to engine.DatabaseClient
- Update enhancer to use engine.ContentClient interface
- All builds and API endpoints verified working

This resolves the 400 Bad Request errors and creates a unified architecture where the server is the single source of truth for all ID generation and content type management.
2025-09-16 16:45:29 +02:00
..

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 layouts
  • framework-based/ - Sites using CSS frameworks (Bootstrap, Tailwind, etc.)
  • complex/ - Complex layouts with advanced interactions
  • templates/ - Template files for new test sites
  • scripts/ - Automation utilities for downloading and enhancing sites
  • results/ - 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

  1. Download - Use scripts to fetch HTML and assets
  2. Enhance - Add insertr classes to content sections
  3. Test - Verify functionality across different layouts
  4. Document - Record results and compatibility notes

Each Site Includes

  • Original HTML files
  • assets/ directory with CSS, JS, and images
  • README.md with site-specific testing notes
  • insertr-config.json with enhancement configuration