---
title: "Pablo Bernal (@bernalmurcia) | Hashnode"
description: "Pablo Bernal (@bernalmurcia) writes on Hashnode. Read their latest articles and follow their work."
url: "https://hashnode.com/@bernalmurcia"
---

@bernalmurcia

# Pablo Bernal

@bernalmurcia · Joined January 2021

## Comments

[I'm still confused about how the state is stored across navigations. I'd think either you don't perform a full navigation or you store state in local/session storage. Which is it when using Context API on the app component? Is the Context API somehow using local storage under the hood, abstracted from us, or does this only work when using NextJS as CSR and not when using SSG? Edit: I understand now! The key is that even for SSG Nextjs actually performs a client-side navigation when using the Link component, instead of a full page refresh, as they mention in the docs for routing: https://nextjs.org/docs/routing/introduction "The Next.js router allows you to do client-side route transitions between pages, similar to a single-page application. A React component called Link is provided to do this client-side route transition."](https://hashnode.com/posts/using-react-context-api-with-nextjs/5f9f3de9de85d46a77d5ebe3/comment/6005a6ab7b30c23b714ab5ff#reply-6005d5e1848f4c3b9a0f1d57)

Reply · Article · Jan 18, 2021 · [Using React Context API with NextJS](https://hashnode.com/posts/using-react-context-api-with-nextjs/5f9f3de9de85d46a77d5ebe3)