| Data Access API Call | CellService.getCellChildren | Retrieves the children for a given cell. |
| Data Access API Call | CellService.getNavigation | Retrieves the navigation for the given cell. Returns a hierarchy of cells starting at the root of the navigation hierarchy of the cell you've specified and ending with the specified cell's children. |
When you retrieved your cell content in
step 2 of this guide, you had the choice of three different "flavors" of retrieved content. The
CellService.getCellWithChildren call comes with its own navigation component; however, if you wish you can build a more integrated navigation structure.
When you enabled users to add pages in
step 6 of this guide, you had the option to pass a parent cell with that interface. If you've implemented parent cells, your users may begin to build out complex navigation heirarchies off of your cells. A navigation through this heirarchy provides two benefits: your users will be able to get to these pages from your site and search engines will be able to crawl your site and find these new pages.
Two Navigation Calls

There are two navigation calls within the CellService.
getCellChildren
The first simply retrieves the children of the current cell. This is useful if you want to list child pages somewhere on your page other than with the getCellWithChildren response, or formatted differently than the option presented there.
getNavigation
The second returns a complete heirarchy of cells, starting with the top-most, or "root," cell, including siblings at every level down to the current cell, and then including that cell's children. This call allows you to create a more dynamic interface than the first call.
There is no API call to retrieve the entire navigation. For performance reasons, the getNavigation API call returns only the information required to show relevant navigation for that one cell.Next Step 8: Implement Templates