managarten/apps/memoro/apps/backend/SIGNUP_BRANDING.md at 6d2509c258f35bd110c23cc1c85c8bf7ccf277e4

mirror of https://github.com/Memo-2023/mana-monorepo.git synced 2026-05-23 04:06:43 +02:00

Till JS d8a2b37126 chore(memoro): import legacy backend, mobile, and landing apps

Adds the original NestJS backends (backend, audio-backend), Expo mobile app,
and Astro landing page as-is from the standalone memoro repo. These are
not yet migrated to monorepo standards (migration tracked in memory/CLAUDE.md).

Also adds eslint.config.mjs ignore for apps/*/apps/audio-backend/**
and .prettierignore entries for legacy memoro dirs.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-03-31 17:30:00 +02:00

3.4 KiB

Raw Blame History

Updated: 2025-11-05

Overview

The signup endpoint automatically applies Memoro branding to all confirmation emails. The branding is hardcoded in the service and includes:

App Name: Memoro
Logo: memoro-logo.png
Primary Color: #F8D62B (Yellow)
Secondary Color: #f5c500 (Golden Yellow)
Tagline DE: "Sprechen statt Tippen"
Tagline EN: "Speak Instead of Type"
Website: https://memoro.ai
Redirect URL: https://app.manacore.ai/welcome?appName=memoro
Copyright: "© 2025 Memoro · Made with 💛 in Germany"

You can optionally override specific branding fields per signup if needed.

Simple Usage

POST /auth/signup
{
  "email": "user@memoro.ai",
  "password": "SecurePass123!",
  "deviceInfo": {
    "deviceId": "web-123",
    "deviceName": "Chrome",
    "deviceType": "web"
  }
}

Result: Email automatically uses Memoro branding (yellow colors, Memoro logo, German/English taglines).

Custom Branding (Optional)

POST /auth/signup
{
  "email": "user@example.com",
  "password": "SecurePass123!",
  "deviceInfo": {
    "deviceId": "web-123",
    "deviceName": "Chrome",
    "deviceType": "web"
  },
  "metadata": {
    "branding": {
      "logoUrl": "custom-logo.svg",
      "primaryColor": "#FF5733"
    }
  }
}

Result: Email uses custom logo and color, other fields use Memoro defaults.

Full Custom Branding

POST /auth/signup
{
  "email": "user@example.com",
  "password": "SecurePass123!",
  "deviceInfo": {...},
  "metadata": {
    "branding": {
      "appName": "Custom App",
      "logoUrl": "custom-logo.svg",
      "primaryColor": "#2C3E50",
      "secondaryColor": "#34495E",
      "websiteUrl": "https://custom-app.com",
      "taglineDe": "Ihre Lösung",
      "taglineEn": "Your Solution",
      "copyright": "© 2025 Custom App"
    }
  }
}

Branding Fields

All fields are optional:

Field	Type	Description	Example
`appName`	string	App display name	`"My App"`
`logoUrl`	string	Logo filename (from Supabase Storage)	`"app-logo.png"`
`primaryColor`	string	Primary color (hex)	`"#F8D62B"`
`secondaryColor`	string	Secondary color (hex)	`"#f5c500"`
`websiteUrl`	string	Website URL	`"https://app.com"`
`taglineDe`	string	German tagline	`"Sprechen statt Tippen"`
`taglineEn`	string	English tagline	`"Speak Instead of Type"`
`copyright`	string	Footer text	`"© 2025 My App"`

TypeScript Types

import { BrandingConfig } from './auth-proxy/interfaces/branding.interface';

// Example
const branding: BrandingConfig = {
  logoUrl: 'custom-logo.svg',
  primaryColor: '#FF5733'
};

await authProxy.signup({
  email: 'user@example.com',
  password: 'pass123',
  deviceInfo: {...},
  metadata: { branding }
});

How It Works

No metadata → Mana Core uses default branding for your app
With metadata.branding → Mana Core merges your branding with defaults
Any missing fields → Filled in by Mana Core defaults

That's It!

✅ Backward compatible - existing signups work unchanged
✅ Simple - just add metadata.branding when you want custom branding
✅ Flexible - override any or all branding fields
✅ No new endpoints - just use POST /auth/signup

3.4 KiB Raw Blame History

Memoro Service - Signup Branding Support