insertr

joakim/insertr

Fork 0

Commit Graph

Author	SHA1	Message	Date
Joakim	04e669eb95	Fix edit form content extraction - show clean customer view 🐛 Problem: Edit forms showed client view with edit buttons/emojis ✅ Solution: Extract clean content without edit interface elements 🔧 Changes: - extractContentFromElement() now properly removes all edit UI - Improved htmlToMarkdown() for better rich content conversion - setupEditableElement() preserves original clean content - Enhanced whitespace normalization in markdown conversion - Handles both simple text and rich markdown content types 🎯 User Experience: - Client sees: Content with edit buttons (✏️) - Edit form shows: Clean, properly formatted content - Customer sees: Original clean content (no edit UI) ✨ Whitespace improvements: - Removes excessive indentation and spacing - Normalizes line breaks and paragraph spacing - Clean, readable content in edit forms Critical fix for proper edit-in-place functionality	2025-08-29 23:04:29 +02:00
Joakim	af88e57272	Add working frontend prototype with edit-in-place functionality ✨ Features implemented: - Complete demo website (Acme Consulting Services) - Core insertr.js library with edit-in-place functionality - Support for simple text and rich markdown content - Mock authentication system (login/logout simulation) - Edit mode toggle for client interface - Local storage persistence - Visual feedback for saving content - Multi-page support (index.html, about.html) - Responsive design with clean UI 🎯 Three user experiences: - Customer: Clean website with no edit interface - Client: Same website + edit buttons when authenticated - Developer: Simple class-based integration 🏗️ Architecture: - Vanilla JavaScript (no framework dependencies) - Alpine.js ready for enhanced interactivity - CSS-only styling for edit indicators - Mock API structure for backend planning Next: Connect to Go backend with real persistence	2025-08-29 22:41:15 +02:00

Author

SHA1

Message

Date

Joakim

04e669eb95

Fix edit form content extraction - show clean customer view

🐛 Problem: Edit forms showed client view with edit buttons/emojis
✅ Solution: Extract clean content without edit interface elements

🔧 Changes:
- extractContentFromElement() now properly removes all edit UI
- Improved htmlToMarkdown() for better rich content conversion
- setupEditableElement() preserves original clean content
- Enhanced whitespace normalization in markdown conversion
- Handles both simple text and rich markdown content types

🎯 User Experience:
- Client sees: Content with edit buttons (✏️)
- Edit form shows: Clean, properly formatted content
- Customer sees: Original clean content (no edit UI)

✨ Whitespace improvements:
- Removes excessive indentation and spacing
- Normalizes line breaks and paragraph spacing
- Clean, readable content in edit forms

Critical fix for proper edit-in-place functionality

2025-08-29 23:04:29 +02:00

Joakim

af88e57272

Add working frontend prototype with edit-in-place functionality

✨ Features implemented:
- Complete demo website (Acme Consulting Services)
- Core insertr.js library with edit-in-place functionality
- Support for simple text and rich markdown content
- Mock authentication system (login/logout simulation)
- Edit mode toggle for client interface
- Local storage persistence
- Visual feedback for saving content
- Multi-page support (index.html, about.html)
- Responsive design with clean UI

🎯 Three user experiences:
- Customer: Clean website with no edit interface
- Client: Same website + edit buttons when authenticated
- Developer: Simple class-based integration

🏗️ Architecture:
- Vanilla JavaScript (no framework dependencies)
- Alpine.js ready for enhanced interactivity
- CSS-only styling for edit indicators
- Mock API structure for backend planning

Next: Connect to Go backend with real persistence

2025-08-29 22:41:15 +02:00

2 Commits