Public Profiles And Pages

File: 06-public-profiles-and-pages.md

Loading documentation...

# Public Profiles & Public Pages

## Overview

Public Profiles represent a creator’s primary presence; Public Pages are standalone pages (landing pages, link-in-bio, promo pages) that can be attached to a profile and optionally served via custom domains.

## Key Concepts
- Profile: owned by a user; has sections, links, media, base template, optional custom domain
- Public Page: owned by a user; has its own sections and base template; can be attached to one or more profiles; unique slug per user
- Custom Domain: mapped to a profile; domain resolution middleware serves the profile and its default page

## Data Model
- `PublicProfile` → user_id, slug, display fields, theme, SEO, `base_template_id`, `is_public`, `is_active`
- `ProfileSection` → ordered, references `SectionType`/`SectionTemplate`, stores `data` JSON
- `ProfileLink` → featured links (optional polymorphic target)
- `PublicPage` → user-owned, slug (unique per user), title, description, `base_template_id`, `is_public`
- `PageSection` → ordered sections for a page
- `CustomDomain`/`ProfileDomain` → verification and DNS meta, status

## API Endpoints (dashboard)
- Profiles: `/api/dashboard/public-profiles` (CRUD, analytics, media, links, sections, domains, public pages assignment)
- Pages: `/api/public-page-live-edit/*` for section CRUD and rendering; `/api/page-sections/{id}` direct section ops

Common calls (use global helpers):
```javascript
// Get profiles
const res = await apiGet('/api/dashboard/public-profiles');

// Update profile appearance
await apiPut(`/api/dashboard/public-profiles/${profileId}/appearance`, { theme_color: '#111827' });

// Create page section
await apiPost(`/api/public-page-live-edit/${pageId}/sections`, { section_type_id, section_template_id, data });
```

## Rendering Flow
- Profiles render via profile view with `base_template` header/footer and ordered `ProfileSection` partials
- Pages render via `public_page.blade.php` layout using `base_template` and ordered `PageSection` partials
- Section templates can be file-based or DB-stored; variables are resolved from `data`

## Custom Domains
- Users add domain to profile; system provides DNS records
- Validation endpoint: `POST /api/dashboard/public-profiles/{profileId}/domains/{domainId}/validate`
- On verified, middleware serves profile at the domain; default page can be set per profile

## Typical Workflows
1) Create Profile → add links/media → add sections → set base template → toggle public
2) Create Public Page → add sections → attach to profile → set as default or link from profile

## Permissions & Visibility
- All dashboard endpoints require `token.auth`
- Public visibility controlled by `is_public` at profile/page and per-section rendering rules

## Troubleshooting
- Domain not resolving: verify DNS records and validation status
- Section not rendering: confirm `section_template_id` and variable schema
- 404 on page slug: ensure slug is unique per user and page is `is_public: true`

Public Profiles And Pages

Public Profiles And Pages

📝 Page Notes

Add New Note