Issues

- Upload API: signed URLs for direct browser-to-Mux upload - Upload UI: drag-drop in VideoEditPanel, progress bar, processing status - Playback: HLS adaptive streaming, poster/thumbnail, autoplay/loop/muted controls - Tier gating: Free=0, Basic=5, Premium=25, Pro=unlimited **Files:** `src/components/editor/VideoEditPanel.tsx`, new `src/lib/mux.ts`, new `app/api/video/upload/route.ts`

Public-facing user profile page. Frontend design penned out in new-salon-app/new-salon-profile.pen.

starting from the request invite flow, the admin invite flow, the user invites users flow, user questionaire etc. we need "Complete your Profile" Message Complete your Profile make users aware of profile customisation. "You can customise your profile now or do it later." Migration -Emails, communication angle: "Claiming your unique username now is a smart move, though!" update Migration Dashboard http://localhost:3006/legacy/migration-status Migration Status Dashboard add email campaign features from http://localhost:3006/legacy/overdue to Migration Status Dashboard make sure legacy user are identified and are allowed to claim their legacy username and member status as a site tier. legacy user badge. member since remember legacy join date. so we can show on user profle , e.g. "Joined January 2013" we already have very elaborated migration process and legacy salon api on username/settings/migration this should evolve or sync with legacy user account claim process

Admin floating toolbar component - shows when an admin views any user's site

New block type with a simple email input + submit button Stores the Mailchimp list URL in block settings Posts directly to Mailchimp's form action URL (no API key needed) Gives you styling control that matches the site theme Requires: new block type in src/types/blocks.ts, renderer, editor UI

## Summary Upgrade the invite flow to remove friction for admins, pre-fill invited user details, collect artistic profile data during signup, and deliver a personalized welcome experience on first login. ## Current vs. Planned | | Current | Planned | |---|---|---| | Admin invite | 3 steps (request → approve → send email) | 1 step (enter email → done) | | Email on signup | User types it manually | Pre-filled and locked from invite | | Signup questions | None (email/username/password only) | + artistic practice, website, social link | | First dashboard visit | Generic empty state | Personalized welcome banner | --- ## A. Admin Direct Invite **New endpoint:** `POST /api/admin/invite` Accepts `{ email, firstName? }`. In one step: 1. Validates caller is admin 2. Creates `invite_requests` row with `status: approved`, `source: admin_direct`, `invited_by: admin_user_id` 3. Generates invite code 4. Sends invite email with link `/auth/signup?invite=CODE` The existing request → approve → send flow stays intact for organic signups. **Database changes:** ```sql ALTER TABLE invite_requests ADD COLUMN invited_by UUID REFERENCES user_profiles(id), ADD COLUMN source TEXT DEFAULT 'request'; -- Values: request, admin_direct, user_referral (future) ``` --- ## B. Pre-filled Email on Signup When an invited user clicks `/auth/signup?invite=CODE`, the email is pre-filled from the invite record. **New RPC function:** `get_invite_by_code(code)` — returns the invite row including email. **Signup page:** Fetches invite details server-side, passes `inviteEmail` to AuthForm. Email field rendered as read-only: "Invited as maria@example.com". **Security:** On submit, verify signup email matches the invite record email. --- ## C. Pre-Signup Questionnaire Two-step signup flow. Step 1: credentials (email, username, password → Continue). Step 2: three questions (→ Create Account). ### Question 1: Artistic Practice (required, multi-select chips) | | | | | |---|---|---|---| | Photography | Illustration | Painting | Graphic Design | | Architecture | Fashion | Film & Video | Sculpture | | Digital Art | Mixed Media | Typography | Animation | | Music | Writing | Crafts | Other | Selecting "Other" shows a freetext input. ### Question 2: Website Link (optional) Text input. Placeholder: `https://your-portfolio.com` ### Question 3: Social Link (optional) Text input. Placeholder: `https://instagram.com/yourusername` Platform auto-detected from URL (instagram.com → instagram field, twitter.com → twitter field, etc.) ### Data Flow Questionnaire answers stored in `user_metadata` during the `signUp()` call. After email verification, the auth callback syncs metadata to `user_profiles`: - `artistic_practice` → new `TEXT[]` column - website → existing `website` column - social link → parsed to appropriate social column **Database changes:** ```sql ALTER TABLE user_profiles ADD COLUMN artistic_practice TEXT[]; ``` --- ## D. Post-Signup Welcome After email verification, redirect to `/{username}/dashboard?welcome=true`. **New component:** `WelcomeBanner` — shows above the empty dashboard bento grid: - "Welcome to Salon.io, Maria!" - If artistic practice known: "We're thrilled to have a fellow photographer on board." - Dismiss button removes the `?welcome=true` param --- ## E. Terms of Service Acceptance Currently there is no ToS acceptance anywhere in the signup flow. This must be added before public launch (March 13). ### Placement The ToS checkbox goes on Step 2 (questionnaire), right above the "Create Account" button: ``` Step 2: About You ┌─────────────────────────────────────┐ │ What do you create? [chips...] │ │ Website link [________] │ │ Social link [________] │ │ │ │ ☐ I agree to the Terms of Service │ │ and Privacy Policy │ │ │ │ [Create Account] │ └─────────────────────────────────────┘ ``` - Checkbox is **unchecked by default** (GDPR requirement — no pre-checked consent) - "Create Account" button disabled until checkbox is checked - "Terms of Service" and "Privacy Policy" are links to `/terms` and `/privacy` - Not a pre-checked box — must be an affirmative action by the user ### What Gets Stored On signup, the acceptance timestamp is included in `user_metadata`: ```typescript options: { data: { username, artistic_practice: [...], tos_accepted_at: new Date().toISOString(), // ISO 8601 tos_version: "2026-03-13", // Version of ToS accepted } } ``` After email verification, synced to `user_profiles`: ```sql ALTER TABLE user_profiles ADD COLUMN tos_accepted_at TIMESTAMPTZ, ADD COLUMN tos_version TEXT; ``` ### Why This Moment The ToS acceptance happens before account creation — before the user receives any value (the 100 SLN signup bonus from the SLN Ledger spec is credited on email confirmation, which comes after). This sequence ensures: 1. User agrees to terms (Step 2, checkbox) 2. Account is created (Supabase signUp) 3. User verifies email (confirmation link) 4. SLN bonus credited (+100 SLN) 5. User lands on dashboard (welcome banner) Legal consent is captured before any credits, subscriptions, or platform features are accessible. ### Legal Requirements (EU/GDPR) | Requirement | How we meet it | |---|---| | Affirmative consent | Unchecked checkbox, user must click | | Informed consent | Links to full ToS and Privacy Policy | | Proof of consent | `tos_accepted_at` timestamp + `tos_version` stored | | Version tracking | `tos_version` field tracks which version was accepted | | Re-consent on changes | When ToS version changes, prompt existing users to re-accept | --- ## New Files | File | Purpose | |---|---| | `app/api/admin/invite/route.ts` | Admin direct invite endpoint | | `src/components/SignupQuestionnaire.tsx` | Questionnaire UI (chips + inputs) | | `src/components/dashboard/WelcomeBanner.tsx` | Personalized welcome banner | | `src/config/artistic-practices.ts` | Category list constant | | `src/utils/social-link-parser.ts` | Detect platform from URL | | `supabase/migrations/YYYYMMDD_invite_flow_upgrade.sql` | Schema + RPC changes | ## Modified Files | File | Change | |---|---| | `src/components/AuthForm.tsx` | Two-step flow, `inviteEmail` prop, questionnaire integration | | `app/auth/signup/page.tsx` | Server-side invite lookup, pass email | | `app/auth/callback/page.tsx` | Sync metadata to profile, `?welcome=true` redirect | | `src/hooks/use-auth.ts` | Extend `signUp()` with questionnaire metadata | | `src/components/dashboard/EmptyDashboard.tsx` | Integrate WelcomeBanner | --- ## Implementation Sequence 1. Database migration (columns + RPC) 2. Config and utilities 3. Admin invite API 4. Signup page (server-side invite lookup) 5. AuthForm two-step flow + SignupQuestionnaire 6. use-auth hook extension 7. Auth callback (profile sync + welcome redirect) 8. WelcomeBanner component 9. Email template updates *Full spec: `new-salon-app/docs/ongoing/INVITE-FLOW-UPGRADE.md`*

## Summary Implement an affiliate/referral program that turns paying customers into a scalable growth channel. The program — called "New Salon Partners" — lets any paying customer earn 20% recurring commissions for 12 months on referred subscriptions, with partner perks and milestone rewards. ## Program Structure **Eligibility:** Any paying customer (Basic, Premium, Pro, or Pro Lifetime) with at least one active subscription. No application process — auto-eligible. **Commission Model: 20% Recurring for 12 Months** | Detail | Value | |---|---| | Rate | 20% of referred customer's subscription revenue | | Type | Recurring — pays on every successful renewal | | Duration | 12 months from referred customer's first payment | | Cookie window | 90 days | | Attribution | Last-click with referral code override | **Revenue per Referral:** | Referred Tier | Monthly Commission | Total over 12 months | |---|---|---| | Basic (€10/mo) | €2/mo | €24 | | Premium (€20/mo) | €4/mo | €48 | | Pro (€40/mo) | €8/mo | €96 | | Pro Lifetime (€399-499) | €79.80-99.80 (one-time) | €79.80-99.80 | **Payouts:** €25 minimum threshold, monthly on the 15th. Options: PayPal, bank transfer, or account credit. **Tier Bonuses:** Pro/Pro Lifetime affiliates get 25% commission instead of 20%. ## Partner Perks | Perk | Requirement | |---|---| | Partner badge on profile | Any paid tier | | Referral dashboard | Any paid tier | | Early access to features | 5+ referrals | | Partner directory listing | 10+ referrals | | Priority support | 10+ referrals | | Annual partner spotlight | Top 10 partners | ## Milestone Rewards | Milestone | Reward | |---|---| | First referral | Welcome Partner email + badge | | 5 paying referrals | 1 month free on current tier | | 10 paying referrals | Lifetime "Founding Partner" badge + directory listing | | 25 paying referrals | Free upgrade to next tier for 6 months | | 50 paying referrals | Pro Lifetime granted | ## Implementation Plan ### Phase 1: Launch with Rewardful (Pre-Launch → Launch Day) - Sign up for Rewardful ($49/mo), connect Stripe, configure 20%/12mo/90-day - Add Rewardful tracking script + Stripe checkout metadata integration - Update `/{username}/settings/invite` with referral link and basic stats - Create `/partners` landing page ### Phase 2: Custom Build (when 50+ active affiliates) - Full custom solution with Supabase tables (`affiliates`, `referral_conversions`, `affiliate_payouts`, `referral_clicks`) - Integrated dashboard in settings, partner badges, milestone automation - Stripe webhook integration for automatic commission tracking ## Revenue Impact (Conservative Estimate, Year 1) - 20 active affiliates × 3 referrals each = 60 new paying customers - Annual revenue from referrals: €10,800 - Commission cost: €2,160 + €540 (Rewardful) - **Net revenue gain: €8,100** ## Competitor Comparison | Platform | Commission | Type | Cookie | |---|---|---|---| | Squarespace | $100-200 | One-time | 30 days | | Wix | $100 | One-time | 30 days | | Webflow | 50% | Recurring, 12 months | 90 days | | **New Salon** | 20% | Recurring, 12 months | 90 days | *Full spec: `new-salon-app/docs/ongoing/AFFILIATE-PROGRAM-PLAN.md`*

## Summary Implement the SLN credit economy as an internal ledger on Supabase. This is Phase 1 of the SAL Protocol — a launch-ready credit system with zero blockchain dependency. Users see "credits" or "SLN balance" while the underlying mechanics are forward-compatible with on-chain settlement in later phases. ## Key Details **Exchange Rate:** Fixed at 1000 SLN = €10 (1 SLN = €0.01) **Onboarding:** New users receive +100 SLN (~€1.00) on email confirmation, plus 5 invite slots. **Invite System:** - Sending an invite costs 20 SLN - When invitee publishes a site: inviter gets +100 SLN (5x return) - When invitee upgrades to Basic: inviter gets +500 SLN bonus + 200 SLN commission - When invitee upgrades to Premium/Pro: inviter gets +1000 SLN bonus + 400-800 SLN commission - Maximum return per invite: 1,600 SLN on 20 SLN investment (80x) **Commission on Upgrades:** 20% of the subscription's first payment, converted to SLN at fixed rate. Recurring commissions deferred to Phase 2. **Spending SLN (at launch):** - Send invite: 20 SLN - Apply as subscription discount: 1:1 at €0.01/SLN - Upgrade to Basic Monthly: 1000 SLN - Cash out: Min 1000 SLN (€10), PayPal or bank transfer, manual review, monthly **Credit Expiry:** 24 months of account inactivity (no login) ## Database Changes - Extend `user_profiles` with `sln_balance`, `invite_slots_total`, `invite_slots_used` - New table: `sln_transactions` (full double-entry ledger with type, amount, balance_after) - New table: `sln_cashout_requests` (manual payout queue) - Extend `invite_requests` with inviter tracking - Atomic `credit_sln` RPC function for all balance mutations - Daily reconciliation query to verify balance integrity ## New API Routes | Route | Method | Purpose | |---|---|---| | `/api/sln/balance` | GET | Current SLN balance and slot count | | `/api/sln/transactions` | GET | Paginated transaction history | | `/api/sln/cashout` | POST | Submit cash-out request | | `/api/sln/apply-discount` | POST | Calculate SLN discount for checkout | | `/api/admin/sln/cashouts` | GET | Pending cash-out requests (admin) | | `/api/admin/sln/cashouts/[id]` | PATCH | Approve/reject cash-out | | `/api/admin/sln/adjust` | POST | Manual balance adjustment | ## Integration Points 1. **Signup flow** — +100 SLN on email confirmation 2. **Invite flow** — SLN debit on send, reward on invitee site publish 3. **Stripe webhook** — Commission on referred user's first subscription payment 4. **Checkout flow** — SLN discount support with atomic debit on payment confirmation 5. **Settings page** — Replace invite placeholder with full balance/transaction/cashout UI ## Phase 2 Migration Path Phase 1 Supabase ledger maps 1:1 to Phase 2 on-chain (BSV-20 SLN tokens). User balances minted as tokens, transaction history archived, UI stays the same. Only visible change is a wallet connection step. *Full spec: `new-salon-app/docs/ongoing/SLN-PHASE-1-INTERNAL-LEDGER.md`*

enhance the ui for the image block settings panel

- Import site logo from legacy profile (`header_image`, `logo` field) - Translate legacy nav styles: horizontal, vertical to sidebar, center to horizontal-centered, none to horizontal - Import navigation colors and font settings - Detect legacy filtered pages and create collection-enabled sections with tag filters - Full caption import from `asset.title` and `i18n.[lang].title` (not just alt text) **Files:** `app/api/migration/import-stream/route.ts`, `src/lib/migration/legacy-service.ts`

- Extend CollectionConfig with `collectionSource`: pages / images / text / video / all - Collection rendering per source type: pages as page cards, images as masonry grid, text as list, video as video grid - Extend `CollectionSettings.tsx` with source type selector - Preview count updates live - Add to collection shortcut from asset gallery (tag assignment) **Files:** `src/components/salon/editor/CollectionSettings.tsx`, `src/types/blocks.ts`, `src/hooks/use-collection.ts`

- Redesign hero with clearer value proposition for creative professionals - Showcase real user sites (pull from actual published sites) - Per-site pricing calculator with interactive slider - Migration CTA for legacy salon.io users - Mobile-first responsive design **Files:** `src/components/landing/NewSalonLanding.tsx`

- Database: create `tags` + `asset_tags` join tables (normalized approach) - Add TagInput to image, text, and video edit panels - Asset gallery: tag display on thumbnails, filtering by tag, bulk tag assignment - Tag cloud of used tags - Sort by tag, date, size, name **Files:** Supabase migration, `ImageEditPanel.tsx`, `TextEditPanel.tsx`, `VideoEditPanel.tsx`, `AssetGallery.tsx`

- Expand SiteThemeSelector from presets-only to custom editing - Allow editing individual colors within a preset (primary, secondary, accent, background, text) - Typography presets: Google Fonts subset (20-30 curated fonts), font size scale selector - Per-section style overrides (color scheme, font override) - Live preview as colors/fonts change **Files:** `src/components/theme/SiteThemeSelector.tsx`, `src/types/site-theme.ts`

- ImageEditPanel (62KB) extract into sub-components - TextEditPanel (70KB) extract into sub-components - Consistent UX: crop/resize, caption editing, alt text, formatting toolbar - Style preset picker more prominent in text panel - Cross-project section copy (user feedback) - Image opacity control (user feedback) **Files:** `src/components/editor/ImageEditPanel.tsx`, `src/components/editor/TextEditPanel.tsx`

- Rewrite `PricingPage.tsx` with per-site calculator - "How many sites do you need?" slider showing monthly total - First site full price, additional sites at 50% - Lifetime Pro section: early bird 399 / regular 499, 2 Pro sites included **Files:** `src/components/landing/PricingPage.tsx`

allow Navigation to hide automatically. expand on hoover.

add option to have a horizontal scrolling canvas --- *Related doc: `layouts/canvas`*

bases on vercel's workflow builder, inspired by vuo

Description: When switching between edit and view mode, the page automatically jumps back to the top. This interrupts the workflow, especially when working on longer pages, as the user has to manually scroll back to the previous position each time. Suggested solution: Preserve the current scroll position when switching between edit and view mode. Benefit: This would create a smoother and more efficient workflow, especially for longer pages, by maintaining context and reducing unnecessary navigation. Optional enhancement: Make this behavior configurable (e.g. “preserve scroll position” vs. “always scroll to top”), allowing users to choose the behavior that best fits their workflow.

Currently, it is only possible to integrate video content via external embeds (e.g. YouTube or Vimeo). There is no option to use video files directly within layouts. This limits the ability to include moving image content in a simple and flexible way. Suggested solution: Allow the use of video files directly within layouts, either via upload or by linking to external sources. Benefit: This would make it possible to integrate moving image content more easily and flexibly, enhancing the visual possibilities and overall design of a page. As motion content has become a standard element in modern web design, this feature would align the tool with common expectations and evolving design practices.

In the previous version of Salon, the background image was visible in Lightbox mode, which helped maintain the visual context of the page. Currently, when opening images in the Lightbox view, the background image is not displayed. While it is possible to adjust the background color, there is no option to display the background image in this mode. Suggested solution: Enable the background image to be displayed in the Lightbox view. Benefit: This would preserve the overall visual design and atmosphere when viewing images in Lightbox mode, creating a more consistent and immersive user experience.

Currently, background colors can be selected using the built-in color picker (including hex input and predefined color options). However, it is not possible to pick a color directly from the canvas or from images within the workspace. This makes it difficult to match colors precisely when working with existing visual elements. Suggested solution: Add an eyedropper tool that allows users to sample colors directly from the canvas or uploaded images. Benefit: This would enable faster and more accurate color matching, improving design consistency and streamlining the workflow. It would also align the tool with standard functionality found in many design applications.

In the previous version of Salon, it was possible to create and adjust horizontal canvases with groups of images in just a few simple steps. This was very convenient and the layout option I used most. In the new version of Salon, the horizontal canvas option is only available in canvas mode. While this works great for many cases, it can be unnecessarily time-consuming for many common use cases. For example, if I want to arrange a series of images (e.g. 20 images of the same size with consistent spacing) in a horizontal row, doing this in canvas mode requires a lot of manual work. Any changes (such as size, spacing, or order) also have to be adjusted manually and individually for each image. Suggested solution: Enable horizontal canvas in fixed height layout mode, with flexible options for sizing and spacing. Benefit: This would allow for quick and efficient creation and adjustment of consistent horizontal image rows, while avoiding the manual overhead required in canvas mode. It would significantly improve workflow efficiency for common horizontal layout tasks.

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

we need a total reality check and overhaul of mobile and device preview. both are pretty much broken now whats expected is that when a user selects mobile device preview, a special panel in sidebar opens, with 3 main tabs section, navigation, style for every section the user should be able to select alternative layout type for mobile. note, that the user should not be able to edit content when in mobile preview mode, but only change/optimise a subset of settings for mobile display

- Database: `content_translations` table + `languages`/`default_language` columns on `websites` - Editor: floating toolbar language switcher pill (only when 2+ languages enabled) - Viewer: `?lang=de` URL param, `Accept-Language` detection, `hreflang` SEO tags - Translatable content: text blocks, image captions/alt, page titles/descriptions, nav labels, site title **Files:** Supabase migration, `src/hooks/use-translations.ts`, `EditorLayout.tsx`, `TextEditPanel.tsx`, `ImageEditPanel.tsx`

- Database: `follows`, `likes`, `posts` tables - Post types: site published (auto), page added (auto), image shared, text post, repost - Following feed (content from people you follow) - Discover feed (trending/new content across platform) - Like button on sites, pages, images - Follow/unfollow on user profiles - Basic in-app notification system **Files:** Supabase migration, new components in `src/components/social/`

- Unified color picker behavior across all panels (text, backgrounds, navigation, theme) - Always show: recent colors (last 8 used), theme colors, standard presets - Compact mode for inline use, expanded mode for detailed editing - Smart suggestions: complementary colors from site theme, high-contrast options against background **Files:** `src/components/ui/color-picker.tsx`

Allow users to duplicate and save sections for re-use. Should provide customizable copy options: - Full copy with layout, styles, images, video, and text - Template copy with placeholders for images, video, and text - Duplicate on same page - Duplicate on different page - Duplicate on new page - Save as template