Update links

mythz · mythz · commit 448af39097e9 · 2025-05-17T12:00:31.000+08:00
diff --git a/MyApp/_includes/empty-projects.md b/MyApp/_includes/empty-projects.md
@@ -1,5 +1,5 @@
 
-If you don't have the [x dotnet tool](/templates/dotnet-new) installed, the quickest way to create a ServiceStack App is to download your preferred template from:
+If you don't have the [x dotnet tool](/dotnet-new) installed, the quickest way to create a ServiceStack App is to download your preferred template from:
 
 <div class="not-prose">
 <h3 class="m-0 py-8 text-4xl text-center text-blue-600"><a href="https://servicestack.net/start">servicestack.net/start</a></h3>
diff --git a/MyApp/_includes/ref-servicestack-client.md b/MyApp/_includes/ref-servicestack-client.md
@@ -82,7 +82,7 @@ A CDN hosted version of UMD `@servicestack/client` is available on unpkg.com at:
 
 ### Reference in npm projects
 
-If you started with any of the [SPA Project Templates](/templates/dotnet-new) [@servicestack/client](https://www.npmjs.com/package/@servicestack/client) is already included, other TypeScript or ES6 projects can install `@servicestack/client` from npm with:
+If you started with any of the [SPA Project Templates](/dotnet-new) [@servicestack/client](https://www.npmjs.com/package/@servicestack/client) is already included, other TypeScript or ES6 projects can install `@servicestack/client` from npm with:
 
 ```bash
 $ npm install @servicestack/client
diff --git a/MyApp/_pages/auth/authentication-and-authorization.md b/MyApp/_pages/auth/authentication-and-authorization.md
@@ -319,7 +319,7 @@ Authentication, Registration and protected Services.
 
 ## Project Templates
 
-Most of [ServiceStack's Project Templates](/templates/dotnet-new) are configured with Auth out-of-the-box or can be easily added to an empty [web](https://github.com/NetCoreTemplates/web)
+Most of [ServiceStack's Project Templates](/dotnet-new) are configured with Auth out-of-the-box or can be easily added to an empty [web](https://github.com/NetCoreTemplates/web)
 project template:
 
 :::sh
diff --git a/MyApp/_pages/create-your-first-webservice.md b/MyApp/_pages/create-your-first-webservice.md
@@ -20,7 +20,7 @@ quickly [apply gists](/mix-tool) to your project enabled by ServiceStack's effor
 
 ## Step 2: Selecting a template
 
-Importantly, the dotnet tools lets you create [.NET 6, .NET Framework](/templates/dotnet-new) and [ASP.NET Core on .NET Framework](/templates/corefx) projects.
+Importantly, the dotnet tools lets you create [.NET 6, .NET Framework](/dotnet-new) and [ASP.NET Core on .NET Framework](/templates/corefx) projects.
 Unless you're restricted to working with .NET Framework you'll want to start with a [.NET 6 project template](/templates/dotnet-new#usage), for this example
 we'll start with the Empty [web](https://github.com/NetCoreTemplates/web) template which implicitly uses the folder name for the Project Name:
 
diff --git a/MyApp/_pages/dotnet-new.md b/MyApp/_pages/dotnet-new.md
@@ -316,7 +316,7 @@ the moment they're created.
 Especially for SPA projects which need to be frequently updated, the existing .NET Project Templates system is a stale solution that doesn't offer 
 much benefit over maintaining individual GitHub projects, which is exactly what the `dotnet-new` npm tool and now `x new` .NET Core are designed around.
 
-Inside [dotnet-new](/templates/dotnet-new) and `x new` is an easier way to create and share any kind of project templates which are easier for developers
+Inside [dotnet-new](/dotnet-new) and `x new` is an easier way to create and share any kind of project templates which are easier for developers
 to create, test, maintain and install. So if you're looking for a simpler way to be able to create and maintain your own value-added project templates 
 with additional bespoke customizations, functionality, dependencies and configuration, using `x new` is a great way to maintain and share them.
 
diff --git a/MyApp/_pages/dotnet-tool.md b/MyApp/_pages/dotnet-tool.md
@@ -9,7 +9,7 @@ delivery platform where they can be run as a .NET Core Windows Desktop App with
 [Live `#Script` playground](https://sharpscript.net/docs/sharp-scripts#live-script-with-web-watch) with `x watch`.
 
 These tools contains all the functionality ServiceStack Developers or API consumers need that can be used 
-[Create ServiceStack projects](/templates/dotnet-new), run [Gist Desktop Apps](https://sharpscript.net/sharp-apps/gist-desktop-apps) 
+[Create ServiceStack projects](/dotnet-new), run [Gist Desktop Apps](https://sharpscript.net/sharp-apps/gist-desktop-apps) 
 or generate typed endpoints for consuming ServiceStack Services by either
 [Add/Update ServiceStack References](/add-servicestack-reference) or by generating [gRPC client proxies](/grpc#grpc-clients).
 
diff --git a/MyApp/_pages/flutter-grpc-mix.md b/MyApp/_pages/flutter-grpc-mix.md
@@ -30,7 +30,7 @@ $ dotnet tool install --global x
 The Flutter integration works with ServiceStack `grpc` template that has been *configured to support gRPC services*. It also makes the assumption that when working locally, the initial Flutter application will connect to the ServiceStack gRPC services via `localhost:5054` or if the client is running on an Android Emulator, `10.0.0.2:5054`.
 `5054` is the insecure HTTP port that is used by the `grpc` project template, but if you want to add `grpc` support to your application using `x mix grpc`, be sure to set up the use of the same port for local development, or modify your Flutter client to match your server setup.
 
-For example, you could [start with a new](/templates/dotnet-new) `grpc` ServiceStack project to host your services via gRPC, and add a working Flutter client which connects via gRPC using the mix template.
+For example, you could [start with a new](/dotnet-new) `grpc` ServiceStack project to host your services via gRPC, and add a working Flutter client which connects via gRPC using the mix template.
 
 ```bash
 $ x new grpc MyApp
diff --git a/MyApp/_pages/flutter-mix.md b/MyApp/_pages/flutter-mix.md
@@ -28,7 +28,7 @@ $ dotnet tool install --global x
 
 The Flutter integration works with most ServiceStack templates. It does make the assumption that when working locally, the initial Flutter application will connect to the ServiceStack host via `localhost:5001` or if the client is running on an Android Emulator, `10.0.0.2:5001`.
 
-For example, you could [start with a new](/templates/dotnet-new) `web` ServiceStack project to host your web services, and add a working Flutter client using the mix template.
+For example, you could [start with a new](/dotnet-new) `web` ServiceStack project to host your web services, and add a working Flutter client using the mix template.
 
 ```bash
 $ x new web MyApp
diff --git a/MyApp/_pages/flutter.md b/MyApp/_pages/flutter.md
@@ -31,7 +31,7 @@ $ dotnet tool install --global x
 
 The Flutter integration works with most ServiceStack templates. It does make the assumption that when working locally, the initial Flutter application will connect to the ServiceStack host via `localhost:5001` or if the client is running on an Android Emulator, `10.0.0.2:5001`.
 
-For example, you could [start with a new](/templates/dotnet-new) `web` ServiceStack project to host your web services, and add a working Flutter client using the mix template.
+For example, you could [start with a new](/dotnet-new) `web` ServiceStack project to host your web services, and add a working Flutter client using the mix template.
 
 ```bash
 $ x new web MyApp
@@ -394,7 +394,7 @@ for a complete example project.
 The Flutter integration works with ServiceStack `grpc` template that has been *configured to support gRPC services*. It also makes the assumption that when working locally, the initial Flutter application will connect to the ServiceStack gRPC services via `localhost:5054` or if the client is running on an Android Emulator, `10.0.0.2:5054`.
 `5054` is the insecure HTTP port that is used by the `grpc` project template, but if you want to add `grpc` support to your application using `x mix grpc`, be sure to set up the use of the same port for local development, or modify your Flutter client to match your server setup.
 
-For example, you could [start with a new](/templates/dotnet-new) `grpc` ServiceStack project to host your services via gRPC, and add a working Flutter client which connects via gRPC using the mix template.
+For example, you could [start with a new](/dotnet-new) `grpc` ServiceStack project to host your services via gRPC, and add a working Flutter client which connects via gRPC using the mix template.
 
 ```bash
 $ x new grpc MyApp
diff --git a/MyApp/_pages/releases/index.md b/MyApp/_pages/releases/index.md
@@ -255,7 +255,7 @@ The primary difference between the .NET Core and .NET Framework project template
 
 v5 includes **11 new .NET Core 2.0 project templates** for each of ServiceStack's most popular starting templates. Each .NET Core 2.0 template has an equivalent .NET Framework template except for [ServiceStack's Sharp Apps](https://sharpscript.net/docs/sharp-apps) which is itself a pre-built .NET Core 2.0 App that lets you develop Web Applications and HTTP APIs on-the-fly without any compilation.
 
-All .NET Core 2.0 Templates can be developed using your preferred choice of either VS Code, VS.NET or JetBrains Project Rider on your preferred Desktop OS. Given the diverse ecosystem used to develop .NET Core Applications, the new Project Templates are being maintained on GitHub and made available via our new [dotnet-new](/templates/dotnet-new) command-line utility, installable from npm with:
+All .NET Core 2.0 Templates can be developed using your preferred choice of either VS Code, VS.NET or JetBrains Project Rider on your preferred Desktop OS. Given the diverse ecosystem used to develop .NET Core Applications, the new Project Templates are being maintained on GitHub and made available via our new [dotnet-new](/dotnet-new) command-line utility, installable from npm with:
  
     $ npm install -g @servicestack/cli
  
diff --git a/MyApp/_pages/releases/v5_00_0.md b/MyApp/_pages/releases/v5_00_0.md
@@ -542,7 +542,7 @@ The primary difference between the .NET Core and .NET Framework project template
  
 Now that ServiceStack v5 has merged into a single unified set of NuGet packages that's consolidated around .NET Standard 2.0, we've developed **11 new .NET Core 2.0 project templates** for each of ServiceStack's most popular starting templates. Each .NET Core 2.0 template has an equivalent .NET Framework template except for [ServiceStack's Sharp Apps](https://sharpscript.net/docs/sharp-apps) which is itself a pre-built .NET Core 2.0 App that lets you develop Web Applications and HTTP APIs on-the-fly without any compilation.
 
-All .NET Core 2.0 Templates can be developed using your preferred choice of either VS Code, VS.NET or JetBrains Project Rider on your preferred Desktop OS. Given the diverse ecosystem used to develop .NET Core Applications, the new Project Templates are being maintained on GitHub and made available via our new [dotnet-new](/templates/dotnet-new) command-line utility, installable from npm with:
+All .NET Core 2.0 Templates can be developed using your preferred choice of either VS Code, VS.NET or JetBrains Project Rider on your preferred Desktop OS. Given the diverse ecosystem used to develop .NET Core Applications, the new Project Templates are being maintained on GitHub and made available via our new [dotnet-new](/dotnet-new) command-line utility, installable from npm with:
  
     $ npm install -g @servicestack/cli
  
diff --git a/MyApp/_pages/releases/v5_01_0.md b/MyApp/_pages/releases/v5_01_0.md
@@ -788,7 +788,7 @@ This lets us use Nuxt's Web Dev Server during development to take advantage of i
 
 ### Getting Started 
 
-To experience App development with Nuxt.js, create a new Nuxt Project using [dotnet-new](/templates/dotnet-new):
+To experience App development with Nuxt.js, create a new Nuxt Project using [dotnet-new](/dotnet-new):
 
     $ dotnet-new vue-nuxt ProjectName
 
diff --git a/MyApp/_pages/releases/v5_02.md b/MyApp/_pages/releases/v5_02.md
@@ -659,7 +659,7 @@ need to be upgraded to support newer major Webpack versions, instead of every pr
 Given the simpler development workflow and smoother future upgrades possible with CLI tools, we've replaced all our SPA Templates to use the latest
 templates generated by the CLI tools for each respective framework.
 
-All templates can be installed using our [dotnet-new](/templates/dotnet-new) tool, which if not already can be installed with:
+All templates can be installed using our [dotnet-new](/dotnet-new) tool, which if not already can be installed with:
 
     $ npm install -g @servicestack/cli
 
diff --git a/MyApp/_pages/releases/v5_05.md b/MyApp/_pages/releases/v5_05.md
@@ -2454,7 +2454,7 @@ the moment they're created.
 Especially for SPA projects which need to be frequently updated, the existing .NET Project Templates system is a stale solution that doesn't offer 
 much benefit over maintaining individual GitHub projects, which is exactly what the `dotnet-new` npm tool and now `web new` .NET Core are designed around.
 
-Inside [dotnet-new](/templates/dotnet-new) and `web new` is an easier way to create and share any kind of project templates which are easier for developers
+Inside [dotnet-new](/dotnet-new) and `web new` is an easier way to create and share any kind of project templates which are easier for developers
 to create, test, maintain and install. So if you're looking for a simpler way to be able to create and maintain your own value-added project templates 
 with additional bespoke customizations, functionality, dependencies and configuration, using `web new` is a great way to maintain and share them.
 
diff --git a/MyApp/_pages/releases/v5_08.md b/MyApp/_pages/releases/v5_08.md
@@ -18,7 +18,7 @@ With the release of [.NET Core 3.1 LTS](https://devblogs.microsoft.com/dotnet/an
 and tools to **.NET Core 3.1 LTS** whilst continuing to support existing **.NET Core 2.1+** and **.NET Framework** projects including 
 [ASP.NET Core Apps on the .NET Framework](/templates/corefx).
 
-You can view all available .NET Core Templates using the [x dotnet tool](/dotnet-tool) and running [x new](/templates/dotnet-new):
+You can view all available .NET Core Templates using the [x dotnet tool](/dotnet-tool) and running [x new](/dotnet-new):
 
     $ dotnet tool install --global x 
     $ x new
diff --git a/MyApp/_pages/releases/v5_11.md b/MyApp/_pages/releases/v5_11.md
@@ -1335,7 +1335,7 @@ container.Register<IRedisClientsManager>(c => sentinel.Start());
 
 ## Cross Platform dotnet scripts
 
-Often most of our [Project Templates](/templates/dotnet-new) need to include scripts to perform different tasks utilized in each project type, e.g. for generating DTOs, running a dev server, publishing release builds, etc.
+Often most of our [Project Templates](/dotnet-new) need to include scripts to perform different tasks utilized in each project type, e.g. for generating DTOs, running a dev server, publishing release builds, etc.
 
 To surface these common tasks to the developer we initially used Gulp and Grunt JS Tasks so they would show up in
 [VS .NET's Task Runner Explorer UI](https://marketplace.visualstudio.com/items?itemName=MadsKristensen.TaskRunnerExplorer) however this has
diff --git a/MyApp/_pages/releases/v5_13.md b/MyApp/_pages/releases/v5_13.md
@@ -506,7 +506,7 @@ Which will use the older mix configuration as its source.
 As an LTS release we expect everyone will want to upgrade to .NET 6 as soon as possible to take advantage of .NET's best & fastest 
 runtime yet. We're already using .NET 6 in production and haven't come across any reason not to upgrade yet. 
 
-With the project templates upgraded, you can now create a new ServiceStack .NET 6 App with [x new](/templates/dotnet-new):
+With the project templates upgraded, you can now create a new ServiceStack .NET 6 App with [x new](/dotnet-new):
 
 ```csharp
 $ x new
diff --git a/MyApp/_pages/releases/v6_02.md b/MyApp/_pages/releases/v6_02.md
@@ -67,7 +67,7 @@ that have benefited all our new modern jamstacks.net templates.
 
 <blazor-template repo="LegacyTemplates/blazor-server" repo2="LegacyTemplates/blazor-tailwind" class="not-prose pb-8"></blazor-template>
 
-Alternatively you can create & download a new Blazor Project with the [x dotnet tool](/templates/dotnet-new):
+Alternatively you can create & download a new Blazor Project with the [x dotnet tool](/dotnet-new):
 
 :::sh
 x new LegacyTemplates/blazor-tailwind ProjectName
diff --git a/MyApp/_pages/releases/v6_07.md b/MyApp/_pages/releases/v6_07.md
@@ -1399,7 +1399,7 @@ The [angular-spa](https://github.com/NetCoreTemplates/angular-spa) project templ
     </div>
 </a>
 
-It can be created from the [servicestack.net/start](https://servicestack.net/start) page or on the command-line with the [x tool](/templates/dotnet-new):
+It can be created from the [servicestack.net/start](https://servicestack.net/start) page or on the command-line with the [x tool](/dotnet-new):
 
 :::sh
 x new angular-spa ProjectName
diff --git a/MyApp/_pages/routing.md b/MyApp/_pages/routing.md
@@ -224,7 +224,7 @@ Which will returns the the default `index.html` page using [#Script Pages](https
 
 #### SPA Fallback
 
-This popular behavior is also available using the more convenient configuration (used in all [SPA Project Templates](/templates/dotnet-new)) with:
+This popular behavior is also available using the more convenient configuration (used in all [SPA Project Templates](/dotnet-new)) with:
 
 ```csharp
 Plugins.Add(new SharpPagesFeature {
diff --git a/MyApp/_pages/templates/aws.md b/MyApp/_pages/templates/aws.md
@@ -22,7 +22,7 @@ slug: templates-aws
 
 This project lets you create a .NET 6 empty ServiceStack web project ready for deployment as a AWS Lambda Function wired with API GateWay and packaged via a Docker image.
 
-Create new project with [x dotnet tool](/templates/dotnet-new):
+Create new project with [x dotnet tool](/dotnet-new):
 
 ```bash
 $ dotnet tool install -g x
diff --git a/MyApp/_pages/templates/blazor-bootstrap.md b/MyApp/_pages/templates/blazor-bootstrap.md
@@ -22,7 +22,7 @@ Customize and Download a new Blazor WASM Bootstrap project with your preferred p
 
 <blazor-templates class="not-prose pb-8"></blazor-templates>
 
-Alternatively you can create & download a new Blazor Project with the [x dotnet tool](/templates/dotnet-new):
+Alternatively you can create & download a new Blazor Project with the [x dotnet tool](/dotnet-new):
 
 :::sh
 x new blazor-wasm ProjectName
diff --git a/MyApp/_pages/templates/blazor-server.md b/MyApp/_pages/templates/blazor-server.md
@@ -91,7 +91,7 @@ Customize and Download a new Blazor WASM Bootstrap project with your preferred p
 
 <blazor-templates class="not-prose pb-8"></blazor-templates>
 
-Alternatively you can create & download a new Blazor Project with the [x dotnet tool](/templates/dotnet-new):
+Alternatively you can create & download a new Blazor Project with the [x dotnet tool](/dotnet-new):
 
 :::sh
 x new blazor ProjectName
diff --git a/MyApp/_pages/templates/blazor-tailwind.md b/MyApp/_pages/templates/blazor-tailwind.md
@@ -29,7 +29,7 @@ title: Blazor Tailwind
 
 <blazor-templates class="not-prose pb-8"></blazor-templates>
 
-Alternatively you can create & download a new Blazor Project with the [x dotnet tool](/templates/dotnet-new):
+Alternatively you can create & download a new Blazor Project with the [x dotnet tool](/dotnet-new):
 
 :::sh
 x new blazor-wasm ProjectName
diff --git a/MyApp/_pages/templates/dotnet-scripts.md b/MyApp/_pages/templates/dotnet-scripts.md
@@ -3,7 +3,7 @@ slug: templates-dotnet-scripts
 title: Cross platform dotnet scripts
 ---
 
-Often most of our [Project Templates](/templates/dotnet-new) need to include scripts to perform different tasks utilized in each project type, e.g. for generating DTOs, running a dev server, publishing release builds, etc. 
+Often most of our [Project Templates](/dotnet-new) need to include scripts to perform different tasks utilized in each project type, e.g. for generating DTOs, running a dev server, publishing release builds, etc. 
 
 To surface these common tasks to the developer we initially used Gulp and Grunt JS Tasks so they would show up in 
 [VS .NET's Task Runner Explorer UI](https://marketplace.visualstudio.com/items?itemName=MadsKristensen.TaskRunnerExplorer) however this has 
diff --git a/MyApp/_pages/templates/mvc.md b/MyApp/_pages/templates/mvc.md
@@ -8,7 +8,7 @@ All ServiceStack Projects can be created from ServiceStack's Start Page:
 <h3 class="m-0 py-8 text-4xl text-center text-blue-600"><a href="https://servicestack.net/start">servicestack.net/start</a></h3>
 </div>
 
-Or using the .NET [x dotnet tool](/templates/dotnet-new):
+Or using the .NET [x dotnet tool](/dotnet-new):
 
 :::sh
 dotnet tool install --global x
diff --git a/MyApp/_pages/templates/single-page-apps.md b/MyApp/_pages/templates/single-page-apps.md
diff --git a/MyApp/_pages/templates/svelte.md b/MyApp/_pages/templates/svelte.md
diff --git a/MyApp/_pages/templates/websites.md b/MyApp/_pages/templates/websites.md
diff --git a/MyApp/_pages/web-new.md b/MyApp/_pages/web-new.md
