When you organize notes, the first question is often: where does this one go?
If the tool offers many folder levels, the question keeps going: under Work, or under a specific project? Should you split by year too? If the place later feels wrong, do you rename—or move a whole group?
Those choices aren’t worthless. But when a classification system needs constant naming, moving, and upkeep, organizing itself starts to consume the energy that was meant for writing. Especially when you don’t have much content yet and real relationships haven’t shown up, designing a full directory tree too early is often just guessing at the future.
That’s why Abox Note uses “single-layer spaces + nested tags”: a space only answers “roughly where does this belong,” and finer sorting goes to tags.
Pick a broad bucket, then start writing
You can create multiple spaces in Abox Note, but spaces themselves don’t nest. Use a space for Work vs. Life, or give an independent project its own space. It only needs to give you a clear enough broad range—it doesn’t have to describe a note’s full address.
In practice, enter the right space and start capturing. Add tags when you need further organization. Tags support tree nesting—for example work/project/ideas. Selecting a tag in the sidebar filters matching notes.
This doesn’t remove hierarchy. It changes where and when hierarchy shows up: catch content with one layer of space first; express finer structure with tags when classification is actually useful. You don’t have to decide a long path before you write—and when content changes, you don’t have to keep rearranging a whole folder tree.
Why keep spaces at all?
If tags can nest, why not put every note in one pile and use only tags?
Because some boundaries need to stay stable. Work material and personal records may not belong in the same list; a set of notes you plan to export or publish also needs an easy-to-understand scope. Abox Note currently lets you manage and filter notes by space, and you can use a space as the publish scope for a static site.
So spaces and tags aren’t two redundant classifiers:
- Spaces are for a few stable, broad buckets;
- Tags are for finer categories that keep growing.
That split keeps necessary order and gives classification a stopping point. The tool no longer invites you by default to create yet another nested space.
Limits are a product choice too
Letting spaces nest forever would feel freer. It would also hand the “do I need another level?” decision back to every organizing session. Abox Note limits space depth to reduce the ongoing burden of maintaining containers—not because folders have no value.
Tags don’t need to go deeper and deeper either. If a tag tree also needs frequent renaming and moving, the old organizing burden just moved houses. Single-layer spaces can reduce default complexity; they can’t automatically invent order for everyone. The practical pattern is usually: keep spaces few and stable, and grow tags only when you really need them.
When it isn’t a fit
Single-layer spaces aren’t right for every kind of material.
If your work must map strictly to company departments, clients, years, and project phases—or external programs depend on fixed multi-level file paths—a tool with nested folders will fit better. If you already have a mature, stable directory convention that barely needs upkeep, there’s no reason to flatten it for the sake of “flat.”
Abox Note is aimed at a different need: notes keep growing and changing, and people want to write first, then gradually see which categories are worth keeping long term. For that way of capturing, structure doesn’t have to be finished before the first sentence. Set a broad bucket, start writing; other relationships can wait.