It is usual to have a top file for each project.
This file typically has some info about the project and annotated virtual fold
links to the source files which make up the project.
Accordingly, I have a file be.top, which looks like this when
inside the editor.
If you move down to the str.C virtual fold, and enter it
(using F3 or ^L ^I in the default key bindings),
then the source file looks like this.
This file is the implementation of a string class in C++. Notice that each method or group of methods is in its own fold. Moving down to the first assignment operator fold, and entering this.
If instead, we had entered the virtual fold leading to str.h,
we would have seen this.
Note the way the classes private internal details are hidden
from immediate view.
If from within be.top, you had entered the virtual fold to
be.htm, you would have seen.
This demonstrates that the concept of folding can apply to things other than code, such as documentation.
Other candidates for folding can include, functions, groups of functions,
cases in a switch statement, the body of an
if, do or while, large comments etc..
Screen shots taken of AE on Linux.