Issues

This would allow for greater creative freedom and create an interesting visual dynamic, particularly in editorial, portfolio, or magazine layouts. Interesting options: right, left, top, bottom

user: "trying to create a page called "home" gives error, probably because internally you have home by default"

allow Navigation to hide automatically. expand on hoover.

bases on vercel's workflow builder, inspired by vuo

I would like to suggest an additional option for the video settings. Currently, videos already support useful playback options such as: autoplay loop muted show controls As an additional feature, it would be great to have a “play on hover” / “start on hover” option. This could create a much more subtle and interactive way of using motion content, especially in galleries, grids, or portfolio layouts, where constant autoplay can sometimes feel visually overwhelming. A hover-triggered playback option could allow motion to appear only when the user intentionally interacts with a specific element, creating a cleaner and more dynamic browsing experience.

I would like to suggest an additional navigation option. Currently, there are several navigation modes available: - horizontal navigation with permanently visible links - sidebar navigation with a permanent vertical list of links - burger navigation with a separate overlay screen While these options already offer flexibility, I sometimes find that permanently visible navigation elements interrupt the visual flow of a page, while the current burger overlay can feel a bit detached from the browsing experience. I would therefore love a more minimal expandable navigation system. For example: clicking the burger icon could simply expand a clean list of links directly over the current page after selecting a link, the menu would automatically collapse again alternatively, a similar expandable/collapsible navigation could also work from the logo area (similar to sidebar navigation, but hidden until activated) The idea would be to have navigation available when needed, while otherwise keeping the page visually clean and uninterrupted. I think this could create a smoother and more elegant browsing experience, especially for visually driven or minimal layouts.

Description: Currently, the Burger Overlay (the menu that opens when clicking the hamburger icon) only allows a solid background color with customizable color and typography settings. This limits the visual flexibility of the overlay and can interrupt the overall design flow of the page. Suggested solution: Add more background options for the Burger Overlay, including: A transparent overlay option, allowing the current page background to remain visible behind the menu The option to upload and use a custom background image for the overlay This would allow the menu links to appear directly over the existing page background or over a specifically designed background image. Benefit: This would create a more seamless and visually consistent user experience, while offering greater design freedom and better integration of the navigation menu into the overall page aesthetic.

Description: In the Canvas layout, it is currently possible to move individual images or the entire layout, but not multiple selected elements at once. This often limits the full potential of the Canvas layout mode. For example, if I need to create space in the middle of a longer and possibly complex layout, I cannot shift a group of elements (e.g. all items on one side) together. Instead, I have to move each element individually to make space for the image I want to insert. This can result in having to partially dismantle and rebuild the layout. Since this mode enables highly customized and intricate designs, this may require undoing work that took significant time and effort to create. Suggested solution: Allow selecting multiple assets (e.g. via the Assets panel) and moving them as a group, similar to layer selection in design tools like Photoshop. Benefit: This would make editing layouts in Canvas mode much faster and more efficient, both for simple arrangements (e.g. inserting an image into a row of elements) and for more complex compositions. It would also better support the intuitive creative potential of the Canvas workflow by preserving carefully arranged layouts and avoiding unnecessary rework. This improvement would benefit both horizontal and vertical use cases.

correct canonical URLs on custom domains etc etc) so your users have good SEO, also make sure its only accessible on the custom domain when user sets one, and that the salon url redirects properly to the custom domain to avoid dublicate content issues and when users port sites from the old salon, the redirects must pass the link juice (301 redirect vs 302)

## Overview Integrate [Agent Browser](https://agent-browser.dev/) — a headless browser automation CLI built for AI agents — to enable automated end-to-end testing, migration verification, and quality assurance across the New Salon platform. Agent Browser uses a Rust CLI + Playwright daemon architecture with a token-efficient "refs" system (~200-400 tokens vs ~3000-5000 for full DOM), making it ideal for AI-driven testing workflows. --- ## Implementation Plan ### Phase 1: Setup & Infrastructure - Install Agent Browser CLI (npm or Homebrew) - Configure daemon settings for our development environment - Set up test runner scripts in `package.json` (e.g., `npm run test:e2e`) - Create `/tests/e2e/` directory structure with shared utilities - Document setup in CLAUDE.md and developer onboarding guide ### Phase 2: Layout Engine Visual Testing - Write automated visual tests for all 8 layout engines: - Canvas: free-form positioning, block overlap, z-index - Mosaic: tile responsiveness, aspect ratios - Slideshow: navigation, transitions, caption display - Justified: row filling, aspect-ratio preservation - Column: snap-to-grid, responsive breakpoints - Fixed Height: row height consistency, floating images - Variable Size: masonry layout, variable widths - Square: uniform aspect ratio grid alignment - Screenshot comparison baselines for each engine - Test across viewport sizes (mobile, tablet, desktop) ### Phase 3: Editor Flow Testing - Block CRUD operations (create, edit, delete, reorder) - Drag-and-drop interactions via @dnd-kit - Section management (add, reorder, delete sections) - Panel interactions (Page, Section, Layout tabs) - Navigation editor flows - Theme switching and preview - Rich text editing (TipTap) interactions ### Phase 4: Migration Verification - Automated comparison between legacy salon.io pages and migrated new.salon.io pages - Fetch legacy page via salon.io JSON API - Render migrated version and capture screenshots - Pixel-diff or structural comparison reporting - Batch verification across migrated user sites ### Phase 5: Payment & Auth Flow Testing - Stripe Checkout session creation and redirect - Subscription management (upgrade, downgrade, cancel, reactivate) - Customer Portal access and navigation - Test all 5 tiers: Free, Basic, Premium, Pro, Pro Lifetime - Webhook handling verification - Auth flows: sign up, sign in, password reset, magic links ### Phase 6: Public Site & SEO Auditing - Crawl published user sites for meta tag verification - OpenGraph and social sharing preview validation - Accessibility audit (WCAG compliance checks) - Custom domain routing and SSL verification - Content width modes (full-bleed, full, wide, inset) rendering - Theme CSS variable application on public pages ### Phase 7: CI/CD Integration - Add Agent Browser tests to Vercel deployment pipeline - Post-deploy smoke tests on preview and production URLs - Failure alerting and screenshot capture on test failures - Test result reporting and trend tracking - Multi-session isolation for parallel test execution --- ## Key Benefits - **Token efficiency**: Refs system uses 10-20x fewer tokens than full DOM, reducing AI testing costs - **Multi-session isolation**: Test authenticated vs anonymous views simultaneously - **CLI-first**: Easy to script into CI/CD pipelines - **Cross-platform**: Works on macOS, Linux, Windows ## Dependencies - Agent Browser CLI (Rust + Node.js) - Playwright (managed by Agent Browser daemon) - Chrome/Chromium browser ## Notes - We already have Playwright MCP connected — Agent Browser complements it for CI/CD and batch testing - Start with Phase 1-2 post-launch (after March 13, 2026) - Prioritize layout engine visual testing as highest-value first use case