I too struggled with this issue and I guess I found out the answers for myself. I am going to share my findings here in the hope that it will help other newcomers to ArchiCAD.
The Navigator is split up into three sections: Project Map, View Map and Layout Book.
The
Project Map contains a hierarchical list of
Viewpoints. A viewpoint is a particular point of view of the 3D model and its 2D annotations. Think of each viewpoint as a slice through the 3D model (horizontal slices for plans and vertical slices for sections and elevations) that shows you a 2D projection of the 3D model. Viewpoints are where you actually model and draw.
In summary a
viewpoint is
what you draw.
The
View Map contains a hierarchical list of
saved view points, simply referred to as views. Views are the way that you tell the story of your building. You'll show structure in some views and not others, furniture on one and fire separations on another, etc. You accomplish this by setting various attributes of the view, such as scale, layer combinations, model view options, graphical overrides, to achieve a particular graphical representation of your overall model. While you can continue drawing/modeling over the top of a view the actual 3D and 2D items you add are attached to/stored on the parent viewpoint, or at least that's how I think of it. Sometimes it is helpful to continue drawing on top of a particular view and sometimes it is not. The system is very flexible and powerful.
In summary a
view is
how you see what you've drawn.
The
Layout Book is a hierarchical list of
Layouts, i.e. drawing sheets. This is the most straight forward item in the navigator to understand - it's a book of drawings arranged into logical sections.
Another thing that I really struggled with initially was ArchiCAD's concept of "layers". I found the word "layer" to be misleading because in my mind layering implies a hierarchical ordering of items. In every other application I have used, which also has the notion of layers, the ordering is obvious and explicit. For example, layers in Photoshop or InDesign behave just the way that one might expect: upper layers cover lower layers.
Generally, ArchiCAD's layer mechanism does not imply any ordering or hierarchy at all (this is not entirely true as there are subtle and advanced interactions between layers when it comes to how elements merge/intersect). I find that ArchiCAD's layers are best thought of as "sets". In that sense ArchiCAD's layers are a mechanism for grouping elements that logically belong together. By analogy, a set of all people over the age of 25 does not imply anything about the sex, ethnicity or profession of any of the members of the set. There is also no ordering or hierarchy. It's just a set. And so in ArchiCAD you might have a layer for all walls that are structural. There is no implication as to the makeup of these walls, their colour, fire rating, height, level or any other attributes. It's just a set of walls that share a particular function and you get to decide on the logic that governs the grouping. In this respect ArchiCAD's layers are not all that dissimilar from how Revit's worksets behave.
There are many interesting articles on how to best use layers and layer combinations. I highly recommend that you find these and read them thoroughly.
All the best on your ArchiCAD journey.
Pushing the boundaries of local time/space continuum since 1972.
Archicad 26 | iMac (Retina 5K, 27-inch, 2017) | 4.2 GHz Quad-Core Intel Core i7 | 24 GB | Radeon Pro 580 8 GB | macOS 12.6