Organization themes

When your organization publishes its themes on the portal, the extension fetches them, checks them and installs them once for all of VS Code: any presentation, whatever its folder (or outside any folder), can use them with theme: Name.

Signing in

1. Run DWA : se connecter au portail (sign in to the portal) and enter the portal address (suggested by the dwa.hub.portal setting).
2. The browser opens; VS Code displays a code.
3. Sign in on the portal (code received by email, or SSO), compare the code with the one in VS Code, then authorize.

A single sign-in per portal is enough: it gives access to the themes of all your organizations, with no extra step. The token is encrypted by VS Code (the system's secret storage) and reused; it never appears in a URL and the portal keeps only its SHA-256 fingerprint. Several portals are supported. In WSL, sign-in goes through the browser and HTTPS polling, with no local callback.

Choosing a theme

DWA : choisir un thème d’organisation (choose an organization theme) lists the themes of all your organizations. Picking one:

• downloads the version and checks the organization, name, version and SHA-256 fingerprint of the CSS;
• runs the theme validator and reports any errors;
• installs the theme in the extension's global storage: one active version per theme, shared across all of VS Code;
• writes theme: Name (and marp: true) into the frontmatter of the open presentation, without touching other keys.

No file is written into your projects for the theme: no more .dwa-theme.json or .dwa/themes/.

How Marp finds themes

Marp for VS Code only accepts URLs or paths inside the open folder. So the extension serves installed themes at http://127.0.0.1:<port>/dwa-themes/… (only requests to 127.0.0.1 are accepted) and declares these URLs in your user settingsmarkdown.marp.themes, keeping your other entries. If a project declares its own Marp themes (which hides the user list), the URLs are added there. Several VS Code windows share the same server. DWA features (overflow, callouts, PPTX) read the installed file directly.

Unobtrusive updates

When you open a presentation that uses an installed theme (at most once per hour and per theme), the extension compares the installed fingerprint with that of the latest published version. If it differs, a notification offers:

• Mettre à jour (Update): installs the new version (with a warning on a major version change);
• Ne plus afficher (Don't show again): no more notifications for this theme.

Nothing is updated without your consent. DWA : vérifier les mises à jour des thèmes (check for theme updates) checks all installed themes on demand.

The dwa.themes.updateNotifications setting defaults to notify; silent turns off all theme notifications, with the status still visible in the status bar.

Withdrawn versions, deleted themes, lost access

Situation	What the extension offers
Version withdrawn by the organization	Switch to the latest published version
Theme deleted	Use the replacement theme, if the organization designated one
Access revoked	Message; no new version possible
Portal unreachable	Nothing: retry later

In every case, the installed copy remains usable.

Status bar

The status bar shows the presentation's theme and version, any Core v1 errors and an available update. Clicking it opens the actions: update, check, validate the theme, open the portal (DWA : état du thème de la présentation (presentation theme status)).

Validation of every theme used

Every theme used, from the portal or local, goes through the same validator as the portal (steps 1 to 4, without a browser): results in Problems, on the CSS file with the line number, and in the status bar. DWA : contrôler le thème (Core v1) (validate the theme) reruns the check; a CSS file declaring @dwa-language is rechecked on every save.

Signing out

DWA : se déconnecter du portail (sign out of the portal) revokes the remote session, then erases the local secret. A session can also be revoked from the portal (Account settings). Installed themes remain usable offline.

Offline and revocation

Copies already installed remain usable offline, even after a revocation or a server-side withdrawal. The portal controls new downloads; it does not delete files remotely. Permissions are a distribution control, not a copy-protection mechanism.

Your presentations are never sent to the portal.