Color
This page documents the real color foundation currently available in the project. It starts with the imported palette tokens, continues with the named project colors, and then shows the first semantic layer that components should consume.
The preview always follows the active project palette. If the page body switches to another brand class such as palette-mavihost, the same UI Kit page automatically updates to that palette without changing the component markup.
Palette Scale (raw color ramps)
These are the imported ramp-based tokens that currently exist in the project. They are part of the foundation layer and are useful for reference, but components should gradually move to semantic tokens instead of consuming these steps directly.
Brand
Imported project ramp
Gray
Imported project ramp
Info
Imported project ramp
Success
Imported project ramp
Danger
Imported project ramp
Attention
Imported project ramp
Named Project Colors (project-specific foundation tokens)
These colors already exist in the project outside the ramp-based groups. They are useful for product-specific accents and should remain visible in the UI Kit because they are part of the actual token set.
Overlay Tokens (alpha foundation)
These tokens are useful for overlays, subtle layers, and transparent treatments. The values automatically invert between light and dark contexts because they are part of the imported runtime token set.
Semantic Colors (usage layer)
This is the first semantic layer currently implemented in the project. New components should consume this layer instead of referencing raw palette steps directly.
Light Mode
Semantic preview against the default light context
Radius
This page documents the current radius scale as it is consumed through Tailwind's native rounded utilities. The visual layout uses fixed pixel spacing for presentation only, while the preview boxes focus on the actual project radius tokens.
Radius is now consumed with the standard Tailwind API, such as rounded-md and rounded-2xl. The runtime tokens still control the real design values, so the same class automatically follows the project scale.
Rounded Utilities (Tailwind native API)
Each preview below uses the real project radius through Tailwind's standard rounded-* classes. The surrounding layout intentionally uses fixed pixel spacing so the presentation stays clean and does not depend on the spacing scale preview.
Spacing Scale
Typography
Chips
Search Boxes
Reusable UI-only search field with internal search/close icons. The component is fluid, direction-aware, and receives its width from the parent container.
States
All states are shown with the 40px size. Icons follow the document direction automatically.
Sizes
Only the base/default state is repeated here to show the height difference.
Compact Link Cards
Compact clickable cards for quick resource links. The component itself is fluid; the parent container controls width.
Docs Cards
Documentation cards with title, description, and a link action row. The card is fluid and receives its width from the parent grid/container.
Quick Link Cards
Compact inline link cards for short navigation items. The component is content-sized, includes an optional icon, a divider, and title text.
FAQ Items
Single FAQ accordion items with default, hover, and open states. The item is fluid and receives its width from the parent container.
Admonitions
Content callout boxes for documentation pages. Each variant uses the real admonition part and can render an optional title, default icon, and HTML-capable content.
Related Links
Documentation helper block for related references. The wrapper is not clickable; links are rendered inside the HTML-capable content area.
Tabs
Tabs component used for switching between related content sections within the same context.
Supports semantic structure with tablist, tab, and tabpanel roles,
and can be controlled via JavaScript API for dynamic interactions.
Documentation Tabs
Main visual test for active border, tab padding, and panel switching.
Console tab content.
CLI tab content.
Github tab content.
Overflow Tabs
Checks horizontal overflow while keeping the active border aligned with the nav border.
Overview item content.
Requirements item content.
Install item content.
Configure item content.
Deploy item content.
Troubleshooting item content.
Legacy Markup Compatibility
Verifies tab-anchor, activeTab, and tab-panel markup uses the same visual states.
Legacy first panel content.
Legacy second panel content.
Legacy third panel content.
Docs Content
Default typography showcase for documentation body content. This section renders the real docs content wrapper and tests native HTML tags such as headings and paragraphs.
Docs Content Typography
This showcase is used to test the default typography rules inside the documentation content wrapper.
Headings and Paragraphs
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer non magna vitae justo gravida luctus.
Heading H3 Example
Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
Heading H4 Example
Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Heading H5 Example
Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
Heading H6 Example
Code Block
This example demonstrates the documentation code block shell. The code highlighting itself is handled by the editor/highlighter integration.
npm install
npm run build
npm run preview Curabitur pretium tincidunt lacus. Nulla gravida orci a odio, and nullam varius turpis et commodo pharetra.
Inline Elements
This is a simple paragraph demonstrating common inline elements used in documentation. You can follow this
link example to explore more details. Some parts of the text are bold or
italic, and occasionally underlined for emphasis. Inline code such as npm install
may appear within sentences, alongside highlighted text for important notes. You might also see
smaller text used for less critical information, or content that has been removed
and updated. In some cases, values like H2O or x2 are displayed using subscript
and superscript. For keyboard inputs, combinations like Ctrl + C are shown clearly.
Ordered List / Step List
This example demonstrates how ordered lists are styled inside the documentation content. Content editors only need to use a standard ordered list, and the numbering style, circular markers, and connecting vertical line will be applied automatically by docs-content.
- Log in to your account using your email and password.
- Click on the "Create Service" button and select your desired plan.
- Configure your resources such as CPU, RAM, and storage based on your requirements.
-
Enable additional features like SSL and backup options if needed.
- Activate SSL from the security settings.
- Set up a backup schedule to protect your data.
- Review your configuration and confirm the order to deploy the service.
Curabitur pretium tincidunt lacus. Nulla gravida orci a odio, and nullam varius turpis et commodo pharetra.
Unordered List
This example demonstrates the default unordered list style inside documentation content.
- Choose the product category that matches your workload.
-
Review the available regions and select the closest location.
- Check latency for the primary user location.
-
Compare nearby fallback regions.
- Keep the fallback region in the same legal zone if needed.
- Check optional features such as backups, monitoring, and security settings.
- Save the configuration after reviewing the final summary.
Table
This example demonstrates the default table style inside documentation content.
| پلن | پردازنده | رم | فضای ذخیرهسازی | کاربرد پیشنهادی |
|---|---|---|---|---|
| شروع | ۲ vCPU | ۴ GB | ۸۰ GB SSD | وبسایتهای کوچک و مستندات سبک. |
| تجاری | ۴ vCPU | ۸ GB | ۱۶۰ GB SSD | سرویسهای درحال رشد با ترافیک منظم. |
| پیشرفته | ۸ vCPU | ۱۶ GB | ۳۲۰ GB SSD | اپلیکیشنهای پرترافیک و بارهای کاری سنگینتر. |