Skip to content

Creator Hub — Final Review Report

Reviewer: reviewer specialist
Date: 2026-05-25
Step: 9-review

Summary

The platform is architecturally solid and substantive. All major surfaces (landing, auth, profile, editor, dashboard) are built and functional. However, four critical integration gaps prevent key features from working end-to-end: the theme picker is fully built but completely disconnected from the rest of the app; the scheduling block type is invisible on the live profile; the mobile sidebar has no toggle button (dashboard inaccessible on mobile); and the analytics link table always shows "Untitled" for editor-created links. These are wiring bugs, not design flaws — fixable with targeted edits.

Critical Issues (must fix)

1. Theme picker is built but never connected — users cannot change their theme

  • theme-picker.js is a fully implemented 14-theme + custom-picker component.
  • app.js never imports it. No route (editor, settings, dashboard) mounts it.
  • applyTheme() from theme-picker.js is never called anywhere in the app.
  • profile-page.js has its own separate 6-entry THEMES object (line 37-44: aurora, midnight, cotton, forest, paper, carbon) that does NOT match the 14 themes in theme-picker.js.
  • Result: users are permanently stuck on "aurora" (the seed default). The entire theme system step (step 8) exists in isolation.
  • Fix: import createThemePicker in the editor/settings route and mount it; replace the hardcoded THEMES map in profile-page.js with the canonical one from theme-picker.js.

2. scheduling block type added in editor but never rendered on profile page

  • block-editor.js BLOCK_TYPES (line 14) includes { type: 'scheduling', ... } with a full config panel (title + Calendly URL).
  • profile-page.js renderBlock() switch (lines 167-176) has no case for 'scheduling' — falls through to return ''.
  • Users can add a scheduling block via the editor, save it, navigate to their profile, and it silently doesn't appear.
  • Fix: add a case 'scheduling': to renderBlock() that renders a link-style card with the calendar URL.

3. Mobile sidebar has no toggle button — dashboard and editor are inaccessible on mobile

  • theme.css lines 399-403 define .sidebar { transform: translateX(-100%) } on screens <1024px and .sidebar.open { transform: translateX(0) }.
  • bindGlobalEvents() in app.js (lines 22-29) only binds the sign-out button. No code adds or removes the .open class.
  • AppShell HTML (layout.js:92-100) does not include a hamburger button.
  • Result: on any mobile or tablet screen, the sidebar is hidden and there is no way to navigate between dashboard, editor, and settings.
  • Fix: add a hamburger <button> to AppShell that toggles .open on #sidebar.

4. Analytics link performance table always shows "Untitled" for editor-created links

  • dashboard.js linkTableRows() at line 171 reads b.title || 'Untitled' to get the display name.
  • After block editor normalization (block-editor.js lines 336-353), all link metadata (title, URL, subtitle) moves into b.config.title — the top-level b.title field is not populated for normalized blocks.
  • Demo seed blocks in store.js (b1, b2) have flat title fields and display correctly. Any block created by a real user via the editor will show "Untitled" in the table.
  • Fix: change dashboard.js:171 to b.config?.title || b.title || 'Untitled'.

Warnings (should fix)

5. og:image references /assets/og-image.png which does not exist (index.html:13)
There is no assets/ directory in the project. OG share images will show a broken image across all social platforms. Either remove the tag or add a placeholder image.

6. --color-primary-light not defined in dark theme (theme.css:60-87)
The light theme defines --color-primary-light: #EEE9FF but the dark theme block omits it. Multiple components reference it for hover/selected states (sidebar active item, block editor modal hover, landing feature cards). In dark mode these will render as blank/transparent.

7. Landing, login, and signup pages do not use a <main> landmark
AppShell correctly wraps content in <main id="main-content"> (layout.js:96). But all three marketing/auth routes (renderLanding, renderLogin, renderSignup) inject raw HTML strings without a <main> wrapper. Screen readers and AT tools rely on <main> for skip-nav.

8. profile-page.js THEMES map is a 6-entry subset, not the canonical 14-theme system
Even after fixing critical issue #1, the profile renderer must be updated to use the same theme data source as the picker. Currently they are two separate static objects with different keys and values.

Minor (nice to have)

9. renderDemo() is dead code / unnecessary indirection (app.js:241-243)
The /demo-shortcut route calls renderDemo() which just calls navigate('/demo'), which triggers /:username with username='demo'. The function serves no purpose. The direct link href="#/demo" already works correctly via the username route.

10. Dashboard stat deltas are hardcoded strings (dashboard.js:210-213)
+12%, +8%, -2%, +10% are static. Fine for MVP, misleading at production scale.

11. Social proof counter animation runs on mount, not on scroll-into-view (landing.js:461-480)
The count-up fires immediately when the landing renders, not when the bar scrolls into the viewport. Most users will miss the animation.

12. window._chSignOut and window._chToggleDropdown pollute global scope (app.js:32-55)
These work but are fragile. If the DOM changes while the dropdown is open, the deferred close listener can fail silently. Scoped event delegation would be more robust.

Feature Coverage Checklist

Feature Status Evidence
Profile page (avatar, name, bio, social icons, link list) PASS profile-page.js — full implementation with SEO, analytics tracking
SEO meta tags (title, description, OG) PASS profile-page.js:213-221; OG in index.html:9-18 (og:image 404 is Warning #5)
Social links (platform icons, hover effects) PASS profile-page.js:180-195, all major platforms with branded SVGs
Embedded content (YouTube, Spotify, TikTok) PASS profile-page.js:108-157 — inline iframes + link fallback
Email capture block PASS email-capture.js wired into editor (block-editor.js:14) and profile renderer (profile-page.js:159,297)
Tip jar block PASS tip-jar.js wired into editor (block-editor.js:16) and profile renderer (profile-page.js:163,316)
Drag-and-drop block editor PASS block-editor.js — HTML5 drag events, reorder, add/delete, live preview
Scheduling link block type PARTIAL FAIL Block type in editor (block-editor.js:14) but not rendered on profile (profile-page.js switch missing case)
Analytics dashboard (views, clicks, CTR, referrers, time-series) PASS dashboard.js — canvas chart, referrer bars, sortable table, range picker
Analytics link click tracking PASS profile-page.js:331-337 — delegate listener on #profile-blocks fires analyticsStore.recordClick()
Landing page (hero, features, comparison, themes, testimonials, pricing, CTA) PASS landing.js — all 8 sections present and substantive
Auth / multi-tenant signup + login PASS auth.js — validation, reserved usernames, localStorage-backed sessions
Custom domain config UI PASS auth.js:200-210 — domain field in settings, CNAME instructions
Theme system (14 presets + custom picker) FAIL theme-picker.js fully built but never imported or mounted anywhere in the app
Mobile responsiveness PARTIAL FAIL CSS breakpoints exist; sidebar has no toggle JS — dashboard/editor inaccessible on mobile
Accessibility basics PARTIAL Email capture and tip jar have aria labels, sr-only, aria-live; main pages missing <main> landmark

Recommendation

NEEDS REVISION

Four targeted fixes required before shipping:

  1. Wire theme-picker.js into the editor/settings route and align profile-page.js THEMES map with the canonical 14-theme set.
  2. Add case 'scheduling': to profile-page.js renderBlock().
  3. Add hamburger button + toggle JS to AppShell.
  4. Fix dashboard.js:171 to read b.config?.title || b.title.

All other issues are warnings or minor polish. The underlying architecture is clean and the feature depth is genuinely competitive with the goal spec.