Fixing links

web/blog/2021-12-02-waspello.md

@@ -139,7 +139,7 @@ page Main {
 }
 ```
 
-All pretty straightforward so far! As you can see here, Wasp also provides [authentication out-of-the-box](/docs/language/features#authentication--authorization).
+All pretty straightforward so far! As you can see here, Wasp also provides [authentication out-of-the-box](/docs/auth/overview).
 
 Currently, the majority of the client logic of Waspello is contained in `src/client/MainPage.js` (we should break it down a little 😅 - [you can help us!](https://github.com/wasp-lang/wasp/issues/334)). Just to give you an idea, here's a quick glimpse into it:
 
@@ -163,7 +163,7 @@ const MainPage = ({ user }) => {
   )
 }
 ```
-Once you've defined a query or action as described above, you can immediately import it into your client code as shown in the code sample, by using the `@wasp` prefix in the import path. `useQuery` ensures reactivity so once the data changes the query will get re-fetched. You can find more details about it [here](/docs/language/features#usequery).
+Once you've defined a query or action as described above, you can immediately import it into your client code as shown in the code sample, by using the `@wasp` prefix in the import path. `useQuery` ensures reactivity so once the data changes the query will get re-fetched. You can find more details about it [here](/docs/data-model/operations/queries#the-usequery-hook-1).
 
 This is pretty much it from the stuff that works 😄 ! I kinda rushed a bit through things here - for more details on all Wasp features and to build your first app with Wasp, check out our [docs](/docs/).
 

web/blog/2022-06-15-jobs-feature-announcement.md

@@ -144,7 +144,7 @@ For those interested, check out the [full diff here](https://github.com/wasp-lan
 
 ## Looks neat! What’s next?
 
-First off, please check out our docs for Jobs: [https://wasp-lang.dev/docs/language/features#jobs](https://wasp-lang.dev/docs/language/features#jobs) There, you will find all the info you need to start using them. Next, if you want to see the code for this example in full, you can find it here: [https://github.com/wasp-lang/wasp/tree/release/examples/waspleau](https://github.com/wasp-lang/wasp/tree/release/examples/waspleau)
+First off, please check out our docs for [Jobs](/docs/advanced/jobs). There, you will find all the info you need to start using them. Next, if you want to see the code for this example in full, you can find it here: [https://github.com/wasp-lang/wasp/tree/release/examples/waspleau](https://github.com/wasp-lang/wasp/tree/release/examples/waspleau)
 
 In the future, we plan to add more job executors, including support for polyglot workers (imagine running your Python ML function from Wasp!). We are also open to any other ideas on how jobs can become more useful to you (like client-side access to server-side jobs, or client-side jobs using similar abstractions?). Let us know what you think!
 

web/blog/2022-06-24-ML-code-gen-vs-coding-by-hand-future.md

@@ -184,7 +184,7 @@ auth: {
     onAuthSucceededRedirectTo: "/dashboard"
   }
 ```
-Based on this, the computer/compiler could take care of all the stuff mentioned above, and then depending on the level of abstraction, provide some sort of interface (e.g. form components, or functions) to “hook” in with our own e.g. React/Node.js code (btw this is how it actually [works in Wasp](/docs/language/features#authentication--authorization)).
+Based on this, the computer/compiler could take care of all the stuff mentioned above, and then depending on the level of abstraction, provide some sort of interface (e.g. form components, or functions) to “hook” in with our own e.g. React/Node.js code (btw this is how it actually [works in Wasp](/docs/auth/overview)).
 
 We don’t need to care what exact packages or encryption methods are used beneath the hood - it is the responsibility we trust with the authors and maintainers of the abstraction layer, just like we trust that Python knows the best how to sum two numbers on the assembly level and that it is kept in sync with the latest advancements in the field. The same happens when we rely on the built-in data structures or count on the garbage collector to manage our program’s memory well.
 

web/blog/2022-09-05-dev-excuses-app-tutrial.md

@@ -137,7 +137,7 @@ We’ve added Tailwind to make our UI more pretty and Axios for making API reque
 
 Also, we’ve declared a database entity called `Excuse`, queries, and action. The `Excuse` entity consists of the entity’s ID and the text. 
 
-`Queries` are here when we need to fetch/read something, while `actions` are here when we need to change/update data. Both query and action declaration consists of two lines – a reference to the file that contains implementation and a data model to operate on. You can find more info [in the docs](#). So let’s proceed with queries/actions. <!-- TODO: update the link -->
+`Queries` are here when we need to fetch/read something, while `actions` are here when we need to change/update data. Both query and action declaration consists of two lines – a reference to the file that contains implementation and a data model to operate on. You can find more info [in the docs](/docs/data-model/operations/overview). So let’s proceed with queries/actions.
 
 
 **2) Create two files: “actions.js” and “queries.js” in the `src/server` folder.**

web/blog/2022-11-15-auth-feature-announcement.md

@@ -113,4 +113,4 @@ export default Login
 
 ## Epilogue
 
-No need to move off the grid out of frustration when adding authentication and social login to your web app. [Here](https://github.com/shayneczyzewski/authExample) is a complete, minimal example if you want to jump right in, and [here](https://wasp-lang.dev/docs/language/features#authentication--authorization) are the full docs for more info. With just a few simple steps above, we've added authentication with best practices baked into our app so we can move on to solving problems that add value to our users!
+No need to move off the grid out of frustration when adding authentication and social login to your web app. [Here](https://github.com/shayneczyzewski/authExample) is a complete, minimal example if you want to jump right in, and [here](/docs/auth/overview) are the full docs for more info. With just a few simple steps above, we've added authentication with best practices baked into our app so we can move on to solving problems that add value to our users!

web/blog/2022-11-30-optimistic-update-feature-announcement.md

@@ -157,7 +157,7 @@ function Task({ id, isDone, description }) {
   )
 }
 ```
-Those are all the changes we need, the rest of the code (i.e., `main.wasp`, `queries.js` and `actions.js`) remains the same. We won't describe the API in detail, but if you're curious, everything is covered by [our official docs](/docs/language/features#the-useaction-hook).
+Those are all the changes we need, the rest of the code (i.e., `main.wasp`, `queries.js` and `actions.js`) remains the same. We won't describe the API in detail, but if you're curious, everything is covered by [our official docs](/docs/data-model/operations/actions#the-useaction-hook-and-optimistic-updates).
 
 Finally, let's see how this version of the app looks in action:
 

web/blog/2023-01-18-wasp-beta-update-dec.md

@@ -49,7 +49,7 @@ To check out the winning projects and see where devs found Wasp most helpful, ta
 
 ## 🔑 New auth method - GitHub! 🐙
 
-Next to [username/password](/docs/language/features#username-and-password) and [Google](/docs/language/features#google), **Wasp now also supports [GitHub](/docs/language/features#github)** as an authentication method!
+Next to [username/password](/docs/auth/username-and-pass) and [Google](/docs/auth/social-auth/google), **Wasp now also supports [GitHub](/docs/auth/social-auth/github)** as an authentication method!
 
 <ImgWithCaption
     alt="Support for GitHub auth in Wasp"
@@ -58,7 +58,7 @@ Next to [username/password](/docs/language/features#username-and-password) and [
 
 Putting the code above in your `main.wasp` file and specifying your GitHub env variables is all you need to do! Wasp will provide you with a full-stack GitHub authentication along with UI helpers (GitHub sign-up button) you can immediately use in your React component.
 
-For more details, check the docs [here](/docs/language/features#github).
+For more details, check the docs [here](/docs/auth/social-auth/github).
 
 ## 💬 Let's discuss - on GitHub Discussions!
 

web/blog/2023-04-11-wasp-launch-week-two.md

@@ -92,7 +92,7 @@ It's Saturday, so you get two features for the price of one!
     caption="Adding a custom route handler at /foo/bar endpoint"
 />
 
-Although for typical CRUD you don't have to define an API since Wasp offers a typesafe RPC layer via [operations](#), sometimes you need extra flexibility (e.g. for implementing webhooks). Now you can easily do it, in a typical boilerplate-free Wasp style! <!-- TODO: update the link -->
+Although for typical CRUD you don't have to define an API since Wasp offers a typesafe RPC layer via [operations](/docs/data-model/operations/overview), sometimes you need extra flexibility (e.g. for implementing webhooks). Now you can easily do it, in a typical boilerplate-free Wasp style.
 
 ### Email sending: Wasp + Sendgrid/Mailgun/...
 

web/blog/2023-06-28-what-can-you-build-with-wasp.md

@@ -55,7 +55,7 @@ Try it out and have fun or use it as an inspiration for your next project!
 
 **Try it out**: [amicus.work](https://www.amicus.work/)
 
-**Wasp features used**: [Authentication](https://wasp-lang.dev/docs/language/features#authentication--authorization), [email sending](/docs/advanced/email), [async/cron jobs](https://wasp-lang.dev/docs/language/features#jobs)
+**Wasp features used**: [Authentication](/docs/auth/overview), [email sending](/docs/advanced/email), [async/cron jobs](/docs/advanced/jobs)
 
 **UI Framework**: [Material UI](https://mui.com/)
 
@@ -89,7 +89,7 @@ What's special about Description Generator is that it was recently sold , making
 
 **Source code**: https://github.com/vincanger/banger-tweet-bot
 
-**Wasp features used**:[Authentication](https://wasp-lang.dev/docs/language/features#authentication--authorization), [async/cron jobs](https://wasp-lang.dev/docs/language/features#jobs)
+**Wasp features used**:[Authentication](/docs/auth/overview), [async/cron jobs](/docs/advanced/jobs)
 
 **UI Framework**: [Tailwind](https://tailwindcss.com/)
 

web/blog/2023-08-09-build-real-time-voting-app-websockets-react-typescript.md

@@ -710,7 +710,7 @@ You should see a login screen this time. Go ahead and first register a user, the
 
 Once logged in, you’ll see the same hardcoded poll data as in the previous example, because, again, we haven’t set up the [Socket.IO](http://Socket.IO) client on the frontend. But this time it should be much easier.
 
-Why? Well, besides less configuration, another nice benefit of working with [TypeScript with Wasp](https://wasp-lang.dev/docs/typescript#websocket-full-stack-type-support), is that you just have to define payload types with matching event names on the server, and those types will get exposed automatically on the client! 
+Why? Well, besides less configuration, another nice benefit of working with [TypeScript with Wasp](/docs/typescript#websocket-full-stack-type-support), is that you just have to define payload types with matching event names on the server, and those types will get exposed automatically on the client! 
 
 Let’s take a look at how that works now.
 

web/docs/advanced/deployment/manually.md

@@ -34,7 +34,7 @@ wasp build
 
 :::caution PostgreSQL in production
 You won't be able to build the app if you are using SQLite as a database (which is the default database).
-You'll have to [switch to PostgreSQL](#) before deploying to production. <!-- TODO: update the link -->
+You'll have to [switch to PostgreSQL](/docs/data-model/backends#migrating-from-sqlite-to-postgresql) before deploying to production.
 :::
 
 ### 2. Deploying the API Server (backend)

web/docs/advanced/jobs.md

@@ -43,7 +43,7 @@ job mySpecialJob {
 </TabItem>
 </Tabs>
 
-Then, in your [Operations](/docs/language/features#queries-and-actions-aka-operations) or [setupFn](/docs/language/features#setupfn-serverimport-optional) (or any other NodeJS code), you can submit work to be done:
+Then, in your [Operations](/docs/data-model/operations/overview) or [setupFn](/docs/project/server-config#setup-function) (or any other NodeJS code), you can submit work to be done:
 
 <Tabs groupId="js-ts">
 <TabItem value="js" label="JavaScript">

web/docs/data-model/crud.md

@@ -13,7 +13,7 @@ Wasp makes handling these boring bits easy by offering a higher-level concept ca
 With a single declaration, you can tell Wasp to automatically generate server-side logic (i.e., Queries and Actions) for creating, reading, updating and deleting [Entities](/docs/data-model/entities). As you update definitions for your Entities, Wasp automatically regenerates the backend logic.
 
 :::caution Early preview
-This feature is currently in early preview and we are actively working on it. Read more about [our plans](/docs/language/features#crud-operations-on-top-of-entities) for CRUD operations.
+This feature is currently in early preview and we are actively working on it. Read more about [our plans](#future-of-crud-operations-in-wasp) for CRUD operations.
 :::
 
 ## Overview
@@ -62,7 +62,7 @@ Keep reading for an example of Automatic CRUD in action, or skip ahead for the [
 
 ## Example: A Simple TODO App
 
-Let's create a full-app example that uses automatic CRUD. We'll stick to using the `Task` entity from the previous example, but we'll add a `User` entity and enable [username and password](/docs/language/features#username-and-password) based auth.
+Let's create a full-app example that uses automatic CRUD. We'll stick to using the `Task` entity from the previous example, but we'll add a `User` entity and enable [username and password](/docs/auth/username-and-pass) based auth.
 
 <ImgWithCaption alt="Automatic CRUD with Wasp" source="img/crud-guide.gif" caption="We are building a simple tasks app with username based auth"/>