Merge pull request #188 from platformatic/fix/broken-redirects-on-build

Author: leorossi

docs/contributing/documentation-style-guide.md

@@ -124,7 +124,7 @@ More like this:
 >As an example, the following recommendations should be
 referenced.
 
-To view a live example, refer to the [Decorators](../db/configuration.md)
+To view a live example, refer to the [Decorators](../packages/db/configuration.md)
 reference document.
 
 To recap, **avoid "you" in reference documentation or API documentation.**

docs/file-formats.md

@@ -22,4 +22,4 @@ Platformatic supports the following file formats, their file extensions and the
 | TOML   | `.tml`, `.toml`    | Yes                |
 
 
-#### [Back to docs](../docs/composer/configuration.md#configuration-files)
+#### [Back to docs](./packages/composer/configuration.md#configuration-files)

docs/getting-started/new-api-project-instructions.md

@@ -31,6 +31,7 @@ This interactive command-line tool will guide you through setting up a new Platf
 
 ```
 - Where would you like to create your project?  => .
+- Which package manager do you want to use?     => npm
 - Which kind of service do you want to create?  => @platformatic/db 
 - What is the name of the service?              => (generated-randomly), e.g. legal-soup
 - What is the connection string?                => sqlite://./db.sqlite
@@ -45,6 +46,8 @@ After completing the wizard, your Platformatic application will be ready in the
 
 :::note
 
-If the wizard does not handle dependency installation, ensure to run `npm/yarn/pnpm` install command manually:
+If the wizard does not handle dependency installation, ensure to run `npm/yarn/pnpm` install command manually.
+
+`wattpm` sets up workspaces for the selected package manager. Running a manual installation with a different package manager may cause issues or trigger warnings.
 
 :::

docs/getting-started/quick-start-guide.md

@@ -6,13 +6,13 @@ import SetupWatt from './setup-watt.md';
 
 # Fullstack Guide
 
-Welcome to your next steps with Platformatic services such as [Platformatic Watt](/docs/watt/overview.md), [Platformatic DB](/docs/db/overview.md) with [SQLite](https://www.sqlite.org/), [Platformatic Client](/docs/client/overview.md) and the [Platformatic Composer](/docs/composer/overview.md). 
+Welcome to your next steps with Platformatic services such as [Platformatic Watt](../packages/watt/overview.md), [Platformatic DB](../packages/db/overview.md) with [SQLite](https://www.sqlite.org/), [Platformatic Client](../packages/client/overview.md) and the [Platformatic Composer](../packages/composer/overview.md). 
 
 In this tutorial, you will build a movie quotes application, where users can add, like and delete quotes from popular movies. This guide will help you setup and run your first full-stack Platformatic application.
 
 :::note
 
-While this guide uses [SQLite](https://www.sqlite.org/), Platformatic DB also supports [PostgreSQL](https://www.postgresql.org/), [MySQL](https://www.mysql.com/), and [MariaDB](https://mariadb.org/). For more details on database compatibility, see the [Platformatic DB documentation](/docs/db/overview.md#supported-databases).
+While this guide uses [SQLite](https://www.sqlite.org/), Platformatic DB also supports [PostgreSQL](https://www.postgresql.org/), [MySQL](https://www.mysql.com/), and [MariaDB](https://mariadb.org/). For more details on database compatibility, see the [Platformatic DB documentation](../packages/db/overview.md#supported-databases).
 
 :::
 
@@ -147,7 +147,7 @@ npx platformatic db migrations apply
 
 ## Add a Composer service 
 
-[Platformatic Composer](/docs/composer/overview.md) integrates different microservices into a single API for more efficient management. For the movie quotes application, you will use the Platformatic composer to aggregate the DB service, and your frontend application. 
+[Platformatic Composer](../packages/composer/overview.md) integrates different microservices into a single API for more efficient management. For the movie quotes application, you will use the Platformatic composer to aggregate the DB service, and your frontend application. 
 
 Inside `web` folder, let's create a new Platformatic Composer
 

docs/getting-started/quick-start-watt.md

@@ -9,10 +9,8 @@ This guide will help you set up and run an application composed of the following
 - [Platformatic Composer](/docs/reference/composer/introduction), to coordinate/expose them all.
 
 :::note
-
 In this guide, we will use `Next.js` as our frontend framework, but you can also use [Astro](https://astro.build/),
 or [Remix](https://remix.run/). We plan to expand the list of supported frameworks in the future.
-
 :::
 
 
@@ -26,106 +24,76 @@ Before starting, ensure you have the following installed:
 ## Set up Watt
 
 ```bash
-mkdir my-app
-cd my-app
 npx wattpm@latest init
 ```
 
 Which will output:
-
 ```
-Need to install the following packages:
-[email protected]
-Ok to proceed? (y) y
-
-[15:48:14.722] DONE (40803): Created a wattpm application in /Users/matteo/tmp/my-app.
+Hello YOUR_NAME, welcome to Watt 2.70.1!
+? Where would you like to create your project? .
+? Which kind of service do you want to create? @platformatic/service
+✔ Installing @platformatic/service@^2.70.1 using npm ...
+? What is the name of the service? my-app
+? Do you want to create another service? no
+? Do you want to use TypeScript? no
+? What port do you want to use? 3042
 ```
 
-Then, run `npm install` to install all the dependencies.
+Dependencies are going to be installed. Your application is located in `web/my-app`.
+The `watt.json` file is automatically created in the `my-app` folder, and the `package.json` file includes a `start` script and `@platformatic/node` as a dependency.
 
 ## Add your first Node.js application to Watt
 
-Inside `my-app`, create a new directory and add a simple Node.js app:
-
-```bash
-mkdir web/node
-```
-
-Then add a `package.json` like the following:
-
-```json
-{
-  "main": "server.js",
-  "type": "module",
-  "dependencies": {
-    "@platformatic/node": "^2.0.0"
-  }
-}
-```
+By choosing the `@platformatic/node` service, you have already created your nodejs app.
 
-Then, create a `web/node/server.js` file with the following content:
+This file is created as your nodejs app:
 
 ```js
-import { createServer } from 'node:http';
-
-export function build () {
-  let count = 0
+import { createServer } from 'node:http'
 
-  const server = createServer((req, res) => {
-    console.log('received request', req.url)
-    res.setHeader('Content-Type', 'application/json');
-    res.end(JSON.stringify({ content: `from node:http createServer: ${count++}!` }));
+export function create() {
+  return createServer((req, res) => {
+    res.writeHead(200, { 'content-type': 'application/json', connection: 'close' })
+    res.end(JSON.stringify({ hello: 'world' }))
   })
-
-  return server
 }
 ```
 
 :::note
-
 In this example, we are using the built-in `node:http` module to
 create a simple HTTP server that responds with a JSON object containing a counter.
 You can see that we are returning a `build` function that creates the server.
 This server will be run by Watt when the application starts in its
 own worker thread.
+:::
 
 You can also use [Express](https://expressjs.com/), [Fastify](https://fastify.dev), [Koa](https://koajs.com/)
 or any other Node.js framework.
 
-:::
-
-
-Then, we need to add the `watt.json` config file by running:
-
-```bash
-wattpm import web/node
-```
-
-Let's install the dependencies in the root of the project with 
-
-
-```bash
-npm install
-```
-
 ### Start your Watt server
 
-Run the following command in your project directory to start your Watt server:
+Run the following command in the root of project to start your Watt server:
 
 ```bash
 npm start
 ```
 
 This will internally run `wattpm start` and start your Watt server.
 
-If you want to have have a "watch mode" to automatically restart the server when you make changes, you can run:
+:::note
+
+running `npm run start` at the root directory is running the watt server. if you run `npm run start` at the service directory(in this case `web/my-app`) it is running that single service via this command from the service package.json script: `start-platformatic-node`
+
+:::
+
+If you want to have a "watch mode" to automatically restart the server when you make changes, you can run this command in the root directory:
 
 ```bash
 npm run dev
 ```
-
 Which will run `wattpm dev` and start your Watt server in watch mode.
 
+
 Your first Watt server is now live! 🌟 You can test it with:
 
 ```bash
@@ -165,10 +133,17 @@ Using existing configuration ...
 
 Start your Watt server again:
 
+You can run these commands in the root directory:
 ```bash
 npm start
 ```
 
+If you want to have a "watch mode" to automatically restart the server when you make changes, you can run this command in the root directory:
+```bash
+npm run dev
+```
+Which will run `wattpm dev` and start your Watt server in watch mode.
+
 Then, you can test it with:
 
 ```bash
@@ -177,8 +152,8 @@ curl http://localhost:3042/node
 
 :::note
 
-You can customize how the various services are expsed by changing `web/composer/platformatic.json`.
-Here is the equivalent of the default configuration when exposing a Node.js application: 
+You can customize how the various services are exposed by changing `web/composer/platformatic.json`.
+Here is the equivalent of the default configuration when exposing a Node.js application:
 
 ```json
 {

docs/guides/deployment/compiling-typescript.md

@@ -1,13 +1,13 @@
 # Compiling Typescript for Deployment
 
-[Platformatic Service](/service/overview.md), Composer, and DB provide automatic TypeScript compilation during the startup
+[Platformatic Service](../../packages/service/overview.md), Composer, and DB provide automatic TypeScript compilation during the startup
 of your Node.js server. While this provides an amazing developer experience, in production it adds additional
 start time, and it requires more resources. In this guide, we show how to compile your TypeScript
 source files before shipping to a server.
 
 ## Setup
 
-The following is supported by all Platformatic applications, as they are all based on the same [plugin system](/service/plugin.md).
+The following is supported by all Platformatic applications, as they are all based on the same [plugin system](../../packages/service/plugin.md).
 If you have generated your application using `npx wattpm create`, you will have a similar section in your config file:
 
 ```json
@@ -39,7 +39,7 @@ Remember to set `PLT_TYPESCRIPT=false` in your environment variables in the depl
 
 ## Usage with Runtime
 
-If you are building a [Runtime](/runtime/overview.md)-based application, you will need
+If you are building a [Runtime](../../packages/runtime/overview.md)-based application, you will need
 to compile every service independently or use the `plt runtime compile` command.
 
 ## Avoid shipping TypeScript sources

docs/guides/logger/services/next/package.json

@@ -9,9 +9,9 @@
     "lint": "next lint"
   },
   "dependencies": {
-    "react": "^19.0.0",
-    "react-dom": "^19.0.0",
-    "next": "15.3.3",
+    "react": "^19.1.0",
+    "react-dom": "^19.1.0",
+    "next": "15.3.5",
     "@platformatic/next": "^2.61.0"
   }
 }

docs/guides/monitoring.md

@@ -38,10 +38,10 @@ Prometheus recommends using a port different from the main application port for
 ...
 ```
 
-All the configuration settings are optional. To use the default settings, set `"metrics": true`. See the [configuration reference](../db/configuration.md#metrics) for more details.md#metrics
+All the configuration settings are optional. To use the default settings, set `"metrics": true`. See the [configuration reference](../packages/db/configuration.md#metrics) for more details.md#metrics
 
 :::caution
-Use [environment variable placeholders](../service/configuration.md#environment-variable-placeholders) in your Platformatic DB configuration file to avoid exposing credentials.
+Use [environment variable placeholders](../packages/service/configuration.md#environment-variable-placeholders) in your Platformatic DB configuration file to avoid exposing credentials.
 :::
 
 ## Custom Metrics

docs/learn/beginner/crud-application.md

@@ -8,15 +8,15 @@ import SetupWatt from '../../getting-started/setup-watt.md';
 
 # Build a Todo API with Platformatic Watt and DB
 
- In this tutorial, you will build a simple ToDo application using the [Platformatic Watt](../../watt/overview.md) and [DB](../../db/overview.md). Platformatic DB makes it easier to create endpoints that return data from a database application. It automatically generates REST/GraphQL endpoints by mapping your database and then exposes these endpoints to your API consumers.
+ In this tutorial, you will build a simple ToDo application using the [Platformatic Watt](../../packages/watt/overview.md) and [DB](../../packages/db/overview.md). Platformatic DB makes it easier to create endpoints that return data from a database application. It automatically generates REST/GraphQL endpoints by mapping your database and then exposes these endpoints to your API consumers.
 
 This guide will walk you through the steps to build Todo CRUD API with Platformatic services, highlighting the differences compared to building traditional APIs.
 
 ## Prerequisites
 Before we begin, make sure you have the following installed:
 
 - [Node.js](https://nodejs.org/) (v20.16.0+ or v22.3.0+)
-- [Platformatic CLI](../../cli.md)
+- [Platformatic CLI](../../packages/platformatic/cli.md)
 
 ## Building a Todo API
 
@@ -26,7 +26,7 @@ Let's get started!
 
 ## Setting Up the Project
 
-Before you create the database for the Todo application, first setup [Platformatic Watt](../../watt/overview.md), the Node.js application server. Run the command to setup Watt:
+Before you create the database for the Todo application, first setup [Platformatic Watt](../../packages/watt/overview.md), the Node.js application server. Run the command to setup Watt:
 
 <SetupWatt />
 
@@ -47,7 +47,7 @@ npm start
 
 Platformatic DB uses [SQLite](https://www.sqlite.org/) as the default database for any Platformatic DB application, you can see the SQL definition in the `.env` file in the root folder of your application.
 
-For the Todo API, we need two tables, Users and Todos, let's edit the migrations generated by [Platformatic CLI](../../cli.md) to add these tables:
+For the Todo API, we need two tables, Users and Todos, let's edit the migrations generated by [Platformatic CLI](../../packages/platformatic/cli.md) to add these tables:
 
 ### Creating a Users table
 
@@ -92,7 +92,7 @@ DROP TABLE Todos;
 ```
 
 :::note
-See the [Glossary](../glossary.md) for terminologies and definitions used in [Platformatic DB](../../db/overview.md).
+See the [Glossary](../glossary.md) for terminologies and definitions used in [Platformatic DB](../../packages/db/overview.md).
 :::
 
 Now let's apply the migrations we just created by running the command below:
@@ -101,7 +101,7 @@ Now let's apply the migrations we just created by running the command below:
 npx platformatic db migrations apply
 ```
 
-Notice that after running migrations, you get a `global.d.ts` and a types folder with all our types and interfaces automatically generated by [Platformatic DB](../../db/overview.md). The `global.d.ts` file is used for querying the Platformatic database.
+Notice that after running migrations, you get a `global.d.ts` and a types folder with all our types and interfaces automatically generated by [Platformatic DB](../../packages/db/overview.md). The `global.d.ts` file is used for querying the Platformatic database.
 
 Now, start your Platformatic DB application by running:
 
@@ -169,4 +169,4 @@ origin to make requests to our API.
 
 ## Conclusion
 
-Congratulations! You have successfully created a simple Todo API using Platformatic. This tutorial covered the basics of setting up a Platformatic project, defining a schema, configuring the service, and creating API endpoints. For more advanced features and configurations, refer to the [Platformatic API Documentation](../../cli.md).
+Congratulations! You have successfully created a simple Todo API using Platformatic. This tutorial covered the basics of setting up a Platformatic project, defining a schema, configuring the service, and creating API endpoints. For more advanced features and configurations, refer to the [Platformatic API Documentation](../../packages/platformatic/cli.md).

docs/learn/glossary.md

@@ -18,7 +18,7 @@ label: A comprehensive glossary of terms and terminologies associated with Platf
 ## C
 
 **CLI (Command Line Interface)**
-- A tool for interacting with Platformatic via text commands. The [Platformatic CLI](../cli.md) simplifies managing services and configurations.
+- A tool for interacting with Platformatic via text commands. The [Platformatic CLI](../packages/platformatic/cli.md) simplifies managing services and configurations.
 
 **CRUD (Create, Read, Update, Delete)**
 - Basic operations for managing data. Platformatic automates CRUD operations for API endpoints based on schemas.
@@ -114,7 +114,7 @@ label: A comprehensive glossary of terms and terminologies associated with Platf
 
 **Service**
 - A dedicated infrastructure layer for managing service-to-service communication. Platformatic can integrate with service meshes for advanced microservice management.
-- A Platformatic [Service](../service/overview.md) is an HTTP server based on [Fastify](https://fastify.dev) that allows developers to build robust APIs with Node.js.
+- A Platformatic [Service](../packages/service/overview.md) is an HTTP server based on [Fastify](https://fastify.dev) that allows developers to build robust APIs with Node.js.
 
 ## T