Subsequent Loads

if the user follows a link inside a Perseus app to another page within that same app, the Sycamore router will catch it and prevent the browser from requesting the new file from the server. The following will then occur (for an /about page rendered simply):

Sycamore router calls Perseus inferred router logic.
Perseus inferred router determines from new URL that template about should be used, returns to Sycamore router.
Sycamore router passes that to closure in perseus-cli-builder shell, which executes core app shell.
App shell checks if an initial load declaration global variable is present and finds none, hence it will proceed with the subsequent load system.
App shell fetches page data from /.perseus/page/<locale>/about?template_name=about (if the app isn't using i18n, <locale> will verbatim be xx-XX).
Server checks to ensure that locale is supported.
Server renders page using internal systems (in this case that will just return the static HTML file from .perseus/dist/static/).
Server renders document <head>.
Server returns JSON of HTML snippet (not complete file), stringified properties, and head.
App shell deserializes page data into state and HTML snippet.
App shell interpolates HTML snippet directly into __perseus_content_rx (which Sycamore router controls), user can now see new page.
App shell interpolates new document <head>.
App shell initializes translator if the app is using i18n.
App shell hydrates content at __perseus_content_rx, page is now interactive.

The two files integral to this process are page_data.rs and shell.rs.