fixed links that came in from last master merge

Author: RicoSaupe

docs/recipes/build/add-build-script.md

@@ -3,7 +3,7 @@
 ## FAKE
 [Fake](https://fake.build/) is a DSL for build tasks that is modular, extensible and easy to start with. Fake allows you to easily build, bundle, deploy your app and more by executing a single command.
 
-> The standard template comes [with a FAKE project](../../../template-safe-commands) by default, so **this recipe only applies to the minimal template**.
+> The standard template comes [with a FAKE project](../../template-safe-commands.md) by default, so **this recipe only applies to the minimal template**.
 
 ---
 #### 1. Create a build project

docs/recipes/build/bundle-app.md

@@ -1,6 +1,6 @@
 # How do I bundle my SAFE application?
 
-When developing your SAFE application, the local runtime experience uses Vite to run the client and redirect API calls to the server on a [different port](../../../faq-build). However, when you *deploy* your application, you'll need to run your Saturn server which will serve up statically-built client resources (HTML, JavaScript, CSS etc.).
+When developing your SAFE application, the local runtime experience uses Vite to run the client and redirect API calls to the server on a [different port](../../faq/faq-build.md). However, when you *deploy* your application, you'll need to run your Saturn server which will serve up statically-built client resources (HTML, JavaScript, CSS etc.).
 
 #### 1. Run the FAKE script
 If you created your SAFE app using the recommended defaults, your application already has a FAKE script which will do the bundling for you. You can create a bundle using the following command:
@@ -11,7 +11,7 @@ dotnet run Bundle
 
 This will build and package up both the client and server and place them into the `/deploy` folder at the root of the repository.
 
-> See [here](../../../template-safe-commands) for more details on this build target.
+> See [here](../../template-safe-commands.md) for more details on this build target.
 
 ## Testing the bundle
 1. Navigate to the `deploy` folder at the root of your repository.
@@ -21,4 +21,4 @@ This will build and package up both the client and server and place them into th
 You should now see your SAFE application.
 
 ## Further reading
-See [this article](/docs/faq-build) for more information on architectural concerns regarding the move from dev to production and bundling SAFE Stack applications.
+See [this article](../../faq/faq-build.md) for more information on architectural concerns regarding the move from dev to production and bundling SAFE Stack applications.

docs/recipes/build/remove-fake.md

@@ -1,5 +1,5 @@
 # How do I remove the use of FAKE?
-[FAKE](https://fake.build/) is a tool for build automation. The standard SAFE template comes with a [ready-made build project](../../../template-safe-commands) at the root of the solution that provides support for many common SAFE tasks.
+[FAKE](https://fake.build/) is a tool for build automation. The standard SAFE template comes with a [ready-made build project](../../template-safe-commands.md) at the root of the solution that provides support for many common SAFE tasks.
 
 If you would prefer not to use FAKE, you can of course simply ignore it, but this recipes shows how to completely remove it from your repository. It is important to note that having removed FAKE, you will have to follow a more manual approach to each of these processes. This recipe will only include instructions on how to run the application after removing FAKE.
 
@@ -36,6 +36,6 @@ dotnet fable watch -o output -s --run npx vite
 The app will now be running at `http://localhost:8080/`. Navigate to this address in a browser to see your app running.
 
 ## Bundling the App
-See [this guide](../build/bundle-app.md#2-im-using-the-minimal-template) to learn how to package a SAFE application for deployment to e.g. Azure.
+See [this guide](bundle-app.md#2-im-using-the-minimal-template) to learn how to package a SAFE application for deployment to e.g. Azure.
 
 ---

docs/recipes/javascript/third-party-react-package.md

@@ -57,7 +57,7 @@ reactSpeedometer [
 
 ## Feliz - Setup
 
-If you don't already have [Feliz](https://www.nuget.org/packages/Feliz/) installed, [add it to your client](../../v4-recipes/ui/add-feliz.md).
+If you don't already have [Feliz](https://www.nuget.org/packages/Feliz/) installed, [add it to your client](../ui/add-feliz.md).
 In the Client projects `Index.fs` add the following snippets
 
 ```fsharp

docs/recipes/package-management/add-nuget-package-to-client.md

@@ -1,5 +1,5 @@
 # How do I add a NuGet package to the Client?
-Adding packages to the Client project is a very [similar process to the Server](../add-nuget-package-to-server), with a few key differences:
+Adding packages to the Client project is a very [similar process to the Server](add-nuget-package-to-server.md), with a few key differences:
 
 - Any references to the `Server` directory should be `Client`
 

docs/recipes/ui/cdn-to-npm.md

@@ -9,11 +9,11 @@ Remove the CDN reference from the index template in `src/Client/index.html`:
 ```
 
 #### 2. Add the NPM Package
-Add styles from NPM. [How do I add an NPM package to the client?](../../package-management/add-npm-package-to-client)  
+Add styles from NPM. [How do I add an NPM package to the client?](../package-management/add-npm-package-to-client.md)
 In this example we will add the [Bulma NPM package](https://www.npmjs.com/package/bulma).
 
 #### 3. Add a reference to your stylesheet
-1. Add a stylesheet to your project using [this recipe](../add-style). Add a scss file instead of a css file.
+1. Add a stylesheet to your project using [this recipe](add-style.md). Add a scss file instead of a css file.
 1. Add the following lines to your scss file:
     ```scss
     // Set variables to affect Bulma styles

docs/v4-recipes/javascript/third-party-react-package.md

@@ -57,7 +57,7 @@ reactSpeedometer [
 
 ## Feliz - Setup
 
-If you don't already have [Feliz](https://www.nuget.org/packages/Feliz/) installed, [add it to your client](../ui/add-feliz.md).
+If you don't already have [Feliz](https://www.nuget.org/packages/Feliz/) installed, [add it to your client](../../recipes/ui/add-feliz.md).
 In the Client projects `Index.fs` add the following snippets
 
 ```fsharp

mkdocs.yml

@@ -65,9 +65,6 @@ nav:
     - Server Side Rendering : "features/feature-ssr.md"
     - Hot Module Replacement : "features/feature-hmr.md"
     - Working with Azure functions : "features/feature-azurefunctions.md"
-  - Server Side Rendering : "feature-ssr.md"
-  - Hot Module Replacement : "feature-hmr.md"
-  - Working with Azure functions : "feature-azurefunctions.md"
 - How do I...:
   - Upgrade from V2 to V3 : "recipes/upgrading/v2-to-v3.md"
   - Upgrade from V3 to V4 : "recipes/upgrading/v3-to-v4.md"
@@ -108,8 +105,8 @@ nav:
     - Post data to the server: "recipes/client-server/messaging-post.md"
     - Share code between the client and the server: "recipes/client-server/share-code.md"
 - FAQs:
-  - Moving from dev to prod : "faq-build.md"
-  - Troubleshooting : "faq-troubleshooting.md"
+  - Moving from dev to prod : "faq/faq-build.md"
+  - Troubleshooting : "faq/faq-troubleshooting.md"
 - Learning Resources:
     - SAFE-Compatible UI Components: "awesome-safe-components.md"
     - Learning: "learning.md"
@@ -150,7 +147,7 @@ nav:
     - Remove Bulma: "v4-recipes/ui/remove-bulma.md"
     - Add Tailwind support: "v4-recipes/ui/add-tailwind.md"
     - Add daisyUI support: "v4-recipes/ui/add-daisyui.md"
-    - Add Feliz support: "v4-recipes/ui/add-feliz.md"
+    - Add Feliz support: "recipes/ui/add-feliz.md"
     - Migrate from a CDN stylesheet to an NPM package: "v4-recipes/ui/cdn-to-npm.md"
     - Add routing with state shared between pages: "v4-recipes/ui/add-routing.md"
     - Add routing with separate models per page: "v4-recipes/ui/add-routing-with-separate-models.md"