From c68d45e71ed6debf5977c2bc28d2fe6a8b3530b5 Mon Sep 17 00:00:00 2001 From: asmyshlyaev177 Date: Wed, 16 Oct 2024 22:33:06 +0400 Subject: [PATCH] fix: update sitemap and description --- .../example-nextjs14/src/app/components/Description.tsx | 4 ++-- packages/example-nextjs14/src/app/sitemap.ts | 6 ++++++ 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/packages/example-nextjs14/src/app/components/Description.tsx b/packages/example-nextjs14/src/app/components/Description.tsx index f33406f..594f95c 100644 --- a/packages/example-nextjs14/src/app/components/Description.tsx +++ b/packages/example-nextjs14/src/app/components/Description.tsx @@ -8,9 +8,9 @@ export const Description = () => (
-
Main goal is to provide state management with URI and good developer experience, there are many similar libraries, but non of them are easy enough to use.
+
Main goal is to provide state management with URI and good developer experience, there are many similar libraries, but non of them are easy enough to use, or lack functionality.

-
state-in-url provides useUrlState hook for Next.js/react-router. With it you can store state easily without a lot of boilerplate.
+
state-in-url provides useUrlState hook for Next.js/react-router. With it you can store state easily without a lot of boilerplate, and implement Deep Links pattern for your App.
No need to wrap components in a provider, can share data between unrelated client components. API is very similar to React.useState.

diff --git a/packages/example-nextjs14/src/app/sitemap.ts b/packages/example-nextjs14/src/app/sitemap.ts index e7311c3..4fddb60 100644 --- a/packages/example-nextjs14/src/app/sitemap.ts +++ b/packages/example-nextjs14/src/app/sitemap.ts @@ -10,5 +10,11 @@ export default function sitemap(): MetadataRoute.Sitemap { changeFrequency: 'weekly', priority: 1, }, + { + url: `${siteUrl}/react-router`, + lastModified: new Date(), + changeFrequency: 'weekly', + priority: 1, + }, ]; }