Front / back stage
Front / back stage

Information hierarchy follows a front stage for the workflow and a back stage for the setup.

Information hierarchy follows a front stage for the workflow and a back stage for the setup.

Use Sections and Folders to organize the different functions and areas of the app. Below is an illustration of a common pattern that we see in the docs; namely, there's a front stage and a back stage of the information hierarchy 👇

⁠

⁠

Makers often include the following components:

⁠

Welcoming⁠

to introduce the doc to users and stakeholders.

Adding a new thing as called out

Views⁠

for a User

Functional views folder as called out

Views⁠

for Stakeholders

Hidden Back End Folder: You can

hide⁠

this supporting section / folder. For example, some docs contain a "Raw Data" folder with sections storing base tables, or an "Admin" folder with lists that support lookup columns in other tables. Often this data rarely changes, or isn't as useful unless it's filtered. In these cases, you can hide those sections so the supporting data is out of the way and is less likely to be accidentally edited or deleted.

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.

Front / back stageFront / back stage

Front / back stage
Front / back stage