This type of navigator would be similar to what we usually have in any documentation website. In Expo docs, for example, where each subheading has a link associated to it and clicking it generates a new sub-link in the URL.
This would basically be a combination of Stack routers in a Scroll View. The props would be inherently the same as other navigators and the initial route name may or may not be the first heading of the page. Having an attribute which states whether each screen should take up the full height of the page and has paging-Enabled set to true can be useful for apps which are not documentation hubs. Animations can also appear fluid based on the scroll offsets of the View.