fix: custom email message for self-signers

chore: fix contributing guide
chore: remove list from gitpod page
2025-11-10 04:22:32 +10:00 · 2024-04-26 17:15:19 +03:00 · 2024-04-26 16:35:56 +03:00 · 2024-04-26 15:41:05 +03:00 · 2024-04-26 15:39:14 +03:00 · 2024-04-26 15:35:53 +03:00
46 changed files with 4116 additions and 9 deletions
--- a/apps/documentation/.gitignore
+++ b/apps/documentation/.gitignore
@ -0,0 +1,36 @@
+# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
+
+# dependencies
+/node_modules
+/.pnp
+.pnp.js
+.yarn/install-state.gz
+
+# testing
+/coverage
+
+# next.js
+/.next/
+/out/
+
+# production
+/build
+
+# misc
+.DS_Store
+*.pem
+
+# debug
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+
+# local env files
+.env*.local
+
+# vercel
+.vercel
+
+# typescript
+*.tsbuildinfo
+next-env.d.ts
--- a/apps/documentation/README.md
+++ b/apps/documentation/README.md
@ -0,0 +1,36 @@
+This is a [Next.js](https://nextjs.org/) project bootstrapped with [`create-next-app`](https://github.com/vercel/next.js/tree/canary/packages/create-next-app).
+
+## Getting Started
+
+First, run the development server:
+
+```bash
+npm run dev
+# or
+yarn dev
+# or
+pnpm dev
+# or
+bun dev
+```
+
+Open [http://localhost:3000](http://localhost:3000) with your browser to see the result.
+
+You can start editing the page by modifying `app/page.tsx`. The page auto-updates as you edit the file.
+
+This project uses [`next/font`](https://nextjs.org/docs/basic-features/font-optimization) to automatically optimize and load Inter, a custom Google Font.
+
+## Learn More
+
+To learn more about Next.js, take a look at the following resources:
+
+- [Next.js Documentation](https://nextjs.org/docs) - learn about Next.js features and API.
+- [Learn Next.js](https://nextjs.org/learn) - an interactive Next.js tutorial.
+
+You can check out [the Next.js GitHub repository](https://github.com/vercel/next.js/) - your feedback and contributions are welcome!
+
+## Deploy on Vercel
+
+The easiest way to deploy your Next.js app is to use the [Vercel Platform](https://vercel.com/new?utm_medium=default-template&filter=next.js&utm_source=create-next-app&utm_campaign=create-next-app-readme) from the creators of Next.js.
+
+Check out our [Next.js deployment documentation](https://nextjs.org/docs/deployment) for more details.
--- a/apps/documentation/app/favicon.ico
+++ b/apps/documentation/app/favicon.ico
--- a/apps/documentation/app/globals.css
+++ b/apps/documentation/app/globals.css
@ -0,0 +1,33 @@
+@tailwind base;
+@tailwind components;
+@tailwind utilities;
+
+:root {
+  --foreground-rgb: 0, 0, 0;
+  --background-start-rgb: 214, 219, 220;
+  --background-end-rgb: 255, 255, 255;
+}
+
+@media (prefers-color-scheme: dark) {
+  :root {
+    --foreground-rgb: 255, 255, 255;
+    --background-start-rgb: 0, 0, 0;
+    --background-end-rgb: 0, 0, 0;
+  }
+}
+
+body {
+  color: rgb(var(--foreground-rgb));
+  background: linear-gradient(
+      to bottom,
+      transparent,
+      rgb(var(--background-end-rgb))
+    )
+    rgb(var(--background-start-rgb));
+}
+
+@layer utilities {
+  .text-balance {
+    text-wrap: balance;
+  }
+}
--- a/apps/documentation/app/layout.tsx
+++ b/apps/documentation/app/layout.tsx
@ -0,0 +1,22 @@
+import type { Metadata } from "next";
+import { Inter } from "next/font/google";
+import "./globals.css";
+
+const inter = Inter({ subsets: ["latin"] });
+
+export const metadata: Metadata = {
+  title: "Create Next App",
+  description: "Generated by create next app",
+};
+
+export default function RootLayout({
+  children,
+}: Readonly<{
+  children: React.ReactNode;
+}>) {
+  return (
+    <html lang="en">
+      <body className={inter.className}>{children}</body>
+    </html>
+  );
+}
--- a/apps/documentation/next.config.js
+++ b/apps/documentation/next.config.js
@ -0,0 +1,9 @@
+/** @type {import('next').NextConfig} */
+const nextConfig = {};
+
+const withNextra = require('nextra')({
+  theme: 'nextra-theme-docs',
+  themeConfig: './theme.config.tsx',
+});
+
+module.exports = withNextra(nextConfig);
--- a/apps/documentation/package.json
+++ b/apps/documentation/package.json
@ -0,0 +1,29 @@
+{
+  "name": "@documenso/documentation",
+  "version": "0.1.0",
+  "private": true,
+  "scripts": {
+    "dev": "next dev -p 3002",
+    "build": "next build",
+    "start": "next start -p 3002",
+    "lint:fix": "next lint --fix",
+    "clean": "rimraf .next && rimraf node_modules",
+    "copy:pdfjs": "node ../../scripts/copy-pdfjs.cjs"
+  },
+  "dependencies": {
+    "next": "14.0.3",
+    "nextra": "^2.13.4",
+    "nextra-theme-docs": "^2.13.4",
+    "react": "^18",
+    "react-dom": "^18"
+  },
+  "devDependencies": {
+    "@types/node": "^20",
+    "@types/react": "^18",
+    "@types/react-dom": "^18",
+    "autoprefixer": "^10.0.1",
+    "postcss": "^8",
+    "tailwindcss": "^3.3.0",
+    "typescript": "^5"
+  }
+}
--- a/apps/documentation/pages/_app.mdx
+++ b/apps/documentation/pages/_app.mdx
@ -0,0 +1,7 @@
+import '../styles.css'
+
+export default function App({ Component, pageProps }) {
+  return <Component {...pageProps} />
+
+
+}
--- a/apps/documentation/pages/_meta.json
+++ b/apps/documentation/pages/_meta.json
@ -0,0 +1,44 @@
+{
+  "index": {
+    "title": "Home",
+    "type": "page",
+    "theme": {
+      "layout": "full",
+      "sidebar": false
+    },
+    "display": "hidden"
+  },
+  "app": {
+    "title": "Getting Started",
+    "type": "page"
+  },
+  "faq": {
+    "title": "FAQ",
+    "type": "page"
+  },
+  "local-development": {
+    "title": "Local Development",
+    "type": "page"
+  },
+  "public-api": {
+    "title": "Public API",
+    "type": "page",
+    "href": "/fcc/"
+  },
+  "webhooks": {
+    "title": "Webhooks",
+    "type": "page"
+  },
+  "contributing": {
+    "title": "Contributing Guide",
+    "type": "page"
+  },
+  "---": {
+    "type": "separator"
+  },
+  "GitHub": {
+    "title": "View on GitHub",
+    "href": "https://documen.so/github",
+    "newWindow": true
+  }
+}
--- a/apps/documentation/pages/app/getting-started.mdx
+++ b/apps/documentation/pages/app/getting-started.mdx
@ -0,0 +1 @@
+# Getting Started
--- a/apps/documentation/pages/contributing/_meta.json
+++ b/apps/documentation/pages/contributing/_meta.json
@ -0,0 +1,8 @@
+{
+  "index": {
+    "title": "Get started",
+    "theme": {
+      "sidebar": false
+    }
+  }
+}
--- a/apps/documentation/pages/contributing/index.mdx
+++ b/apps/documentation/pages/contributing/index.mdx
@ -0,0 +1,115 @@
+---
+title: Contributing Guide
+description: Learn how to contribute to Documenso and become part of our community.
+---
+
+import { Callout, Steps } from 'nextra/components';
+
+# Contributing to Documenso
+
+If you plan to contribute to Documenso, please take a moment to feel awesome ✨. People like you are what open source is about ♥. Any contributions, no matter how big or small, are highly appreciated 🙏. This guide will help you get started with contributing to Documenso 💻.
+
+## Before Getting Started
+
+<Steps>
+
+### Check the Existing Issues and Pull Requests
+
+Search the existing [issues](https://github.com/documenso/documenso/issues) to see if someone else reported the same issue. Or, check the [existing PRs](https://github.com/documenso/documenso/pulls) to see if someone else is already working on the same thing.
+
+### Creating a New Issue
+
+If there is no issue or PR for the problem you are facing, feel free to create a new issue. Make sure to provide as much detail as possible, including the steps to reproduce the issue.
+
+### Picking an Existing Issue
+
+If you pick an existing issue, take into consideration the discussion on the issue.
+
+### Contributor License Agreement
+
+Accept the [Contributor License Agreement](https://documen.so/cla) to ensure we can accept your contributions.
+
+</Steps>
+
+## Taking Issues
+
+Before taking an issue, ensure that:
+
+- The issue has been assigned the public label.
+- The issue is clearly defined and understood.
+- No one has been assigned to the issue.
+- No one has expressed the intention to work on it.
+
+After that:
+
+1. Comment on the issue with your intention to work on it.
+2. Start working on the issue.
+
+Feel free to ask for help, clarification or guidance if needed. We are here to help you.
+
+## Developing
+
+The development branch is `main`, and all pull requests should be made against this branch. Here's how you can get started with developing:
+
+<Steps>
+
+### Set Up Documenso Locally
+
+Check out the [local development](/local-development) guide to set up your local environment.
+
+### Pick a Task
+
+Find an issue to work on or create a new one.
+
+- Before starting to work on an issue, ensure that no one else is working on it. If no one is assigned to the issue, feel free to pick it up by leaving a comment on the issue and asking to get it assigned to you.
+
+Before creating a new issue, check the existing issues to see if someone else has already reported it.
+
+### Create a New Branch
+
+After you're assigned an issue, you can start working on it. Create a new branch for your feature or bug fix.
+
+When creating a branch, make sure that the branch name:
+
+- starts with the correct prefix: `feat/` for new features, `fix/` for bug fixes, etc.
+- includes the issue id you are working on (if applicable).
+- is descriptive.
+
+```sh
+git checkout -b feat/issue-id-your-branch-name
+
+## Example
+git checkout -b feat/1234-add-share-button-to-articles
+```
+
+In the pull request description, include `references #yyyy` or `fixes #yyyy` to link it to the issue you are working on.
+
+### Implement Your Changes
+
+Start working on the issue you picked up and implement the changes. Make sure to test your changes locally and ensure that they work as expected.
+
+### Open a Pull Request
+
+After implementing your changes, open a pull request against the `main` branch.
+
+</Steps>
+
+<Callout type="info">
+  If you need help getting started, [join us on Discord](https://documen.so/discord).
+</Callout>
+
+## Building
+
+Before pushing code or creating pull requests, please ensure you can successfully create a successful production build. You can build the project by running the following command in your terminal:
+
+```bash
+npm run build
+```
+
+Once the project builds successfully, you can push your code changes or create a pull request.
+
+<Callout type="info">
+  Remember to run tests and perform any necessary checks before finalizing your changes. As a
+  result, we can collaborate more effectively and maintain a high standard of code quality in our
+  project.
+</Callout>
--- a/apps/documentation/pages/faq/faq.mdx
+++ b/apps/documentation/pages/faq/faq.mdx
@ -0,0 +1 @@
+# FAQ
--- a/apps/documentation/pages/index.mdx
+++ b/apps/documentation/pages/index.mdx
@ -0,0 +1,78 @@
+export const Wrapper = ({ children }) => {
+  return <div className="p-24">{children}</div>;
+};
+
+<Wrapper>
+
+# Documentation
+
+Welcome to the official Documenso documentation! This documentation is designed to help you get started with Documenso.
+
+For users, we'll guide you through setting up your Documenso account, creating and organizing your documents, collaborating with team members, and leveraging our advanced features. You'll learn how to get the most out of Documenso.
+
+If you're a developer, you'll find detailed information on how to set up your local development environment, work with our API, and utilize webhooks for seamless integration. We'll provide code examples, best practices, and troubleshooting tips to help you effectively incorporate Documenso's features into your applications.
+
+We aim to make our documentation clear, concise, and easy to navigate. If you have any questions, feedback, or suggestions for improving our documentation, please don't hesitate to reach out to us. We want to make your experience with Documenso as smooth and enjoyable as possible.
+
+Let's get started!
+
+## About Documenso
+
+Signing documents digitally should be fast and easy and should be the best practice for every document signed worldwide.
+
+This is technically quite easy today, but it also introduces a new party to every signature: The signing tool providers. While this is not a problem in itself, it should make us think about how we want these providers of trust to work.
+
+Documenso aims to be the world's most trusted document-signing tool. This trust is built by empowering you to self-host Documenso and review how it works under the hood.
+
+Join us in creating the next generation of open trust infrastructure.
+
+## Our tech stack:
+
+- [Typescript](https://www.typescriptlang.org/) - Language
+- [Next.js](https://nextjs.org/) - Framework
+- [Prisma](https://www.prisma.io/) - ORM
+- [Tailwind](https://tailwindcss.com/) - CSS
+- [shadcn/ui](https://ui.shadcn.com/) - Component Library
+- [NextAuth.js](https://next-auth.js.org/) - Authentication
+- [react-email](https://react.email/) - Email Templates
+- [tRPC](https://trpc.io/) - API
+- [@documenso/pdf-sign](https://www.npmjs.com/package/@documenso/pdf-sign) - PDF Signatures
+- [React-PDF](https://github.com/wojtekmaj/react-pdf) - Viewing PDFs
+- [PDF-Lib](https://github.com/Hopding/pdf-lib) - PDF manipulation
+- [Stripe](https://stripe.com/) - Payments
+- [Vercel](https://vercel.com) - Hosting
+
+<div className="mt-16 flex items-center justify-center gap-4">
+  <a href="https://documen.so/discord">
+    <img
+      src="https://img.shields.io/badge/Discord-documen.so/discord-%235865F2"
+      alt="Join Documenso on Discord"
+    />
+  </a>
+  <a href="https://github.com/documenso/documenso/stargazers">
+    <img src="https://img.shields.io/github/stars/documenso/documenso" alt="Github Stars" />
+  </a>
+  <a href="https://github.com/documenso/documenso/blob/main/LICENSE">
+    <img src="https://img.shields.io/badge/license-AGPLv3-purple" alt="License" />
+  </a>
+  <a href="https://github.com/documenso/documenso/pulse">
+    <img
+      src="https://img.shields.io/github/commit-activity/m/documenso/documenso"
+      alt="Commits-per-month"
+    />
+  </a>
+  <a href="https://vscode.dev/redirect?url=vscode://ms-vscode-remote.remote-containers/cloneInVolume?url=https://github.com/documenso/documenso">
+    <img
+      alt="open in devcontainer"
+      src="https://img.shields.io/static/v1?label=Dev%20Containers&message=Enabled&color=blue&logo=visualstudiocode"
+    />
+  </a>
+  <a href="https://github.com/documenso/documenso/blob/main/CODE_OF_CONDUCT.md">
+    <img
+      src="https://img.shields.io/badge/Contributor%20Covenant-2.1-4baaaa.svg"
+      alt="Contributor Covenant"
+    />
+  </a>
+</div>
+
+</Wrapper>
--- a/apps/documentation/pages/local-development/_meta.json
+++ b/apps/documentation/pages/local-development/_meta.json
@ -0,0 +1,7 @@
+{
+  "index": "Home",
+  "quickstart": "Developer Quickstart",
+  "manual": "Manual Setup",
+  "docker": "Docker",
+  "gitpod": "Gitpod"
+}
--- a/apps/documentation/pages/local-development/docker.mdx
+++ b/apps/documentation/pages/local-development/docker.mdx
@ -0,0 +1,177 @@
+---
+title: Docker Development
+description: Set up Documenso using Docker for local development.
+---
+
+import { Callout, Steps } from 'nextra/components';
+
+# Docker
+
+The following guide will walk you through setting up Documenso using Docker. You can choose between a Docker Compose production setup or a standalone container.
+
+We provide a Docker container for Documenso, which is published on both DockerHub and GitHub Container Registry.
+
+- DockerHub: [https://hub.docker.com/r/documenso/documenso](https://hub.docker.com/r/documenso/documenso)
+- GitHub Container Registry: [https://ghcr.io/documenso/documenso](https://ghcr.io/documenso/documenso)
+
+You can pull the Docker image from either of these registries and run it with your preferred container hosting provider.
+
+Please note that you will need to provide environment variables for connecting to the database, mail server, and other services.
+
+## Prerequisites
+
+Before you begin, ensure that you have the following installed:
+
+- Docker
+- Docker Compose (if using the Docker Compose setup)
+
+## Option 1: Production Docker Compose Setup
+
+This setup includes a PostgreSQL database and the Documenso application. You will need to provide your own SMTP details using environment variables.
+
+<Steps>
+
+### Download the Docker Compose File
+
+Download the Docker Compose file from the Documenso repository - [compose.yml](https://raw.githubusercontent.com/documenso/documenso/release/docker/production/compose.yml).
+
+### Navigate to the `compose.yml` File
+
+Once downloaded, navigate to the directory containing the `compose.yml` file.
+
+### Set Up Environment Variables
+
+Create a `.env` file in the same directory as the `compose.yml` file.
+
+Then add your SMTP details as well as the following environment variables:
+
+```bash
+NEXTAUTH_SECRET="<your-secret>"
+NEXT_PRIVATE_ENCRYPTION_KEY="<your-key>"
+NEXT_PRIVATE_ENCRYPTION_SECONDARY_KEY="<your-secondary-key>"
+NEXT_PUBLIC_WEBAPP_URL="<your-url>"
+NEXT_PRIVATE_SMTP_TRANSPORT="smtp-auth"
+NEXT_PRIVATE_SMTP_HOST="<your-host>"
+NEXT_PRIVATE_SMTP_PORT=<your-port>
+NEXT_PRIVATE_SMTP_USERNAME="<your-username>"
+NEXT_PRIVATE_SMTP_PASSWORD="<your-password>"
+```
+
+### Update the Volume Binding
+
+The `cert.p12` file is required to sign and encrypt documents, so you must provide your key file. Update the volume binding in the `compose.yml` file to point to your key file:
+
+```yaml
+volumes:
+  - /path/to/your/keyfile.p12:/opt/documenso/cert.p12
+```
+
+After updating the volume binding, save the `compose.yml` file and run the following command to start the containers:
+
+```bash
+docker-compose --env-file ./.env -d up
+```
+
+The command will start the PostgreSQL database and the Documenso application containers.
+
+### Access the Application
+
+Access the Documenso application by visiting `http://localhost:3000` in your web browser.
+
+</Steps>
+
+## Option 2: Standalone Docker Container
+
+If you prefer to host the Documenso application on a specific container provider, you can use the pre-built Docker image from DockerHub or GitHub's Package Registry. Note that you will need to provide your own database and SMTP host.
+
+<Steps>
+
+### Pull the Docker Image
+
+Pull the Documenso Docker image from DockerHub:
+
+```bash
+docker pull documenso/documenso
+```
+
+Or, pull the image from GitHub Container Registry:
+
+```bash
+docker pull ghcr.io/documenso/documenso
+```
+
+### Run the Docker Container
+
+Run the Docker container with the required environment variables:
+
+```bash
+docker run -d \
+ -p 3000:3000 \
+ -e NEXTAUTH_URL="<your-nextauth-url>"
+ -e NEXTAUTH_SECRET="<your-nextauth-secret>"
+ -e NEXT_PRIVATE_ENCRYPTION_KEY="<your-next-private-encryption-key>"
+ -e NEXT_PRIVATE_ENCRYPTION_SECONDARY_KEY="<your-next-private-encryption-secondary-key>"
+ -e NEXT_PUBLIC_WEBAPP_URL="<your-next-public-webapp-url>"
+ -e NEXT_PRIVATE_DATABASE_URL="<your-next-private-database-url>"
+ -e NEXT_PRIVATE_DIRECT_DATABASE_URL="<your-next-private-database-url>"
+ -e NEXT_PRIVATE_SMTP_TRANSPORT="<your-next-private-smtp-transport>"
+ -e NEXT_PRIVATE_SMTP_FROM_NAME="<your-next-private-smtp-from-name>"
+ -e NEXT_PRIVATE_SMTP_FROM_ADDRESS="<your-next-private-smtp-from-address>"
+ -v /path/to/your/keyfile.p12:/opt/documenso/cert.p12
+ documenso/documenso
+```
+
+Replace the placeholders with the actual values.
+
+### Access the Application
+
+Access the Documenso application by visiting the URL you provided for the `NEXT_PUBLIC_WEBAPP_URL` environment variable in your web browser.
+
+</Steps>
+
+## Advanced Configuration
+
+The environment variables listed above are a subset of those available for configuring Documenso. The table below provides a complete list of environment variables and their descriptions.
+
+| Variable                                     | Description                                                                                         |
+| -------------------------------------------- | --------------------------------------------------------------------------------------------------- |
+| `PORT`                                       | The port on which the Documenso application runs. It defaults to `3000`.                            |
+| `NEXTAUTH_URL`                               | The URL for the NextAuth.js authentication service.                                                 |
+| `NEXTAUTH_SECRET`                            | The secret key used by NextAuth.js for encryption and signing.                                      |
+| `NEXT_PRIVATE_ENCRYPTION_KEY`                | The primary encryption key for symmetric encryption and decryption (at least 32 characters).        |
+| `NEXT_PRIVATE_ENCRYPTION_SECONDARY_KEY`      | The secondary encryption key for symmetric encryption and decryption (at least 32 characters).      |
+| `NEXT_PRIVATE_GOOGLE_CLIENT_ID`              | The Google client ID for Google authentication (optional).                                          |
+| `NEXT_PRIVATE_GOOGLE_CLIENT_SECRET`          | The Google client secret for Google authentication (optional).                                      |
+| `NEXT_PUBLIC_WEBAPP_URL`                     | The URL for the web application.                                                                    |
+| `NEXT_PRIVATE_DATABASE_URL`                  | The URL for the primary database connection (with connection pooling).                              |
+| `NEXT_PRIVATE_DIRECT_DATABASE_URL`           | The URL for the direct database connection (without connection pooling).                            |
+| `NEXT_PRIVATE_SIGNING_TRANSPORT`             | The signing transport to use. Available options: local (default)                                    |
+| `NEXT_PRIVATE_SIGNING_PASSPHRASE`            | The passphrase for the key file.                                                                    |
+| `NEXT_PRIVATE_SIGNING_LOCAL_FILE_CONTENTS`   | The base64-encoded contents of the key file will be used instead of the file path.                  |
+| `NEXT_PRIVATE_SIGNING_LOCAL_FILE_PATH`       | The path to the key file, default `/opt/documenso/cert.p12`.                                        |
+| `NEXT_PUBLIC_UPLOAD_TRANSPORT`               | The transport for file uploads (database or s3).                                                    |
+| `NEXT_PRIVATE_UPLOAD_ENDPOINT`               | The endpoint for the S3 storage transport (for third-party S3-compatible providers).                |
+| `NEXT_PRIVATE_UPLOAD_FORCE_PATH_STYLE`       | Whether to force path-style URLs for the S3 storage transport.                                      |
+| `NEXT_PRIVATE_UPLOAD_REGION`                 | The region for the S3 storage transport (defaults to us-east-1).                                    |
+| `NEXT_PRIVATE_UPLOAD_BUCKET`                 | The bucket to use for the S3 storage transport.                                                     |
+| `NEXT_PRIVATE_UPLOAD_ACCESS_KEY_ID`          | The access key ID for the S3 storage transport.                                                     |
+| `NEXT_PRIVATE_UPLOAD_SECRET_ACCESS_KEY`      | The secret access key for the S3 storage transport.                                                 |
+| `NEXT_PRIVATE_SMTP_TRANSPORT`                | The transport to send emails (smtp-auth, smtp-api, resend, or mailchannels).                        |
+| `NEXT_PRIVATE_SMTP_HOST`                     | The host for the SMTP server for SMTP transports.                                                   |
+| `NEXT_PRIVATE_SMTP_PORT`                     | The port for the SMTP server for SMTP transports.                                                   |
+| `NEXT_PRIVATE_SMTP_USERNAME`                 | The username for the SMTP server for the `smtp-auth` transport.                                     |
+| `NEXT_PRIVATE_SMTP_PASSWORD`                 | The password for the SMTP server for the `smtp-auth` transport.                                     |
+| `NEXT_PRIVATE_SMTP_APIKEY_USER`              | The API key user for the SMTP server for the `smtp-api` transport.                                  |
+| `NEXT_PRIVATE_SMTP_APIKEY`                   | The API key for the SMTP server for the `smtp-api` transport.                                       |
+| `NEXT_PRIVATE_SMTP_SECURE`                   | Whether to force the use of TLS for the SMTP server for SMTP transports.                            |
+| `NEXT_PRIVATE_SMTP_FROM_ADDRESS`             | The email address for the "from" address.                                                           |
+| `NEXT_PRIVATE_SMTP_FROM_NAME`                | The sender name for the "from" address.                                                             |
+| `NEXT_PRIVATE_RESEND_API_KEY`                | The API key for Resend.com for the `resend` transport.                                              |
+| `NEXT_PRIVATE_MAILCHANNELS_API_KEY`          | The optional API key for MailChannels (if using a proxy) for the `mailchannels` transport.          |
+| `NEXT_PRIVATE_MAILCHANNELS_ENDPOINT`         | The optional endpoint for the MailChannels API (if using a proxy) for the `mailchannels` transport. |
+| `NEXT_PRIVATE_MAILCHANNELS_DKIM_DOMAIN`      | The domain for DKIM signing with MailChannels for the `mailchannels` transport.                     |
+| `NEXT_PRIVATE_MAILCHANNELS_DKIM_SELECTOR`    | The selector for DKIM signing with MailChannels for the `mailchannels` transport.                   |
+| `NEXT_PRIVATE_MAILCHANNELS_DKIM_PRIVATE_KEY` | The private key for DKIM signing with MailChannels for the `mailchannels` transport.                |
+| `NEXT_PUBLIC_DOCUMENT_SIZE_UPLOAD_LIMIT`     | The maximum document upload limit displayed to the user (in MB).                                    |
+| `NEXT_PUBLIC_POSTHOG_KEY`                    | The optional PostHog key for analytics and feature flags.                                           |
+| `NEXT_PUBLIC_DISABLE_SIGNUP`                 | Whether to disable user signups through the /signup page.                                           |
--- a/apps/documentation/pages/local-development/gitpod.mdx
+++ b/apps/documentation/pages/local-development/gitpod.mdx
@ -0,0 +1,10 @@
+---
+title: Run in Gitpod
+description: Get started with Documenso in a ready-to-use Gitpod workspace in your browser.
+---
+
+# Run in Gitpod
+
+Click below to launch a ready-to-use Gitpod workspace in your browser.
+
+[![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/#https://github.com/documenso/documenso)
--- a/apps/documentation/pages/local-development/index.mdx
+++ b/apps/documentation/pages/local-development/index.mdx
@ -0,0 +1,15 @@
+---
+title: Local development
+description: Learn how to set up Documenso for local development.
+---
+
+# Local development
+
+There are multiple ways of setting up Documenso for local development. At the moment of writing this documentation, there are 4 ways of running Documenso locally:
+
+- [Using the developer quickstart](/local-development/quickstart)
+- [Manually setting up the development environment](/local-development/manual)
+- [Using the Docker image](/local-development/docker)
+- [Using Gitpod](/local-development/gitpod)
+
+Pick the one that fits your needs the best.
--- a/apps/documentation/pages/local-development/manual.mdx
+++ b/apps/documentation/pages/local-development/manual.mdx
@ -0,0 +1,77 @@
+---
+title: Manual Setup
+description: Manually set up Documenso on your machine for local development.
+---
+
+import { Callout, Steps } from 'nextra/components';
+
+# Manual Setup
+
+Follow these steps to set up Documenso on your local machine:
+
+<Steps>
+
+### Fork Documenso
+
+Fork the [Documenso repository](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks) to your GitHub account.
+
+### Clone Repository
+
+After forking the repository, clone it to your local device by using the following command:
+
+```bash
+git clone https://github.com/<your-username>/documenso
+```
+
+### Install Dependencies
+
+Run `npm i` in the root directory to install the dependencies required for the project.
+
+### Set Up Environment Variables
+
+Set up the following environment variables in the `.env` file:
+
+```bash
+NEXTAUTH_URL
+NEXTAUTH_SECRET
+NEXT_PUBLIC_WEBAPP_URL
+NEXT_PUBLIC_MARKETING_URL
+NEXT_PRIVATE_DATABASE_URL
+NEXT_PRIVATE_DIRECT_DATABASE_URL
+NEXT_PRIVATE_SMTP_FROM_NAME
+NEXT_PRIVATE_SMTP_FROM_ADDRESS
+```
+
+Alternatively, you can run `cp .env.example .env` to get started with our handpicked defaults.
+
+### Create Database Schema
+
+Create the database schema by running the following command:
+
+```bash
+npm run prisma:migrate-dev
+```
+
+### Optional: Seed the Database
+
+Seed the database with test data by running the following command:
+
+```bash
+npm run prisma:seed -w @documenso/prisma
+```
+
+### Start the Application
+
+Run `npm run dev` in the root directory to start the application.
+
+### Access the Application
+
+Access the Documenso application by visiting `http://localhost:3000` in your web browser.
+
+</Steps>
+
+<Callout type="info">
+  Optional: Create your signing certificate. To generate your own using these steps and a Linux
+  Terminal or Windows Subsystem for Linux (WSL), see **[Create your signing
+  certificate](./SIGNING.md)**.
+</Callout>
--- a/apps/documentation/pages/local-development/quickstart.mdx
+++ b/apps/documentation/pages/local-development/quickstart.mdx
@ -0,0 +1,66 @@
+---
+title: Developer Quickstart
+description: Quickly set up Documenso on your machine for local development with Docker and Docker Compose.
+---
+
+import { Callout, Steps } from 'nextra/components';
+
+# Developer Quickstart
+
+<Callout type="info">
+  **Note**: This guide assumes that you have both [docker](https://docs.docker.com/get-docker/) and
+  [docker-compose](https://docs.docker.com/compose/) installed on your machine.
+</Callout>
+
+Want to get up and running quickly? Follow these steps:
+
+<Steps>
+
+### Fork Documenso
+
+Fork the [Documenso repository](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks) to your GitHub account.
+
+### Clone Repository
+
+After forking the repository, clone it to your local device by using the following command:
+
+```bash
+git clone https://github.com/<your-username>/documenso
+```
+
+### Set Up Environment Variables
+
+Set up your environment variables in the `.env` file using the `.env.example` file as a reference.
+
+Alternatively, you can run `cp .env.example .env` to get started with our handpicked defaults.
+
+### Start Database and Mail Server
+
+Run `npm run dx` in the root directory.
+
+This will spin up a Postgres database and inbucket mailserver in a docker container.
+
+### Start the Application
+
+Run `npm run dev` in the root directory to start the application.
+
+### Optional: Fasten the Process
+
+Want it even faster? Just use:
+
+```sh
+npm run d
+```
+
+</Steps>
+
+### Access Points for the Project
+
+You can access the following services:
+
+- Main application - http://localhost:3000
+- Incoming Mail Access - http://localhost:9000
+- Database Connection Details:
+- Port: 54320
+- Connection: Use your favourite database client to connect to the database.
+- S3 Storage Dashboard - http://localhost:9001
--- a/apps/documentation/pages/public-api/_meta.json
+++ b/apps/documentation/pages/public-api/_meta.json
@ -0,0 +1,6 @@
+{
+  "intro": "Intro",
+  "authentication": "Authentication",
+  "versioning": "Versioning",
+  "api-reference": "API Reference"
+}
--- a/apps/documentation/pages/public-api/api-reference.mdx
+++ b/apps/documentation/pages/public-api/api-reference.mdx
@ -0,0 +1,6 @@
+---
+title: 'API Reference'
+description: 'Reference documentation for the Documenso public API.'
+---
+
+# API Reference
--- a/apps/documentation/pages/public-api/authentication.mdx
+++ b/apps/documentation/pages/public-api/authentication.mdx
@ -0,0 +1,67 @@
+---
+title: 'API Authentication'
+description: 'Learn how to create a Documenso API key and authenticate your API requests.'
+---
+
+# API Authentication
+
+Documenso uses API keys for authentication. An API key is a unique token that is generated for each client. The client must provide the key whenever it makes an API call. This way, Documenso can identify the clients making the requests and authorize their access to the API.
+
+## Creating an API Key
+
+To create an API key, navigate to the user settings page. Click on your avatar in the top right corner of the dashboard and select "**[User settings](https://app.documenso.com/settings)**" from the dropdown menu.
+
+![A screenshot of the Documenso's dashboard that shows the dropdown menu when you click on your user avatar](/public-api-images/documenso-user-dropdown-menu.webp)
+
+Once you're on the user settings page, navigate to the "**[API Tokens](https://app.documenso.com/settings/tokens)**" tab. The "API Token" page lists your existing keys and enables you to create new ones.
+
+![A screenshot of the Documenso's user settings page that shows the API Tokens page](/public-api-images/api-tokens-page-documenso.webp)
+
+To create a new API key, you must:
+
+- Choose a name (e.g. "zapier-key")
+- we recommend using a descriptive name that helps you quickly identify the key and its purpose
+- Choose an expiration date
+- you can set the key to never expire or choose when to become invalid: 7 days, 1 month, 3 months, 6 months, or 1 year
+
+After providing the required information, click the "Create token" button to generate the API key.
+
+![A screenshot of the newly created API token in the Documenso dashboard](/public-api-images/documenso-api-key-blurred.webp)
+
+Once you've created the token, Documenso will display the key on the screen. Make sure to copy the key and store it securely. You won't be able to see the key again once you refresh/leave the page.
+
+## Using the API Key
+
+To authenticate your API requests, you must include the API key in the `Authorization` request header. The format is `Authorization: api_xxxxxxxxxxxxxxxx`.
+
+Here's a sample API request using cURL:
+
+```bash
+curl --location 'https://app.documenso.com/api/v1/documents?page=1&perPage=1' \
+--header 'Authorization: api_xxxxxxxxxxxxxxxx'
+```
+
+Here's a sample response from the API based on the above cURL request:
+
+```json
+{
+  "documents": [
+    {
+      "id": 11,
+      "userId": 2,
+      "teamId": null,
+      "title": "documenso",
+      "status": "PENDING",
+      "documentDataId": "ab2ecm1npk11rt5sp398waf7h",
+      "createdAt": "2024-04-25T11:05:18.420Z",
+      "updatedAt": "2024-04-25T11:05:36.328Z",
+      "completedAt": null
+    }
+  ],
+  "totalPages": 1
+}
+```
+
+![A screenshot of a cURL request to the Documenso public API with the API key in the Authorization header](/public-api-images/documenso-api-authorization.webp)
+
+The API key has access to your account and all its resources. Please keep it secure and do not share it with others. If you suspect that your key has been compromised, you can revoke it from the API Tokens page in your user settings.
--- a/apps/documentation/pages/public-api/intro.mdx
+++ b/apps/documentation/pages/public-api/intro.mdx
@ -0,0 +1,22 @@
+---
+title: 'Public API'
+description: 'Learn how to interact with your documents programmatically using the Documenso public API.'
+---
+
+# Public API
+
+Documenso provides a public REST API that enables you to interact with your documents programmatically. The API exposes various HTTP endpoints that allow you to perform operations such as:
+
+- retrieving, uploading, deleting, and sending documents for signing
+- creating, updating, and deleting recipients
+- creating, updating, and deleting document fields
+
+The documentation walks you through creating API keys and using them to authenticate your API requests. You'll also learn about the available endpoints, request and response formats, and how to use the API.
+
+## Swagger Documentation
+
+There is also the [Swagger documentation](https://app.documenso.com/api/v1/openapi) available, which provides information about the API endpoints, request parameters, response formats, and authentication methods.
+
+## Availability
+
+The API is available to individual users and teams.
--- a/apps/documentation/pages/public-api/versioning.mdx
+++ b/apps/documentation/pages/public-api/versioning.mdx
@ -0,0 +1,18 @@
+---
+title: 'API Versioning'
+description: 'Versioning information for the Documenso public API.'
+---
+
+import { Callout } from 'nextra/components';
+
+# API Versioning
+
+Documenso uses API versioning to manage changes to the public API. This allows us to introduce new features, fix bugs, and make other changes without breaking existing integrations.
+
+<Callout type="info">The current version of the API is `v1`.</Callout>
+
+The API version is specified in the URL. For example, the base URL for the `v1` API is `https://app.documenso.com/api/v1`.
+
+We may make changes to the API without incrementing the version number. We will always try to avoid breaking changes, but in some cases, it may be necessary to make changes that are not backward compatible. In these cases, we will increment the version number and provide information about the changes in the release notes.
+
+Also, we may deprecate certain features or endpoints in the API. When we deprecate a feature or endpoint, we will provide information about the deprecation in the release notes and give a timeline for when the feature or endpoint will be removed.
--- a/apps/documentation/pages/webhooks/_meta.json
+++ b/apps/documentation/pages/webhooks/_meta.json
@ -0,0 +1,8 @@
+{
+  "intro": {
+    "title": "Get started",
+    "theme": {
+      "sidebar": false
+    }
+  }
+}
--- a/apps/documentation/pages/webhooks/intro.mdx
+++ b/apps/documentation/pages/webhooks/intro.mdx
@ -0,0 +1,350 @@
+---
+title: 'Webhooks'
+description: 'Learn how to use webhooks to receive real-time notifications about your documents.'
+---
+
+# Webhooks
+
+Webhooks are HTTP callbacks that are triggered by specific events. When the user subscribes to a specific event and that event occurs, the webhook makes an HTTP request to the URL provided by the user. The request can be a simple notification or can carry a payload with more information about the event.
+
+Some of the common use cases for webhooks include:
+
+1. **Real-time Data Syncing**: Webhooks provide a way to keep data in sync across different platforms. For example, you can keep your system up-to-date with your Documenso documents by subscribing to events like document creation or signing.
+2. **Automating Workflows**: They can trigger automated workflows that start when an event occurs. For example, the webhook could trigger an email when a document is signed.
+3. **Integrating Third-Party Services**: Webhooks can be used to integrate Documenso with third-party services. For example, you could use a webhook to send data to a CRM system when a document is signed.
+
+Documenso supports Webhooks and allows you to subscribe to the following events:
+
+- `document.created`
+- `document.sent`
+- `document.opened`
+- `document.signed`
+- `document.completed`
+
+## Create a webhook subscription
+
+You can create a webhook subscription from the user settings page. Click on your avatar in the top right corner of the dashboard and select "**[User settings](https://app.documenso.com/settings)**" from the dropdown menu.
+
+![A screenshot of the Documenso's dashboard that shows the dropdown menu when you click on your user avatar](/webhook-images/dashboard-user-dropdown-menu.webp)
+
+Then, navigate to the "**[Webhooks](https://app.documenso.com/settings/webhooks)**" tab, where you can see a list of your existing webhooks and create new ones.
+
+![A screenshot of the Documenso's user settings page that shows the Webhooks tab and the Create Webhook button](/webhook-images/webhooks-settings-page.webp)
+
+Clicking on the "**Create Webhook**" button opens a modal to create a new webhook subscription.
+
+To create a new webhook subscription, you need to provide the following information:
+
+- Enter the webhook URL that will receive the event payload.
+- Select the event(s) you want to subscribe to: `document.created`, `document.sent`, `document.opened`, `document.signed`, `document.completed`.
+- Optionally, you can provide a secret key that will be used to sign the payload. This key will be included in the `X-Documenso-Signature` header of the request.
+
+![A screenshot of the Create Webhook modal that shows the URL input field and the event checkboxes](/webhook-images/webhooks-page-create-webhook-modal.webp)
+
+After you have filled in the required information, click on the "**Create Webhook**" button to save your subscription.
+
+The screenshot below illustrates a newly created webhook subscription.
+
+![A screenshot of the Documenso's user settings page that shows the newly created webhook subscription](/webhook-images/webhooks-page.webp)
+
+You can edit or delete your webhook subscriptions by clicking the "**Edit**" or "**Delete**" buttons next to the webhook.
+
+## Webhook fields
+
+The payload sent to the webhook URL contains the following fields:
+
+| Field                                        | Type      | Description                                          |
+| -------------------------------------------- | --------- | ---------------------------------------------------- |
+| `event`                                      | string    | The type of event that triggered the webhook.        |
+| `payload.id`                                 | number    | The id of the document.                              |
+| `payload.userId`                             | number    | The id of the user who owns the document.            |
+| `payload.authOptions`                        | json?     | Authentication options for the document.             |
+| `payload.formValues`                         | json?     | Form values for the document.                        |
+| `payload.title`                              | string    | The name of the document.                            |
+| `payload.status`                             | string    | The current status of the document.                  |
+| `payload.documentDataId`                     | string    | The identifier for the document data.                |
+| `payload.createdAt`                          | datetime  | The creation date and time of the document.          |
+| `payload.updatedAt`                          | datetime  | The last update date and time of the document.       |
+| `payload.completedAt`                        | datetime? | The completion date and time of the document.        |
+| `payload.deletedAt`                          | datetime? | The deletion date and time of the document.          |
+| `payload.teamId`                             | number?   | The id of the team.                                  |
+| `payload.documentData.id`                    | string    | The id of the document data.                         |
+| `payload.documentData.type`                  | string    | The type of the document data.                       |
+| `payload.documentData.data`                  | string    | The data of the document.                            |
+| `payload.documentData.initialData`           | string    | The initial data of the document.                    |
+| `payload.Recipient[].id`                     | number    | The id of the recipient.                             |
+| `payload.Recipient[].documentId`             | number?   | The id the document associated with the recipient.   |
+| `payload.Recipient[].templateId`             | number?   | The template identifier for the recipient.           |
+| `payload.Recipient[].email`                  | string    | The email address of the recipient.                  |
+| `payload.Recipient[].name`                   | string    | The name of the recipient.                           |
+| `payload.Recipient[].token`                  | string    | The token associated with the recipient.             |
+| `payload.Recipient[].expired`                | datetime? | The expiration status of the recipient.              |
+| `payload.Recipient[].signedAt`               | datetime? | The date and time the recipient signed the document. |
+| `payload.Recipient[].authOptions.accessAuth` | json?     | Access authentication options.                       |
+| `payload.Recipient[].authOptions.actionAuth` | json?     | Action authentication options.                       |
+| `payload.Recipient[].role`                   | string    | The role of the recipient.                           |
+| `payload.Recipient[].readStatus`             | string    | The read status of the document by the recipient.    |
+| `payload.Recipient[].signingStatus`          | string    | The signing status of the recipient.                 |
+| `payload.Recipient[].sendStatus`             | string    | The send status of the document to the recipient.    |
+| `createdAt`                                  | datetime  | The creation date and time of the webhook event.     |
+| `webhookEndpoint`                            | string    | The endpoint URL where the webhook is sent.          |
+
+## Webhook event payload example
+
+When an event that you have subscribed to occurs, Documenso will send a POST request to the specified webhook URL with a payload containing information about the event.
+
+## Example payloads
+
+Below are examples of the payloads that are sent for each of the supported events. The payloads are sent as JSON data in the body of the POST request.
+
+Example payload for the `document.created` event:
+
+```json
+{
+  "event": "DOCUMENT_CREATED",
+  "payload": {
+    "id": 10,
+    "userId": 1,
+    "authOptions": null,
+    "formValues": null,
+    "title": "documenso.pdf",
+    "status": "DRAFT",
+    "documentDataId": "hs8qz1ktr9204jn7mg6c5dxy0",
+    "createdAt": "2024-04-22T11:44:43.341Z",
+    "updatedAt": "2024-04-22T11:44:43.341Z",
+    "completedAt": null,
+    "deletedAt": null,
+    "teamId": null
+  },
+  "createdAt": "2024-04-22T11:44:44.779Z",
+  "webhookEndpoint": "https://mywebhooksite.com/mywebhook"
+}
+```
+
+Example payload for the `document.sent` event:
+
+```json
+{
+  "event": "DOCUMENT_SENT",
+  "payload": {
+    "id": 10,
+    "userId": 1,
+    "authOptions": null,
+    "formValues": null,
+    "title": "documenso.pdf",
+    "status": "PENDING",
+    "documentDataId": "hs8qz1ktr9204jn7mg6c5dxy0",
+    "createdAt": "2024-04-22T11:44:43.341Z",
+    "updatedAt": "2024-04-22T11:48:07.569Z",
+    "completedAt": null,
+    "deletedAt": null,
+    "teamId": null,
+    "Recipient": [
+      {
+        "id": 52,
+        "documentId": 10,
+        "templateId": null,
+        "email": "signer2@documenso.com",
+        "name": "Signer 2",
+        "token": "vbT8hi3jKQmrFP_LN1WcS",
+        "expired": null,
+        "signedAt": null,
+        "authOptions": {
+          "accessAuth": null,
+          "actionAuth": null
+        },
+        "role": "VIEWER",
+        "readStatus": "NOT_OPENED",
+        "signingStatus": "NOT_SIGNED",
+        "sendStatus": "SENT"
+      },
+      {
+        "id": 53,
+        "documentId": 10,
+        "templateId": null,
+        "email": "signer1@documenso.com",
+        "name": "Signer 1",
+        "token": "HkrptwS42ZBXdRKj1TyUo",
+        "expired": null,
+        "signedAt": null,
+        "authOptions": {
+          "accessAuth": null,
+          "actionAuth": null
+        },
+        "role": "SIGNER",
+        "readStatus": "NOT_OPENED",
+        "signingStatus": "NOT_SIGNED",
+        "sendStatus": "SENT"
+      }
+    ]
+  },
+  "createdAt": "2024-04-22T11:48:07.945Z",
+  "webhookEndpoint": "https://mywebhooksite.com/mywebhook"
+}
+```
+
+Example payload for the `document.opened` event:
+
+```json
+{
+  "event": "DOCUMENT_OPENED",
+  "payload": {
+    "id": 10,
+    "userId": 1,
+    "authOptions": null,
+    "formValues": null,
+    "title": "documenso.pdf",
+    "status": "PENDING",
+    "documentDataId": "hs8qz1ktr9204jn7mg6c5dxy0",
+    "createdAt": "2024-04-22T11:44:43.341Z",
+    "updatedAt": "2024-04-22T11:48:07.569Z",
+    "completedAt": null,
+    "deletedAt": null,
+    "teamId": null,
+    "Recipient": [
+      {
+        "id": 52,
+        "documentId": 10,
+        "templateId": null,
+        "email": "signer2@documenso.com",
+        "name": "Signer 2",
+        "token": "vbT8hi3jKQmrFP_LN1WcS",
+        "expired": null,
+        "signedAt": null,
+        "authOptions": {
+          "accessAuth": null,
+          "actionAuth": null
+        },
+        "role": "VIEWER",
+        "readStatus": "OPENED",
+        "signingStatus": "NOT_SIGNED",
+        "sendStatus": "SENT"
+      }
+    ],
+    "documentData": {
+      "id": "hs8qz1ktr9204jn7mg6c5dxy0",
+      "type": "S3_PATH",
+      "data": "9753/xzqrshtlpokm/documenso.pdf",
+      "initialData": "9753/xzqrshtlpokm/documenso.pdf"
+    }
+  },
+  "createdAt": "2024-04-22T11:50:26.174Z",
+  "webhookEndpoint": "https://mywebhooksite.com/mywebhook"
+}
+```
+
+Example payload for the `document.signed` event:
+
+```json
+{
+  "event": "DOCUMENT_SIGNED",
+  "payload": {
+    "id": 10,
+    "userId": 1,
+    "authOptions": null,
+    "formValues": null,
+    "title": "documenso.pdf",
+    "status": "COMPLETED",
+    "documentDataId": "hs8qz1ktr9204jn7mg6c5dxy0",
+    "createdAt": "2024-04-22T11:44:43.341Z",
+    "updatedAt": "2024-04-22T11:52:05.708Z",
+    "completedAt": "2024-04-22T11:52:05.707Z",
+    "deletedAt": null,
+    "teamId": null,
+    "Recipient": [
+      {
+        "id": 51,
+        "documentId": 10,
+        "templateId": null,
+        "email": "signer1@documenso.com",
+        "name": "Signer 1",
+        "token": "HkrptwS42ZBXdRKj1TyUo",
+        "expired": null,
+        "signedAt": "2024-04-22T11:52:05.688Z",
+        "authOptions": {
+          "accessAuth": null,
+          "actionAuth": null
+        },
+        "role": "SIGNER",
+        "readStatus": "OPENED",
+        "signingStatus": "SIGNED",
+        "sendStatus": "SENT"
+      }
+    ]
+  },
+  "createdAt": "2024-04-22T11:52:18.577Z",
+  "webhookEndpoint": "https://mywebhooksite.com/mywebhook"
+}
+```
+
+Example payload for the `document.completed` event:
+
+```json
+{
+  "event": "DOCUMENT_COMPLETED",
+  "payload": {
+    "id": 10,
+    "userId": 1,
+    "authOptions": null,
+    "formValues": null,
+    "title": "documenso.pdf",
+    "status": "COMPLETED",
+    "documentDataId": "hs8qz1ktr9204jn7mg6c5dxy0",
+    "createdAt": "2024-04-22T11:44:43.341Z",
+    "updatedAt": "2024-04-22T11:52:05.708Z",
+    "completedAt": "2024-04-22T11:52:05.707Z",
+    "deletedAt": null,
+    "teamId": null,
+    "documentData": {
+      "id": "hs8qz1ktr9204jn7mg6c5dxy0",
+      "type": "S3_PATH",
+      "data": "bk9p1h7x0s3m/documenso-signed.pdf",
+      "initialData": "9753/xzqrshtlpokm/documenso.pdf"
+    },
+    "Recipient": [
+      {
+        "id": 50,
+        "documentId": 10,
+        "templateId": null,
+        "email": "signer2@documenso.com",
+        "name": "Signer 2",
+        "token": "vbT8hi3jKQmrFP_LN1WcS",
+        "expired": null,
+        "signedAt": "2024-04-22T11:51:10.055Z",
+        "authOptions": {
+          "accessAuth": null,
+          "actionAuth": null
+        },
+        "role": "VIEWER",
+        "readStatus": "OPENED",
+        "signingStatus": "SIGNED",
+        "sendStatus": "SENT"
+      },
+      {
+        "id": 51,
+        "documentId": 10,
+        "templateId": null,
+        "email": "signer1@documenso.com",
+        "name": "Signer 1",
+        "token": "HkrptwS42ZBXdRKj1TyUo",
+        "expired": null,
+        "signedAt": "2024-04-22T11:52:05.688Z",
+        "authOptions": {
+          "accessAuth": null,
+          "actionAuth": null
+        },
+        "role": "SIGNER",
+        "readStatus": "OPENED",
+        "signingStatus": "SIGNED",
+        "sendStatus": "SENT"
+      }
+    ]
+  },
+  "createdAt": "2024-04-22T11:52:18.277Z",
+  "webhookEndpoint": "https://mywebhooksite.com/mywebhook"
+}
+```
+
+## Availability
+
+Webhooks are available to individual users and teams.
--- a/apps/documentation/postcss.config.js
+++ b/apps/documentation/postcss.config.js
@ -0,0 +1,6 @@
+module.exports = {
+  plugins: {
+    tailwindcss: {},
+    autoprefixer: {},
+  },
+};
--- a/apps/documentation/public/pdf.worker.min.js
+++ b/apps/documentation/public/pdf.worker.min.js
--- a/apps/documentation/public/public-api-images/api-tokens-page-documenso.webp
+++ b/apps/documentation/public/public-api-images/api-tokens-page-documenso.webp
--- a/apps/documentation/public/public-api-images/documenso-api-authorization.webp
+++ b/apps/documentation/public/public-api-images/documenso-api-authorization.webp
--- a/apps/documentation/public/public-api-images/documenso-api-key-blurred.webp
+++ b/apps/documentation/public/public-api-images/documenso-api-key-blurred.webp
--- a/apps/documentation/public/public-api-images/documenso-api-key.webp
+++ b/apps/documentation/public/public-api-images/documenso-api-key.webp
--- a/apps/documentation/public/public-api-images/documenso-user-dropdown-menu.webp
+++ b/apps/documentation/public/public-api-images/documenso-user-dropdown-menu.webp
--- a/apps/documentation/public/webhook-images/dashboard-user-dropdown-menu.webp
+++ b/apps/documentation/public/webhook-images/dashboard-user-dropdown-menu.webp
--- a/apps/documentation/public/webhook-images/webhooks-page-create-webhook-modal.webp
+++ b/apps/documentation/public/webhook-images/webhooks-page-create-webhook-modal.webp
--- a/apps/documentation/public/webhook-images/webhooks-page.webp
+++ b/apps/documentation/public/webhook-images/webhooks-page.webp
--- a/apps/documentation/public/webhook-images/webhooks-settings-page.webp
+++ b/apps/documentation/public/webhook-images/webhooks-settings-page.webp
--- a/apps/documentation/styles.css
+++ b/apps/documentation/styles.css
@ -0,0 +1,3 @@
+@tailwind base;
+@tailwind components;
+@tailwind utilities;
--- a/apps/documentation/tailwind.config.ts
+++ b/apps/documentation/tailwind.config.ts
@ -0,0 +1,20 @@
+import type { Config } from "tailwindcss";
+
+const config: Config = {
+  content: [
+    "./pages/**/*.{js,ts,jsx,tsx,mdx}",
+    "./components/**/*.{js,ts,jsx,tsx,mdx}",
+    "./app/**/*.{js,ts,jsx,tsx,mdx}",
+  ],
+  theme: {
+    extend: {
+      backgroundImage: {
+        "gradient-radial": "radial-gradient(var(--tw-gradient-stops))",
+        "gradient-conic":
+          "conic-gradient(from 180deg at 50% 50%, var(--tw-gradient-stops))",
+      },
+    },
+  },
+  plugins: [],
+};
+export default config;
--- a/apps/documentation/theme.config.tsx
+++ b/apps/documentation/theme.config.tsx
@ -0,0 +1,49 @@
+import { useConfig } from 'nextra-theme-docs';
+import type { DocsThemeConfig } from 'nextra-theme-docs';
+
+const themeConfig: DocsThemeConfig = {
+  logo: <span>Documenso Docs</span>,
+  head: function useHead() {
+    const config = useConfig<{ title?: string; description?: string }>();
+
+    const title = `${config.frontMatter.title} | Documenso Docs` || 'Documenso Docs';
+    const description = config.frontMatter.description || 'The official Documenso documentation';
+
+    return (
+      <>
+        <meta httpEquiv="Content-Language" content="en" />
+        <meta name="title" content={title} />
+        <meta name="og:title" content={title} />
+        <meta name="description" content={description} />
+        <meta name="og:description" content={description} />
+      </>
+    );
+  },
+  project: {
+    link: 'https://documen.so/github',
+  },
+  chat: {
+    link: 'https://documen.so/discord',
+  },
+  docsRepositoryBase: 'https://github.com/documenso/documenso/tree/main/apps/documentation',
+  footer: {
+    text: (
+      <span>
+        {new Date().getFullYear()} ©{' '}
+        <a href="https://documen.so" target="_blank">
+          Documenso
+        </a>
+        .
+      </span>
+    ),
+  },
+  primaryHue: 100,
+  primarySaturation: 48.47,
+  useNextSeoProps() {
+    return {
+      titleTemplate: '%s | Documenso Docs',
+    };
+  },
+};
+
+export default themeConfig;
--- a/apps/documentation/tsconfig.json
+++ b/apps/documentation/tsconfig.json
@ -0,0 +1,27 @@
+{
+  "compilerOptions": {
+    "lib": ["dom", "dom.iterable", "esnext"],
+    "allowJs": true,
+    "skipLibCheck": true,
+    "strict": true,
+    "noEmit": true,
+    "esModuleInterop": true,
+    "module": "esnext",
+    "moduleResolution": "node",
+    "resolveJsonModule": true,
+    "isolatedModules": true,
+    "jsx": "preserve",
+    "incremental": true,
+    "plugins": [
+      {
+        "name": "next"
+      }
+    ],
+    "paths": {
+      "@/*": ["./*"]
+    },
+    "forceConsistentCasingInFileNames": true
+  },
+  "include": ["next-env.d.ts", "**/*.ts", "**/*.tsx", ".next/types/**/*.ts"],
+  "exclude": ["node_modules"]
+}
--- a/package-lock.json
+++ b/package-lock.json
--- a/package.json
+++ b/package.json
@ -3,8 +3,8 @@
  "scripts": {
    "build": "turbo run build",
    "build:web": "turbo run build --filter=@documenso/web",
-    "dev": "turbo run dev --filter=@documenso/web --filter=@documenso/marketing",
-    "start": "turbo run start --filter=@documenso/web --filter=@documenso/marketing",
+    "dev": "turbo run dev --filter=@documenso/web --filter=@documenso/marketing --filter=@documenso/documentation",
+    "start": "turbo run start --filter=@documenso/web --filter=@documenso/marketing --filter=@documenso/documentation",
    "lint": "turbo run lint",
    "lint:fix": "turbo run lint:fix",
    "format": "prettier --write \"**/*.{js,jsx,cjs,mjs,ts,tsx,cts,mts,mdx}\"",
--- a/packages/lib/server-only/document/resend-document.tsx
+++ b/packages/lib/server-only/document/resend-document.tsx
@ -110,7 +110,7 @@ export const resendDocument = async ({
        assetBaseUrl,
        signDocumentLink,
        customBody: renderCustomEmailTemplate(
-          selfSigner ? selfSignerCustomEmail : customEmail?.message || '',
+          selfSigner && !customEmail?.message ? selfSignerCustomEmail : customEmail?.message || '',
          customEmailTemplate,
        ),
        role: recipient.role,
--- a/packages/lib/server-only/document/send-document.tsx
+++ b/packages/lib/server-only/document/send-document.tsx
@ -149,7 +149,7 @@ export const sendDocument = async ({
        assetBaseUrl,
        signDocumentLink,
        customBody: renderCustomEmailTemplate(
-          selfSigner ? selfSignerCustomEmail : customEmail?.message || '',
+          selfSigner && !customEmail?.message ? selfSignerCustomEmail : customEmail?.message || '',
          customEmailTemplate,
        ),
        role: recipient.role,
Author	SHA1	Message	Date
Catalin Pit	c63047a049	fix: custom email message for self-signers	2024-04-26 17:15:19 +03:00
Catalin Pit	882d569992	chore: fix contributing guide	2024-04-26 16:35:56 +03:00
Catalin Pit	4de2cb10e0	chore: remove list from gitpod page	2024-04-26 15:41:05 +03:00
Catalin Pit	d7f2767377	Merge branch 'main' into feat/create-documentation-site	2024-04-26 15:39:14 +03:00
Catalin Pit	1387ce11f9	chore: lots of content updates	2024-04-26 15:35:53 +03:00
Catalin Pit	885809603a	chore: added versioning information	2024-04-26 10:47:13 +03:00
Catalin Pit	5a9ac21443	chore: content updates	2024-04-26 10:25:16 +03:00
Catalin Pit	c7beda4dd2	chore: finish api auth section	2024-04-25 14:39:04 +03:00
Catalin Pit	39d2630714	chore: started api documentation	2024-04-25 12:07:50 +03:00
Catalin Pit	47d1febad7	chore: added webhook fields documentation	2024-04-25 09:46:54 +03:00
Catalin Pit	442e88cff8	chore: added webhooks content and updated home page	2024-04-22 16:58:00 +03:00
Catalin Pit	2ed4cb636b	chore: improved contributing copy	2024-04-22 12:03:45 +03:00
Catalin Pit	bd82d46ecd	chore: add contributing guide	2024-04-15 11:12:24 +03:00
Catalin Pit	86df82dc9f	chore: hide home from nav	2024-04-12 15:16:49 +03:00
Catalin Pit	c29e6ea861	chore: added frontmatter plus some changes	2024-04-12 14:40:39 +03:00
Catalin Pit	1f71baaffb	chore: some changes	2024-04-12 13:41:52 +03:00
Catalin Pit	df699e890c	chore: added content and updated settings	2024-04-12 12:05:31 +03:00
Catalin Pit	24ed73ef3e	chore: add package.json commands	2024-04-11 20:22:27 +03:00
Catalin Pit	23c4054d23	fix: app name	2024-04-11 20:15:50 +03:00
Catalin Pit	b105be2305	fix: invalid key	2024-04-11 17:01:58 +03:00
Catalin Pit	5799e366d1	feat: documentation site	2024-04-11 16:44:22 +03:00