fix: update core docs

Author: boazpoolman

packages/docs/docs/api/graphql.md

@@ -10,6 +10,3 @@ slug: /api/graphql
 
 As of writing this page there is no GraphQL API exposed by the Webtools core plugin. You might be able to still get most of its functionality by querying the native Strapi GraphQL API, but this is not officially supported at this time.
 
-## Status
-
-GraphQL support for Webtools core is not available yet. If you want this feature to happen, please get involved on GitHub. Webtools is a rapidly growing plugin suite for Strapi and community feedback is always appreciated.

packages/docs/docs/getting-started/installation.md

@@ -10,21 +10,11 @@ slug: /
 Complete installation requirements are the exact same as for Strapi itself and can be found in the Strapi documentation.
 
 **Additional Requirements:**
-- **Node.js**: Version 18.17 or higher
+- **Node.js**: Version 18 or higher
 - **Strapi**: Version 5.x
 
-:::tip Node Version Manager
-Create a `.nvmrc` file with `18.17` for consistent versions across your team:
-```bash
-echo "18.17" > .nvmrc
-nvm use
-```
 :::
 
-### Supported versions
-
-- Strapi v5
-
 ### Installation
 
 To install the plugin run the following command in your Strapi project directory. This invokes the core Webtools CLI (webtools-cli).

packages/docs/docs/getting-started/troubleshooting.md

@@ -12,13 +12,13 @@ Common issues and solutions when working with Strapi Webtools.
 
 ### Node.js version error
 ```
-The engine "node" is incompatible with this module. Expected version ">=18.17"
+The engine "node" is incompatible with this module. Expected version ">=18"
 ```
 
-**Solution:** Update Node.js to version 18.17 or higher:
+**Solution:** Update Node.js to version 18 or higher:
 ```bash
-nvm install 18.17
-nvm use 18.17
+nvm install 18
+nvm use 18
 ```
 
 ### Peer dependency warnings
@@ -28,6 +28,11 @@ Multiple warnings about unmet peer dependencies during installation.
 
 ## Pattern & URL Issues
 
+### URL is incorrect
+The Webtools plugin applies it's own slugify function to your URLs. That means that if you have already have a slugified field, which you then use in an URL pattern, it will be slugified again, potentially causing incorrect URLs. If you want you can disable the slugify function of Webtools by updating the slugify configuration.
+
+See [slugify configuration docs](/configuration/slugify)
+
 ### Can't select field in pattern
 When creating URL patterns, some content types don't show field options.
 

packages/docs/docs/getting-started/usage.md

@@ -62,10 +62,3 @@ After enabling Webtools for your content types:
 Type `[` in the pattern field to see available fields from your content type.
 :::
 
-## Sitemap setup
-
-For setting up and generating your XML sitemap, see Addons > Sitemap:
-- Getting Started and Settings: /addons/sitemap/getting-started/introduction and /addons/sitemap/settings/introduction
-- CLI usage: /addons/sitemap/cli
-
-This keeps sitemap-specific steps within the Addons documentation.

packages/docs/docs/getting-started/use-cases.md

@@ -24,9 +24,8 @@ const sidebars = {
       items: [
         "getting-started/installation",
         "getting-started/usage",
-        "getting-started/url-alias",
         "getting-started/url-pattern",
-        "getting-started/use-cases",
+        "getting-started/url-alias",
         "getting-started/permissions",
         "getting-started/troubleshooting",
       ],