> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mindli.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Building Your Boxes
> How to structure Boxes so your thinking stays organized as it grows
export const MndIcon = ({icon, size = 20, color, circle = false}) => {
const iconUrl = `https://app.mindli.com/api/icon/${icon}`;
const [isDarkMode, setIsDarkMode] = React.useState(false);
React.useEffect(() => {
const checkTheme = () => {
const darkClass = document.documentElement.classList.contains('dark');
const darkAttr = document.documentElement.getAttribute('data-theme') === 'dark';
setIsDarkMode(darkClass || darkAttr);
};
checkTheme();
const observer = new MutationObserver(checkTheme);
observer.observe(document.documentElement, {
attributes: true,
attributeFilter: ['class', 'data-theme']
});
return () => observer.disconnect();
}, []);
let finalColor = color;
if (!color) {
finalColor = isDarkMode ? '#FFFFFF' : '#333333';
}
const iconElement = ;
if (!circle) {
return
{iconElement}
;
}
const circleSize = Math.max(size + 6, 20);
return
{iconElement}
;
};
## Overview
A Box is not just a folder. It's a thinking space — a container with its own Sparks, Sub-Boxes, AI insights, and structure.
Getting Box design right makes the difference between a system you return to and one you abandon.
***
## Name with Intent
A good Box name tells you at a glance what belongs inside — and what doesn't.
* Prefer specific over generic: **"Trip to Greece — May 2026"** beats **"Travel"**
* Include a time anchor when relevant: **"Q3 Planning"**, **"Book — July Read"**
* Avoid single-word names unless the scope is truly that narrow
Duplicate Box names are allowed but not recommended — they create confusion when searching or assigning Sparks.
***
## Use Sub-Boxes to Add Depth
When a Box grows beyond 20–30 Sparks, or when it contains clearly separate topics, split it with Sub-Boxes.
A well-structured nesting example for a freelance designer:
```
Work
├── Client — Acme Corp
│ ├── Briefs
│ ├── Feedback
│ └── Deliverables
├── Client — Bloom Studio
│ ├── Briefs
│ └── Deliverables
└── Admin
├── Invoices
└── Contracts
```
Each leaf Box stays focused. The parent Boxes give you a quick overview without drowning in Sparks.
***
## A Practical Day-to-Day Setup
Here's a simple structure that works for most people:
```
Inbox ← all new Sparks land here
Now ← what you're actively working on this week
Projects ← one Sub-Box per project
Learning ← articles, books, courses
Ideas ← raw thoughts not yet tied to a project
Archive ← completed work, kept for reference
```
The key habit: once a week, open Inbox and move Sparks into the right Box. Keeps everything clean without requiring real-time organization.
***
## Connect a Spark to Multiple Boxes
A Spark doesn't have to live in just one Box. Connect it to every Box where it's relevant.
For example, a research article about pricing strategy could belong to both **"Client — Acme Corp"** and **"Learning"**.
Tap ** Boxes** on any Spark to add or remove Box connections. You can also let AI suggest Boxes for you.
***
## Keep Home Clean with Star and Archive
* **Star** your most active Boxes to keep them prominent on Home
* **Archive** Boxes you're done with — they stay searchable but disappear from your main view
* Use ** Filter** on Home to switch between active and archived views when you need to reference old work
***
## AI Works Better with Good Box Structure
The more focused a Box is, the better AI Create performs when generating insights across it.
A tightly scoped Box like **"Client — Acme Corp > Feedback"** will produce sharper summaries and more actionable output than a broad catch-all Box.