User Interface Overview
This section provides an overview of the application user interface (UI) of Sveltia CMS. It covers the main features and components of the UI, including navigation, content editing, asset management and customization options.

Accessing the Admin UI
The Sveltia CMS admin user interface is accessed by navigating to the URL where the index.html file in the static files folder is deployed. For example, if the site is deployed to https://example.com and Sveltia CMS is placed in the admin folder, it is available at https://example.com/admin/.
Main Components
Login Screen
The login screen allows users to authenticate with the configured backend using the regular OAuth flow or an access token. See each backend documentation for more details on authentication methods.
When working locally, the local workflow option is also available, allowing users to select a local folder for storing content.
Users can sign in using the OAuth flow even locally. The OAuth client should allow http://localhost as a valid redirect URI for this to work.
Navigation
The Sveltia CMS UI features a global navigation bar at the top of the screen, providing easy access to key sections of the application listed below. It also includes a user menu for account settings and preferences.
There is also the Quick Add button (+ icon) in the navigation bar, which allows users to quickly create a new entry or upload new assets from anywhere in the CMS.
Main Pages
The Sveltia CMS UI consists of several main pages:
- Content Library: Manage and organize content entries.
- Content Editor: Create and edit content entries.
- Asset Library: Manage and upload media assets.
- Editorial Workflow: Manage entries before they are published or deleted. This page only appears when the advanced workflow is enabled.
Account Menu
The account menu is accessible from the user avatar in the navigation bar. It provides access to:
- A link to the user’s profile page (if supported by the backend).
- A link to the live site. It points to the
display_urlorsite_urlconfiguration option value, in that order of precedence. - User Settings, including appearance, language, Content Editor preferences and Developer Mode.
- Keyboard shortcuts reference.
- Sign In with Mobile option, which shows a QR code for passwordless sign-in on mobile devices.
- Sign Out option to log out of the CMS.
Settings Dialog
Users can personalize the application with various settings, including appearance and language. Developer Mode can also be enabled in the Developer tab, which enables certain features and displays the CMS version number. When working with a local repository, the Developer tab also lets you turn on Git commits.
The Data Management tab has a Clear Data section:
- Clear File Cache deletes the locally cached file contents and image thumbnails.
- Erase All Data removes everything the CMS keeps in the user’s browser, including unsaved drafts, settings and the sign-in state.
Neither affects anything already saved to the repository.
General Features
Content editing in Sveltia CMS is designed to be intuitive and efficient. Key features include:
Themes
Users can switch between light and dark themes in the CMS interface. The theme setting is Automatic by default, meaning the CMS follows the system’s light or dark appearance and switches with it right away. Users can pick Dark or Light at any time in the application settings.
More appearance options may be added in future releases.
Localization
The CMS interface is available in various languages. The language setting is Automatic by default, meaning the CMS follows the language set in the browser — and switches as soon as it changes, without a page reload. Users can pick a specific language at any time in the application settings, and the CMS will remember the choice for future sessions.
Currently, the following languages are available:
- Arabic
- Bulgarian
- Catalan
- Chinese (China)
- Chinese (Taiwan)
- Croatian
- Czech
- Danish
- Dutch
- English (Canada)
- English (South Africa)
- English (UK)
- English (US)
- Finnish
- French
- German
- Greek
- Hebrew
- Hungarian
- Italian
- Japanese
- Korean
- Norwegian Bokmål
- Persian
- Polish
- Portuguese (Brazil)
- Portuguese (Portugal)
- Russian
- Slovak
- Spanish (Colombia)
- Spanish (Spain)
- Swedish
- Turkish
- Ukrainian
- Vietnamese
If a user has picked a specific language and the browser’s language later becomes available, the CMS will prompt the user to switch to it. The prompt doesn’t appear on the Automatic setting, which already follows the browser. If the user dismisses it, they can still change the language in the application settings.
Compatibility Note
The following languages are available in Decap CMS but not yet available in Sveltia CMS:
- Lithuanian
- Macedonian
- Norwegian Nynorsk
- Romanian
- Serbian (Cyrillic)
- Slovenian
- Thai
Unlike Netlify CMS and Decap CMS, Sveltia CMS does not require developers to configure the app UI locale. The CMS automatically detects and applies the user’s preferred language based on their browser settings. The CMS.registerLocale API method is a no-op and the locale configuration option is ignored in Sveltia CMS.
CSP Consideration
If the site uses a strict Content Security Policy (CSP), you may need to add the connect-src directive with the value https://unpkg.com to the CSP header. This allows the CMS to retrieve locale files for the admin interface other than English (US). See the Setting up Content Security Policy section for more details.
Localizers Wanted
Interested in contributing to Sveltia CMS localization? We welcome contributions from the community! Contributors can help translate the CMS interface into their language. Check out the localization guide for instructions on how to get started.
Keyboard Shortcuts
The following keyboard shortcuts are available in the Sveltia CMS UI:
- View the Content Library:
Alt+1 - View the Asset Library:
Alt+2 - Search for entries and assets:
Ctrl+F(Windows/Linux) orCommand+F(macOS) - Create a new entry:
Ctrl+E(Windows/Linux) orCommand+E(macOS)
Shortcuts are ignored while text is being composed with an input method editor (IME), so pressing Enter or Escape to confirm or cancel a conversion doesn’t trigger them.
On macOS, holding the Option key in a text field types a special character. So Alt shortcuts like Alt+1 don’t work while a text field has focus.
Mobile Support
The Sveltia CMS UI is fully responsive and optimized for mobile devices, providing a seamless experience across different screen sizes, including smartphones and tablets.
When a user opens the CMS for the first time on desktop, it shows a notification suggesting that they try it on mobile for the best experience, along with a QR code for passwordless sign-in. The user’s settings are automatically copied when they sign in via the QR code.
If the user dismisses the notification, the mobile login option will still be available in the user menu.
Installing as an App
Sveltia CMS is a progressive web app (PWA), which means users can install it on their device and use it like a native application. Offline support is not available yet, but it will be added in a future release.
The application logo and title can be customized with the logo and app_title configuration options. The default title is “Sveltia CMS”.
CSP Consideration
If the site uses a strict Content Security Policy (CSP), you may need to add the manifest-src directive with the value blob: to the CSP header. This allows the CMS to be installed as an app. See the Setting up Content Security Policy section for more details.
Developer Mode
Developer Mode can be enabled in the Developer tab of the Settings dialog. When enabled, it provides additional features useful for developers, such as:
- Displays the Help menu in the navigation bar, including a link to the release notes with the current CMS version number.
- Additional debugging information in the browser console.
- The browser’s native context menu.
Accessibility
Sveltia CMS is meant to be usable by everyone who edits content, however they work: with a keyboard, a screen reader, voice control, a touchscreen or a mouse.
We work toward WCAG 2.2 Level AA. This is our target, not a claim of conformance: we have conducted an automated self-audit, which can’t find every barrier, and we’ll continue to test and improve the application.
Our accessibility statement covers supported environments, known limitations and how we respond to reports. If you encounter any accessibility issues, please report them by creating an issue on our GitHub repository or by emailing [email protected].
Keyboard Navigation
- Navigate through UI elements using the Tab, Space, Enter and arrow keys.
- Keyboard shortcuts are also available for common actions.
- Mouse interactions, such as drag-and-drop, have keyboard alternatives.
- Our custom UI component library is built with keyboard use in mind.
Screen Reader Support
- The UI uses WAI-ARIA roles and labels to support screen readers like NVDA and VoiceOver.
- Announcements are read out when the user navigates to another page.
Rich Text Editor
- The rich text editor is built with Lexical, which follows accessibility best practices and includes Dragon NaturallySpeaking support.
Visual Design
- We aim for sufficient contrast between foreground text and background colors.
- Links are underlined by default for easy recognition (configurable in the Accessibility tab of the Settings dialog).
System Preferences
- The CMS honors the operating system’s reduced motion, reduced transparency and increased contrast settings.
Supported Browsers
Sveltia CMS works with all modern browsers. It relies on some recent JavaScript features, so the following versions or later are required:
- Chrome and Edge 140
- Firefox 133
- Safari 18.4
An older browser is detected when the CMS loads, and an error message asking the user to update the browser is shown instead of the sign-in page.
There are also a few limitations because Sveltia CMS utilizes some new web technologies:
- The local workflow requires a Chromium-based browser, including Chrome, Edge and Brave.
- Safari: The Test backend requires version 26 or later; image optimization is slower than in other browsers.
- Firefox Extended Support Release (ESR) and its derivatives, including Tor Browser and Mullvad Browser, are not officially supported, although they may still work.
Make sure to use the latest version of the browser for the best experience.