{"path":"/guide/reading/navigation-and-loading","content":{"title":"Navigation and loading","summary":"Use the title bar, keep your place between pages, and understand the loading placeholders.","breadcrumbs":"[All topics](/guide) / [About Everything](/topics/about-everything) / [Finding and reading](/guide/reading)","body":"The title bar stays available while you move around Everything. **Home** and the Everything logo lead to [the topic index](/guide). The [About Everything](/topics/about-everything) topic is the entry point for the documentation guide. **About** currently opens [How Everything works](/guide/how-it-works). These are configured links to ordinary content pages. **Search** opens the built-in [Search page](/search); **Explore** opens [Browse](/browse). Search and Browse are application views rather than stored wiki pages.\n\n## What loads when\n\nFirst you receive the site header, navigation and a skeleton placeholder. The article is fetched separately and replaces the skeleton when ready. Related search results then load in their own request when the panel approaches the visible area. You can start reading without waiting for those results.\n\nOn wide screens, the guide has a main reading column and a related-reading sidebar. On smaller screens, the sidebar moves below the article. The template also supplies curated **Guide links**, which are separate from the search-generated cards.\n\nOrdinary internal links and search forms update the main content while retaining the shell. The address bar and browser Back/Forward still work. External links, downloads, JSON/media links and opening a link in a new tab keep their ordinary browser behavior.\n\n## Slow or failed requests\n\nA skeleton means the content request is still running, not that a copy is already available. A first visit can still be slow because application or storage dependencies need to start. [Caching](/guide/how-it-works/caching) helps repeated reads but does not guarantee a fast response.\n\nIf an article fails, the navigation stays available and a **Try again** button lets you retry deliberately. If related results fail, you can still read the article and use Search. The browser does not poll, prefetch the entire guide or automatically retry failures.\n\nWith JavaScript disabled, use the offered server-rendered link. Adding `?view=server` to a page URL also requests that fallback; it can wait for synchronous rendering and optional related work. [Web, JSON and MCP](/guide/reading/interfaces) explains the other interfaces.","navigation":"[About Everything](/topics/about-everything) · Section: [Finding and reading](/guide/reading) · Next: [Search and browse](/guide/reading/search)","related":[{"title":"Caching and freshness","url":"/guide/how-it-works/caching"},{"title":"Check your MCP connection","url":"/guide/getting-started/connect-agent/first-steps"}]}}