← Back

Infinite Levels

← Back to all docs

Infinite Levels

Master multi-level diagrams by drilling down into nodes to create hierarchical architecture documentation

basicsbeginner⏱️5 min
Home/Documentation/Infinite Levels

Master multi-level diagrams by drilling down into nodes to create hierarchical architecture documentation

Infinite Levels & Multi-Level Diagrams

One of ArkT's most powerful features is the ability to create infinite levels of detail. You can drill into any node to see what's inside it, creating a hierarchical architecture diagram with unlimited nesting.

The Power of Hierarchy

🚀 Think of it like folders: Just as you can organize files in nested folders, you can organize your architecture in nested diagrams within nodes!

Key Capabilities

Drill Down

Alt/Option click any node to see its internal components

Breadcrumb Navigation

Navigate back up using breadcrumb trail

Unlimited Nesting

Create as many levels as needed for your architecture

Context Preservation

Maintain context across all diagram levels

Core Concepts

What is Node Drilling?

Node drilling allows you to create hierarchical diagrams by "zooming into" nodes to see their internal structure. Each node can contain its own complete diagram with nodes and edges.

The Zoom Analogy

Think of it like zooming:

  • 🌍 Top level: High-level architecture overview (e.g., "Frontend", "Backend", "Database")
  • 🔍 Drill down: Detailed view inside a component (e.g., inside "Backend" you see "API Gateway", "Auth Service", "User Service")
  • 🔬 Multiple levels: Go as deep as needed for complete documentation

Each node can contain its own complete diagram with nodes and edges!

What happens when you drill down into a node?

The node gets deleted
You see a new canvas inside that node
The node changes color
Nothing happens

Multi-Level Use Cases

System Architecture

•

Top Level

Major systems (Frontend, Backend, Database, External APIs)

•

Level 2

Services within each system (Auth Service, User Service, Payment Service)

•

Level 3

Internal modules within services (Controllers, Models, Utilities)

Microservices Architecture

•

Top Level

Service mesh overview (API Gateway, Services, Databases, Message Queues)

•

Level 2

Individual microservices (User Service, Order Service, Notification Service)

•

Level 3

Service internals (Endpoints, Business Logic, Data Access Layer)

Cloud Infrastructure

•

Top Level

Cloud regions and availability zones

•

Level 2

VPCs, subnets, and network boundaries

•

Level 3

Individual resources (EC2 instances, Lambda functions, S3 buckets)

✨ Best Practice

Progressive Disclosure: Multi-level diagrams let you show high-level architecture first, then drill down to reveal details only when needed. This keeps diagrams clean and understandable!

How many levels of nesting does ArkT support?

Only 2 levels
Maximum 5 levels
Up to 10 levels
Unlimited levels
Step-by-Step Guides

Drilling Down into Nodes

How to Drill Down

•

Alt/Option click on any node

•

The canvas transitions to show the inside of that node

•

Create nodes and edges inside just like the top level

•

Breadcrumbs appear at the top showing your current path

⌨️ Keyboard Shortcut

Mac users: Hold Option and click
Windows/Linux users: Hold Alt and click
Quick tip: You'll see the cursor change when hovering over a node with Alt/Option held!

What Happens When You Drill

New Canvas

You enter a new "canvas" inside that node

Empty by Default

This new canvas starts empty (unless you've added content before)

Full Functionality

You can create nodes, edges, and even drill down further

Context Preserved

The parent context is preserved - you can always navigate back

Navigating with Breadcrumbs

Breadcrumbs show your current location in the diagram hierarchy and provide quick navigation between levels.

Understanding Breadcrumbs

🗺️ Breadcrumb Example

Example breadcrumb trail:
Root > Backend Service > Auth Module

This shows you're currently viewing the "Auth Module" inside "Backend Service" at the root level.

How to Navigate

Click "Root"

Return to the top level of your diagram

Click Any Breadcrumb

Jump directly to that level in the hierarchy

Navigate Intermediate Levels

Click any level between root and current

💡 Quick Navigation

Navigation tips:

  • Breadcrumbs appear automatically when you drill down
  • Current level is highlighted in the breadcrumb trail
  • Use breadcrumbs for quick jumps across multiple levels
  • You don't need to go back one level at a time!

How do you navigate back to the root level?

Press Escape key
Click "Root" in breadcrumbs
Alt/Option click on empty space
Refresh the page

Organizing Multi-Level Diagrams

📐 Hierarchy Planning

Planning Your Hierarchy:

🌍 Top Level: High-level architecture overview

  • Show major systems and boundaries
  • Keep it simple (5-10 nodes)
  • Focus on main components

🔍 Middle Levels: Subsystem details

  • Break down each major component
  • Show internal structure
  • Reveal key relationships

🔬 Deep Levels: Implementation details

  • Document specific modules or classes
  • Add technical specifications
  • Show fine-grained architecture

Best Practices

Start broad, go deep progressively - don't skip levels

Each level should be understandable on its own

Use consistent naming across levels for clarity

Don't create unnecessary depth (2-4 levels is usually sufficient)

Keep each level focused - 5-10 nodes per level is ideal

Document what each level represents in node descriptions

⚠️ Keep It Simple

Avoid Over-Nesting: While ArkT supports unlimited levels, too many levels can make navigation confusing. Most architectures are well-served by 2-4 levels of depth.

What is the recommended number of levels for most architectures?

Always 1 level
2-4 levels
5-10 levels
As many as possible
Reference Material

Best Practices

Keep top-level diagrams simple with 5-10 major components

Use meaningful node names that make sense in hierarchical context

Create 2-4 levels of depth for most architectures

Each level should tell a complete story on its own

Use breadcrumbs to quickly navigate between levels

Document what each level represents in node descriptions

Common Use Cases

Breaking down monolithic applications into microservices view

Documenting cloud infrastructure at multiple detail levels

Creating progressive disclosure documentation

Mapping organizational structure with team details

Designing layered software architectures

Documenting nested data structures and schemas

UI Elements

Interface Guide

Alt/Option Click

On any node - Drill down into the node to see its internal diagram

Breadcrumbs

Top of canvas - Shows current location in diagram hierarchy. Click any breadcrumb to navigate to that level.

Root Breadcrumb

First item in breadcrumb trail - Always available. Click to return to top level.

Continue Learning

Multi-Level Master! 🎯

You now understand how to create hierarchical architecture diagrams with infinite levels of detail!

🎉 Congratulations!

What you've mastered: ✅ How to drill down into nodes (Alt/Option click) ✅ How to create internal components at each level ✅ How to navigate using breadcrumbs ✅ How to organize hierarchical architecture ✅ Best practices for multi-level diagrams

Pro tips to remember:

  • Keep top levels simple (5-10 nodes)
  • Go 2-4 levels deep for most architectures
  • Use breadcrumbs for quick navigation
  • Each level should tell its own story
5 of 10

Related Articles

Templates

Create reusable node templates for consistency

featuresintermediate
7 min

Create Your First Node

Master the basics of node creation in ArkT diagrams

basicsbeginner
5 min

Edge Connections

Learn how to connect nodes with directional edges

basicsbeginner
7 min

On This Page

IntroductionUnderstanding Multi-Level DiagramsWorking with Multi-Level DiagramsQuick ReferenceNext Steps