Notice: This page requires JavaScript to function properly.
Please enable JavaScript in your browser settings or update your browser.
Learn Optimizing Navigation in Next.js | Building Pages and Layouts in Next.js
Next.js 14 Mastery for Building Modern Web Apps

bookOptimizing Navigation in Next.js

Now that we've got all the required pages, let's explore how users can move around them. Traditionally, we might employ the default HTML <a> tag. However, the issue with this approach is that it triggers a full page reload, impacting the user experience.

Next.js proposes using the <Link> component, enabling us to facilitate client-side navigation.

Note
Note

For further details on client-side navigation, check out the documentation at:Β  docs

Alternatively, we can continue working on the project. You can trust that using theΒ LinkΒ component is a better approach, and we can see its practical implementation in the project.

Back to the Project

To implement the client-side navigation, access app/ui/dashboard/nav-links.tsx, import the Link component from next/link, and substitute the <a> tag with <Link>.

Upon saving your changes, test your localhost to enable seamless page navigation without refreshing the page.

In Practice

Everything was clear?

How can we improve it?

Thanks for your feedback!

SectionΒ 3. ChapterΒ 4

Ask AI

expand

Ask AI

ChatGPT

Ask anything or try one of the suggested questions to begin our chat

Suggested prompts:

Can you explain how the Link component improves navigation compared to the <a> tag?

What else can I customize when using the Next.js Link component?

Are there any best practices for using client-side navigation in Next.js?

Awesome!

Completion rate improved to 2.08

bookOptimizing Navigation in Next.js

Swipe to show menu

Now that we've got all the required pages, let's explore how users can move around them. Traditionally, we might employ the default HTML <a> tag. However, the issue with this approach is that it triggers a full page reload, impacting the user experience.

Next.js proposes using the <Link> component, enabling us to facilitate client-side navigation.

Note
Note

For further details on client-side navigation, check out the documentation at:Β  docs

Alternatively, we can continue working on the project. You can trust that using theΒ LinkΒ component is a better approach, and we can see its practical implementation in the project.

Back to the Project

To implement the client-side navigation, access app/ui/dashboard/nav-links.tsx, import the Link component from next/link, and substitute the <a> tag with <Link>.

Upon saving your changes, test your localhost to enable seamless page navigation without refreshing the page.

In Practice

Everything was clear?

How can we improve it?

Thanks for your feedback!

SectionΒ 3. ChapterΒ 4
some-alt