Release history

Every release moves the editor closer to a real publishing workflow.

DevFrame evolves around a practical loop: edit in Studio, manage structured content in Builder, publish to `/p/[slug]`, and keep template changes from damaging the underlying portfolio record.

Open Studio View roadmap

DevFrame system map

The same App Router shell powers marketing, Studio, Builder, Dashboard, and public portfolio routes.

Current focus

v0.5.x

Persistence and asset safety

Templates

Nova, Vertex, Drift

Publishing

/p/[slug]

Public portfolio output

Fallback

Preview cookie

Usable without Supabase

v0.5.0

Upload fixes, asset lifecycle cleanup, and single-record persistence

Moved image uploads away from large Server Action bodies, tightened Supabase Storage asset handling, and reinforced the single portfolio record rule.

Profile and gallery images upload directly to Supabase Storage before save actions receive URL/path metadata.

Template-agnostic assets are preserved across Nova, Vertex, and Drift switches.

Saving updates the owner's current portfolio instead of creating duplicate portfolio rows.

v0.4.0

Studio live editing and public portfolio publishing

Introduced the desktop-first Studio surface with a central live preview and a public `/p/[slug]` output route.

Studio became the flagship live editing workspace.

Builder stayed available as the structured form editor and mobile fallback.

Published portfolios render through the shared template registry and portfolio renderer.

v0.3.0

Template registry with Nova, Vertex, and Drift

Standardized template discovery, preview data, and dynamic settings so templates stay decoupled from the renderer.

Nova focuses on minimal editorial presentation.

Vertex uses a high-density bento layout with profile and gallery assets.

Drift provides a split, leadership-oriented portfolio layout.

v0.2.0

Custom Clerk auth and onboarding flow

Replaced stock auth overlays with custom DevFrame-styled sign-in, sign-up, OAuth, and callback surfaces.

Clerk remains the session infrastructure while the UI stays custom.

Authenticated users can publish to Supabase when persistence is configured.

Demo mode keeps the app usable when auth credentials are absent.

v0.1.0

Initial DevFrame foundation

Laid down the Next.js App Router shell, dark-first design system, portfolio schema, and public rendering path.

Marketing pages, shared UI primitives, and App Router route groups.

Supabase schema for portfolios, projects, experience, sections, and assets.

Cookie-backed preview fallback for local and unconfigured environments.