Roadmap

The next DevFrame work is about making publishing feel production-grade.

The roadmap keeps the existing architecture intact: Next.js App Router, custom Clerk auth, Supabase persistence, Studio, Builder, Dashboard, and the template registry all stay focused on one portfolio record.

Suggest a feature Report an issue

DevFrame system map

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

Planned

Templates

More layouts and community paths

Planned

Imports

GitHub and project data

Planned

Domains

Custom public portfolio routes

Planned

Analytics

Portfolio view insights

Templates

More portfolio templates

Expand beyond Nova, Vertex, and Drift while keeping every template on the same shared schema and registry.

New templates should register through `src/templates/registry.ts` and `src/lib/template-catalog.ts`.

Template-specific settings belong in `template_settings`, not separate tables.

Community templates should ship with realistic seed data and preview coverage.

Studio

Better live editing experience

Polish Studio into a faster desktop-first editor with clearer section navigation, safer save states, and stronger preview controls.

Improve section focus, preview scaling, and template setting controls.

Keep Builder as the structured/mobile editor instead of overloading Studio with dense forms.

Prevent local draft state from overwriting published Supabase records.

Import

GitHub and project import support

Help developers turn GitHub profile data, repositories, and project metadata into editable portfolio content.

Import candidate projects into the existing recent projects array.

Let users review summaries before publishing.

Avoid hard dependencies so demo mode and local setup still work.

Publishing

Custom domains and analytics

Add production publishing tools around the existing `/p/[slug]` route.

Custom domain mapping with ownership verification.

Portfolio view analytics that respect privacy and avoid noisy tracking.

Dashboard status cards for routes, updates, templates, and asset counts.

Community

Template marketplace or community templates

Create a contribution path for polished community layouts without fragmenting the renderer or database schema.

Template review checklist for accessibility, responsive behavior, and data coverage.

Catalog metadata for ideal use cases, highlights, and preview thumbnails.

No per-template database tables or renderer special cases.

Open source

Improved contribution workflow

Make it easier to report bugs, reproduce issues, and submit focused pull requests.

Issue templates for Studio, Builder, templates, auth, Supabase, and uploads.

Contributor docs for local demo mode and full Clerk/Supabase setup.

More examples for adding templates and validating public routes.