dnb.no valid

Eufemia documentation

DNB's Eufemia design system. This file points LLMs to machine-readable docs and clean Markdown copies.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-26T03:31:49.348Z. Cached copy · Source on dnb.no

# Eufemia documentation

> DNB's Eufemia design system. This file points LLMs to machine-readable docs and clean Markdown copies.

## Version

This documentation reflects Eufemia **v0.0.0-development**, generated 2026-10-23T12:32:48.356Z.

- Use the documentation exactly as provided.
- Gather all required information from the documentation before using it as a reference.
- Do not make assumptions or infer missing details unless explicitly instructed to do so.

## Quick Reference

- [Eufemia quick reference](https://eufemia.dnb.no/uilib/usage/first-steps/quick-reference.md): A compact, practical guide with setup, components, forms, and key conventions.

## Machine-readable docs

Every Eufemia documentation page — including components, Forms fields, values, and related entities — includes machine-readable Markdown copies with JSON blocks that describe its public API.

Each page is both:

- a standalone documentation page, and
- an addressable API surface with structured JSON blocks.

The JSON blocks may include:

- props (properties, types, defaults, descriptions).
- events.
- relationships to other pages or components.
- links to related documentation pages.
- a docs entry that leads to the markdown file, which includes additional information, demos and examples.

The docs links are referenced from each page's frontmatter and are intended for tooling and AI-assisted usage, without relying on prose.

### Finding component API details

For any page (component, field, value, etc.):

- Open the page markdown (e.g. `/uilib/components/<name>.md`).
- Look at the demos and examples how to use the component.
- Read the JSON blocks in the markdown to get the API (props, events, translations).

## General

- [EufemiaChangelog](https://eufemia.dnb.no/EUFEMIA_CHANGELOG.md): Look into the documentation for more details.

- [Brand](https://eufemia.dnb.no/brand.md): Brand guidelines - typography, colors, etc.

- [Company logos](https://eufemia.dnb.no/collections/logos.md): Find company logos maintained by Eufemia.

- [Collections](https://eufemia.dnb.no/collections.md): Additional assets for DNB interfaces.

- [Contact](https://eufemia.dnb.no/contribute/contact.md): Look into the documentation for more details.

- [Icons Library](https://eufemia.dnb.no/contribute/deploy/icons.md): Look into the documentation for more details.

- [Design tokens (WIP)](https://eufemia.dnb.no/contribute/deploy/tokens.md): Look into the documentation for more details.

- [Deployment](https://eufemia.dnb.no/contribute/deploy.md): Look into the documentation for more details.
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=dnb.no · GET /v1/domain/dnb.no · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for dnb.no:
1. POST https://agentwebmap.com/v1/sites/dnb.no/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://dnb.no/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/dnb.no/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/dnb.no).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.