Getting Started

The Antumo Design System ships as two packages with different delivery pipelines. Pick the one that matches your stack.

Package	Registry	Consumers	Docs
@antumo/design	npm (Azure Artifacts)	Angular + PrimeNG, vanilla HTML	CSS + JS
Antumo.Blazor	NuGet (Azure Artifacts)	Blazor, ASP.NET	Blazor / .NET

Both deliver the same design tokens, the same component styling, and the same dark mode — only the packaging differs.

Registry access

Both feeds are hosted on the private m2tcorp Azure Artifacts organization. You need access to that organization to install either package.

npm

Add to your project's .npmrc:

@antumo:registry=https://pkgs.dev.azure.com/m2tcorp/_packaging/antumo/npm/registry/

npm install @antumo/design

NuGet

Add the feed, then install:

dotnet nuget add source https://pkgs.dev.azure.com/m2tcorp/_packaging/antumo/nuget/v3/index.json \
  --name antumo

dotnet add package Antumo.Blazor

The one rule that matters

Use standard Bootstrap 5 class names. The DS styles them the Antumo way. You almost never write custom CSS.

<button class="btn btn-primary">Save</button>
<table class="table table-striped">…</table>
<input class="form-control" type="email">

Components without a Bootstrap 5 equivalent use the .antumo-* prefix (e.g. .antumo-steps). For anything the DS doesn't cover, write app-specific CSS — but always use DS tokens (var(--antumo-*)), never hardcoded colors or spacing.

Next steps

• CSS + JS setup — Angular + PrimeNG, vanilla HTML, the JS API
• Blazor / .NET setup — NuGet, <AntumoIcon>, Razor components
• Dark mode — one attribute, both themes
• Design tokens — the CSS variable reference
• Components — all 39, with live examples
• Figma ↔ CSS map — how we verify design fidelity