{"version":"1","document":{"id":"front-base-js-navigation-and-recovery","product":"front-base-js","product_name":"FrontBaseJS","title":"Navigation, state and recovery","version":"2026-10-30","url":"\/developers\/front-base-js","content":"Enhanced navigation should preserve the behaviors people expect from a website: useful links, browser history and a recoverable path when a request fails.","body":["The KoniKode Knowledge Base uses the FrontBaseJS HTTP client to request bounded document data. It validates the response before replacing article content, cancels superseded requests and retains sidebar state while the reading pane changes.","Native document URLs remain the source of navigation. A successful client transition updates browser history; Back and Forward select the corresponding document. A failed or invalid enhanced response falls back to loading the server-rendered page.","Keep private data out of compiled public views and service-worker caches. A browser-side state store is not an authorization boundary. Product integrations should follow the pinned runtime contract and verify behavior with JavaScript unavailable."],"points":["Start with normal URLs and meaningful server HTML","Preserve history, focus and understandable loading feedback","Recover through native navigation when enhancement cannot complete"],"api_url":"\/api\/knowledge\/front-base-js-navigation-and-recovery"}}