> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nuwacom.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Creating Design systems

Creating a Design system opens a chat beside its page. The page fills with the elements gathered during the conversation. Each creation chat builds one Design system. A website, brand files or a description in chat can provide the starting point.

1. Open *Design systems*.
2. Create a new Design system.
3. Select *Your website* or *Brand files* as the starting point.
4. Enter the website address or provide a presentation, template, PDF or Word file.
5. Review the overview, colors, typography, logos, graphics and files in the editor.

A Design system can also start without a website or file. In that case, the builder asks for basic information about the brand in chat. Logos, graphics and font files can be added separately.

## Reviewing Design System

After nuwacom processes the supplied sources, the Design system is organized into six tabs:

* *Overview*: A summary of the Design system and its design guidance.
* *Colors*: The captured color palette.
* *Typography*: The captured text styles.
* *Logos*: Brand logos.
* *Graphics*: Other visual assets.
* *Files*: Files added as sources.

To check the result, select the Design system in chat and create a representative output, such as a landing page or presentation. Compare its appearance with the brand materials.

## Call a Design System

A Design system can be selected on the chat start page or through *@ > Design systems*. If exactly one Design system is available in the workspace, nuwacom applies it automatically.

If several are available and none has been selected, nuwacom asks which one to use. It does not combine two Design systems.

The toggle on an individual Design system enables or disables its automatic use in a person’s own chats. A disabled Design system remains available for manual selection.

## Supported sources and limits

The following file formats and sources are supported when creating a Design system:

**Documents**

* **PowerPoint:** .pptx, .potx
* **Word:** .docx, .dotx
* **PDF:** .pdf (first 30 pages)
* **File size limit:** 50 MB per file

**Websites**

* Must be publicly accessible via HTTPS
* Maximum review time: 45 seconds per website

**Images**

* .svg, .png, .jpg, .jpeg, .webp, .gif

**Fonts**

* .woff, .woff2, .ttf, .otf

**Design System Limits**

* **Colors:** Up to 12
* **Type styles:** Up to 24
* **Sources:** Up to 50

***

## FAQ

**What happens if a website cannot be read?**

Only public HTTPS pages can be reviewed. If a site blocks automated access or takes too long to load, a supported brand file can be used instead. An unsuccessful review does not change the Design system.

**Can a Design System be created without brand files or a website?**

Yes. A description in chat provides the starting point. The builder asks for basic brand details and builds the Design system from the answers. Its elements can then be refined on the page or in chat.

**Which fonts are retrieved automatically?**

Freely available, license-free fonts, including suitable web fonts, are retrieved automatically.

**Which fonts must be uploaded?**

Fonts that require a license must be uploaded separately as font files.

**What does the label *Font is missing* mean, and how is it resolved?**

A font defined in the design system is not available to the system. This applies to licensed fonts without an uploaded font file and to fonts that cannot be retrieved automatically.

To resolve it:

1. Open *Design systems* and select the affected design system.
2. Open the *Typography* tab.
3. Upload the font file for the font marked *Font is missing*.

Once the file is uploaded, the font is available for documents, slides and apps created with this design system.

***


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.