[jelmore]

At first, I had a bunch of heirarchially-organized contexts under various major headers:

@Home
-> @Chores
-> @Improvement
@Office
-> @Wiki
-> @External KB
-> @Testing
-> @Training
-> @Mail
@Email
-> @Home Email
-> @Office Email
@Phone
-> @Home Phone
-> @Office Phone
@Roaming
-> @Groceries
-> @Shopping
@Waiting For
@Computer
-> @Home Computer
-> @Office Computer

But it wasn't working for me, because I didn't find myself using the subcategories much. I mean, I'm unlikely to say "I feel like doing wiki stuff" right now.

So I moved much of my taxonomy to the Projects side; now all of my Office projects are broken down into folders for topics (Training, Wiki, External KB) and my contexts were simplified as a result.

So now I have:

@Home
@Office
@Computer
-> @Office Computer
-> @Home Computer
-> @Email
@Phone
@Roaming
-> @Groceries
-> @Shopping
@Agenda
-> @(sub-contexts for the significant people in my life)
@Waiting For
-> @Delegated

@Home, @Office and @Phone should be self-explanatory. @Computer is subcategorized, as there are certain tasks I can only do in a given location (installing software, backups) so those need to be called out. I use Gmail as my main home account, so @Email covers both locales.

@Roaming is a catch-all for stuff that can't be done at home or at work; @Groceries is a sub-context so I can print out a quick grocery list for myself or my wife, as is @Shopping.

Each major contact in my life gets a sub-context under @Agenda; one-offs just go directly under @Agenda.

@Waiting For is self-explanatory, with @Delegated as a sub-context that I keep "follow up with person foo on item bar"-type stuff.

The idea behind my current nestings is that I want to be able to work off of the main contexts whenever possible, with subcontexts used sparingly to filter out items that are not applicable. If I'm going to go talk to my supervisor Paul, I can glance at @Agenda > @Paul. If I'm at home, I will look at @Computer for tasks, zooming in to @Home Computer as needed.