Skip to content

feat(design): new workspaces start on the portal design engine - #845

Closed
mortondev wants to merge 2 commits into
feat/portal-design-v2-phase3-attachmentsfrom
feat/portal-design-v2-phase3-release
Closed

mortondev wants to merge 2 commits into
feat/portal-design-v2-phase3-attachmentsfrom
feat/portal-design-v2-phase3-release

Conversation

@mortondev

@mortondev mortondev commented Oct 31, 2026 •

Copy link
Copy Markdown
Member

The twelfth of the stack that builds a new design engine for the portal, and the last of phase 3. New workspaces start on the design engine.

A workspace created now has portalDesignV2 on, so its portal renders through the design document and Settings › Portal opens on Appearance. Existing workspaces keep their theme until someone turns the engine on in Labs; nothing changes for them on upgrade. The plan makes it the default for everyone one release later.

Kept as its own PR so it can be held back while the rest of the stack lands.

Verification

The flag tests now check that the default stays off and that new workspaces start with it on. The settings and onboarding suites pass.

A workspace created now has portalDesignV2 on, so its portal renders through
the design document and Settings › Portal opens on Appearance. Existing
workspaces keep their theme until someone turns the engine on in Labs.
@mortondev
mortondev added this pull request to stack #833 October 31, 2026 00:00
@mortondev

Copy link
Copy Markdown
Member Author

Condensed into #878. The stack is now five PRs, #878 to #882; this branch is kept as it was.

@mortondev mortondev closed this Nov 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant