Migrate HelpScout docs to a Knapsack workspace (dog fooding!)

Adobe Experience Manager integration

Workspaces would have only latest & draft. Users would work on a shared draft and then publish to latest.

Easily create new Blocks, Pages, & Patterns using Templated Content

Create Design Tokens that reference & modify other tokens by performing operations such as darken/lighten on colors, multiply/divide on dimensions, and more. Helpful with color palettes and spacing scales.

Search will now find content on within pages & will prioritize results in a helpful way.

Changes to Design Tokens would result in CSS Vars being injected into Component demos – allowing live theming changes by cloud users

Pages with tabbed sections, similar to our Pattern pages

Increase ease of editing Pattern demos with AI, including ability to easily compose bigger experiences using nested components.

Customers could write React code to make a custom block unique to their workspace

Adding ability to use Cmd+K to open quick actions and search content

Digital Asset Management for brand assets such as logos, stock photography, fonts, and more.

Add links to other pages of your workspace easily in Blocks

https://tr.designtokens.org/format/#typography

We already have the ground work laid in settings. We just need to adjust the UX/UI and remove the feature flag.

Would also be great if one could drag between slots (i.e. drag from header to footer) – see Productlane feedback

Setup Knapsack in minutes yourself

Basic stats about the design system packages used in Knapsack workspace

Dedicated page for managing Branches, allowing more control & insight along with batch changes

Control access to specific sections & pages instead of whole workspace

Having the ability to share system status information across the entire site allows us to communicate important news, notify users about feature announcements, product updates, policy changes, or even collect customer feedback.

Ability to add a collection of prominent & nice looking links for things like Jira/Linear Tickets, GitHub repos, internal wikis, etc

A block that references a markdown file in the repo - editing can happen either in file or in Knapsack UI

Components that have JSDoc will have that content shown in Knapsack on it's Pattern Template page

Work better with multiple design systems & Knapsack Workspaces

Showcase animations using transition design tokens

Smoother creation of branches & publishing

Building upon Template Suggestions, a new top level page where all Patterns can be managed and easily bulk imported

Knapsack branches when proposed will show CI status to ensure that appropriate safety checks can be made - especially valuable for design token changes which may have downstream consequences.