Deprecate the theme package

[mrosvik]

Our current theme package has fallen out of use and is no longer maintained. It has also largely been forgotten internally, and it is not used by the teams in Digdir that it was originally created for.

We should also question whether Designsystemet should own Digdir-specific themes at all. Maintaining organisation-specific themes does not align with our role or responsibilities and may create unclear ownership in the long term.

Points to discuss

• The package is currently unused by the intended teams at Digdir.
• Owning Digdir-specific themes does not naturally belong within Designsystemet’s scope or mandate.
• Continuing to support the package may not provide value relative to the effort required.

Proposed next steps

• Verify whether any external consumers still rely on the package.
• If not, define a deprecation plan and communicate it clearly.
• Clarify ownership of Digdir’s themes outside of Designsystemet.
• Remove the package from the repository once deprecation is completed.

[Barsnes]

We should still give a default theme, but this should come from @digdir/designsystemet-css under /theme

[Barsnes]

We have decided to deprecate this package, and move it elsewhere.
Searching "@digdir/designsystemet-theme": on github only shows a few results, and a lot of them are out of date versions, forks of this repo, test repos, or simply having it as a dependency but not using it.

[mimarz]

We just need to move the CSS variables build from the theme package to css package and this should be ok.

We also generate typings and tailwind from generated theme CSS variables which we need to find out how to expose.

Maybe something along the lines of;

• @digdir/designsystemet-css/theme
• @digdir/designsystemet-css/theme/types
• @digdir/designsystemet-css/theme/tailwind

We could probably already do this and just have these builds work in parallell to test things work properly before deprecation and removal.

[mimarz]

After closer inspection we need to have a discussion if we need want to remove the actual package or not, as there are points for keeping it.

In addition to hosting the other theme digdir themes, it also does the following;

1. Holds the configuration for Designsystemet default theme.
2. Creates and builds Designsystemet default design tokens (into css variables).
3. Invokes commanding for creating preview tokens used on the design tokens page in storefront; https://designsystemet.no/no/fundamentals/design-elements/variables

Point 3. could be brought up for discussion if we should move it elsewhere, but for now its lived here as its directly tied to the default theme which lives here.

Also if we move this logic to the css package, @digdir/designsystemet-types would become a dependency there. I would be nice for the css to have a default theme, but this also comes with other overhead so will have to evaluate the tradeoff here.

Based on this, I suggest for now we just remove the Digdir specific themes and keep this package as is with just the Designsystemet theme (and business logic related to it).

@digdir/designsystemet-theme would only include the theme files and config (design tokens still live under design-tokens)

Edit: We could also move the create, build and preview tokens logic somewhere else, where would need to be looked at, maybe in internal.