Skip to content
umlimator
Main Navigation GuideAPIExamples
Changelog
npm
Releases

Appearance

Sidebar Navigation

Examples

All examples

Maps

Map

UML structure

Class

Object

Package

Composite structure

Component

Deployment

Profile

UML behaviour

Use case

Activity

State machine

Sequence

Communication

Interaction overview

Timing

Information flow

SysML

Requirement

Block definition

Internal block

Parametric

Architecture, data and process

C4

Entity-relationship

Data flow

Flowchart

BPMN

Mindmap

Cloud architecture

AWS

Google Cloud

Azure

Atlas

The Umlimator Atlas

The Bookshop Atlas

The Umlimator Atlas ​

Umlimator's own model, drawn with umlimator: its parts and who uses each (a map), its system context and containers (C4), the core module's packages in build order (a package diagram), the typed diagram families (a component diagram), the diff Action on a pull request (a sequence diagram) and umlimator's state machines (navigation, the story player, tours, the page's keys and the MCP page), joined by cards that open them.

Open full screen (The Umlimator Atlas)A pull request, from push to comment (The Umlimator Atlas)An assistant, then the reader (The Umlimator Atlas)PDF (The Umlimator Atlas)Model (The Umlimator Atlas)

Its views ​

Umlimator

Map

The atlas's root: umlimator's parts and who uses each, the Python parts in a box, line kinds (feeds, state, triggers) and weights, two cards whose views a host may load when opened, and a story along a pull request.

umlimator: system context

C4

The system context: the author and the reader as people, umlimator as the system, the AI assistant, GitHub and Chrome as external systems.

umlimator: containers

C4

The containers inside umlimator's dashed boundary, each with its technology, and the relationships the context implies.

The module's packages, in build order

Package

The core module's packages in src/, in the order tools/build.mjs concatenates them into lib/umlimator.js.

umlimator/all: the typed families

Component

The typed families as components, each depending on the core's registry, which the typed canvas looks up.

The diff Action on a pull request

Sequence

The diff Action on a pull request: an async start, calls and their replies, a self-call, and an alt frame on whether the token can write.

umlimator's state machines

Map

How umlimator's machines relate: the page and the MCP page drive render()'s handle, a box holding the story player, navigation and tours, which report every change to MapState.

Navigation

Map

Navigation's states, a move at a time, with its loops back and run order numbered.

Story player

Map

The story player's states, from entering a step to ended or stopped.

Tour and replay

Map

A tour's or a replay's states: riding, held, at the end or cut short.

The page's keys

Map

The order the page's keys close its layers in, as boxes of states.

The MCP page

Map

A page tool, step by step, from the assistant's call to the answer once a page has shown it.

Edit this page on GitHub
Pager
Previous pageAzure
Next pageThe Bookshop Atlas