feat: remove next-sitemap and use the native Next.js sitemap/robots.txt

.env

@@ -3,6 +3,10 @@
 # For security reason, don't push secret key in your git repo.
 # Append .local to the environement files to prevent your secret key from being commited to Git.
 
+# Hosting
+# Replace by your domain name
+NEXT_PUBLIC_APP_URL=https://example.com
+
 # Database
 # Please use a working DATABASE_URL. Otherwise, Next.js build will timeout and you will get the following error: "because it took more than 60 seconds"
 # DATABASE_URL=libsql://[RANDOM-CHARS]-[DB-NAME]-[ORG-NAME].turso.io

.gitignore

@@ -23,11 +23,6 @@ storybook-static
 /.next
 /out
 
-# next-sitemap
-public/robots.txt
-public/sitemap.xml
-public/sitemap-*.xml
-
 # cache
 .swc/
 

README.md

@@ -136,7 +136,7 @@ Developer experience first, extremely flexible code structure and only keep what
 - 💡 Absolute Imports using `@` prefix
 - 🗂 VSCode configuration: Debug, Settings, Tasks and Extensions
 - 🤖 SEO metadata, JSON-LD and Open Graph tags
-- 🗺️ Sitemap.xml and robots.txt with next-sitemap
+- 🗺️ Sitemap.xml and robots.txt
 - ⌘ Database exploration with Drizzle Studio and CLI migration tool with Drizzle Kit
 - ⚙️ [Bundler Analyzer](https://www.npmjs.com/package/@next/bundle-analyzer)
 - 🌈 Include a FREE minimalist theme
@@ -270,7 +270,6 @@ You can easily configure Next js Boilerplate by making a search in the whole pro
 - `src/utils/AppConfig.ts`: configuration file
 - `src/templates/BaseTemplate.tsx`: default theme
 - `next.config.mjs`: Next.js configuration
-- `next-sitemap.config.js`: sitemap configuration
 - `.env`: default environment variables
 
 You have access to the whole code source if you need further customization. The provided code is only example for you to start your project. The sky is the limit 🚀.