link to defang.io/samples instead of /#samples

Author: jordanstephens

blog/2024-02-12-announcing-defang-public-beta.md

@@ -12,7 +12,7 @@ Ever since we shipped our Private Beta in the summer of 2023, we have been worki
 
 And so, today with our Public Beta, we are addressing this request. With today’s release of [Defang BYOC](https://docs.defang.io/docs/concepts/defang-byoc) (Bring-your-own-Cloud), you can now enjoy all the benefits of Defang **and** deploy applications to your own AWS account! Our Private Beta experience is still available as [Defang Playground](https://docs.defang.io/docs/concepts/defang-playground) for you to quickly and easily prototype applications and deploy them to our hosted environment.
 
-You can learn more about Defang [here](https://docs.defang.io/docs/intro). Also check out our [tutorials](https://docs.defang.io/docs/category/tutorials), [samples](https://defang.io/#samples), and [FAQ](https://docs.defang.io/docs/category/faq) to know more.
+You can learn more about Defang [here](https://docs.defang.io/docs/intro). Also check out our [tutorials](https://docs.defang.io/docs/category/tutorials), [samples](https://defang.io/samples), and [FAQ](https://docs.defang.io/docs/category/faq) to know more.
 
 **Try the Public Beta!**
 

blog/2024-07-31-july-product-updates-2.md

@@ -11,7 +11,7 @@ Hey folks! We can’t believe a month has gone by already, time flies when you
 
 1.  As our user-base grows, we wanted to make sure we’re able to scale our [Playground](https://docs.defang.io/docs/concepts/defang-playground) environment to be able to handle the load. This involved being able to shard the workload across multiple ALBs and being able to dynamically move some workloads  across shards where possible. With these changes, we are now able handle a large number of concurrent users comfortably. The only noticeable change in behavior you would see is that Defang will now ask you to “`compose down`” your previous project before you are able to deploy a new project on Playground.
 
-2.  The major news this month was the introduction of our “`debug`” functionality. The motivation for this feature was that while the Defang experience is amazing when everything goes smoothly, we saw users (including our own interns who are helping write all those [samples](https://defang.io/#samples)) struggle when they hit an error. The underlying reason for the error could come from a variety of sources: an error in the developer’s application (including in their Dockerfile or Compose file), an issue in the way Defang is processing the application, or an issue in the underlying cloud platform (currently, AWS). To the developer, it is often not obvious what the issue is or how to fix it. That got us thinking how we could make this debugging experience “radically simpler” and thus the idea for `defang debug` was born.
+2.  The major news this month was the introduction of our “`debug`” functionality. The motivation for this feature was that while the Defang experience is amazing when everything goes smoothly, we saw users (including our own interns who are helping write all those [samples](https://defang.io/samples)) struggle when they hit an error. The underlying reason for the error could come from a variety of sources: an error in the developer’s application (including in their Dockerfile or Compose file), an issue in the way Defang is processing the application, or an issue in the underlying cloud platform (currently, AWS). To the developer, it is often not obvious what the issue is or how to fix it. That got us thinking how we could make this debugging experience “radically simpler” and thus the idea for `defang debug` was born.
 
     Now (with CLI v0.5.37 if your application encounters an error that leads to a failed deployment, a failed health-check, or a run-time error, Defang will automatically detect the issue. It will then offer to help you debug it by running the `defang debug`  command. If you choose to proceed, Defang will apply an LLM model to try to determine the precise cause of the error, with the context of your application source, logs, error code etc. And it will try to come up with one or more actionable insights on how to fix the error. For an example, see the case below:
 

blog/2024-11-12-hard-lessons-from-hardware.md

@@ -60,4 +60,4 @@ Before I let you go, here are the hard lessons from hardware, from yours truly:
 4. Choose the simpler way if it is offered.
 5. That’s where Defang comes in.
 
-Want to try deploying to the cloud yourself? You can try it out [here](https://defang.io/#samples). Keep on composing up! 💪 
+Want to try deploying to the cloud yourself? You can try it out [here](https://defang.io/samples). Keep on composing up! 💪

docs/intro/features.mdx

@@ -10,7 +10,7 @@ Defang provides a streamlined experience to develop, deploy, and debug your clou
 
 ### Wide Variety of Use Cases
 - Support for [various types of applications](/docs/intro/use-cases): web services and APIs, mobile app backends, ML services, hosting LLMs, etc...
-- Support for your programming [language of choice](https://defang.io/#samples): Node.js, Python, Golang, or anything else you can package in a Dockerfile
+- Support for your programming [language of choice](https://defang.io/samples): Node.js, Python, Golang, or anything else you can package in a Dockerfile
 
 ### AI-Driven Features
 - Built-in AI agent to go [from natural language prompt to an outline project](/docs/tutorials/generate-new-code-using-ai)

docs/tutorials/deploy-using-pulumi.mdx

@@ -26,7 +26,7 @@ Make sure you are logged into the [Defang CLI](/docs/concepts/authentication.md)
 
 ## Step 2 - Configure the Pulumi Backend
 
-Navigate to your project directly. (If you don't have a project yet, try one of our [samples](https://defang.io/#samples))
+Navigate to your project directly. (If you don't have a project yet, try one of our [samples](https://defang.io/samples))
 
 
 Pulumi uses the `pulumi login` command to select a backend. In this tutorial, we will use the Local Filesystem backend for simplicity. When you are ready to deploy to production, you will probably want to look into other [Pulumi backend options](https://www.pulumi.com/docs/iac/concepts/state-and-backends).

docusaurus.config.js

@@ -7,7 +7,7 @@ const darkCodeTheme = themes.dracula;
 const redirects = [
   {
     from: '/docs/samples',
-    to: 'https://defang.io/#samples',
+    to: 'https://defang.io/samples',
   },
 ];
 
@@ -126,7 +126,7 @@ const config = {
             },
             {
               label: 'Samples',
-              href: 'https://defang.io/#samples',
+              href: 'https://defang.io/samples',
             },
             {
               label: 'GitHub',

sidebars.js

@@ -16,7 +16,7 @@ const sidebars = {
   // By default, Docusaurus generates a sidebar from the docs folder structure
   docsSidebar: [
     {type: 'autogenerated', dirName: '.'},
-    { type: 'link', label: 'Samples', href: 'https://defang.io/#samples' },
+    { type: 'link', label: 'Samples', href: 'https://defang.io/samples' },
   ],
 };