next-forge Documentation

File: README.md Copy Chapter

▲ / next-forge

Production-grade Turborepo template for Next.js apps.

Overview Copy Chapter

next-forge is a production-grade Turborepo template for Next.js apps. It's designed to be a comprehensive starting point for building SaaS applications, providing a solid, opinionated foundation with minimal configuration required.

Built on a decade of experience building web applications, next-forge balances speed and quality to help you ship thoroughly-built products faster.

Philosophy Copy Section

next-forge is built around five core principles:

• Fast — Quick to build, run, deploy, and iterate on
• Cheap — Free to start with services that scale with you
• Opinionated — Integrated tooling designed to work together
• Modern — Latest stable features with healthy community support
• Safe — End-to-end type safety and robust security posture

Demo Copy Chapter

Experience next-forge in action:

• Web — Marketing website
• App — Main application
• Storybook — Component library
• API — API health check

Features Copy Chapter

next-forge comes with batteries included:

Apps Copy Section

• Web — Marketing site built with Tailwind CSS and TWBlocks
• App — Main application with authentication and database integration
• API — RESTful API with health checks and monitoring
• Docs — Documentation site powered by Mintlify
• Email — Email templates with React Email
• Storybook — Component development environment

Packages Copy Section

• Authentication — Powered by Clerk
• Database — Type-safe ORM with migrations
• Design System — Comprehensive component library with dark mode
• Payments — Subscription management via Stripe
• Email — Transactional emails via Resend
• Analytics — Web (Google Analytics) and product (Posthog)
• Observability — Error tracking (Sentry), logging, and uptime monitoring (BetterStack)
• Security — Application security (Arcjet), rate limiting, and secure headers
• CMS — Type-safe content management for blogs and documentation
• SEO — Metadata management, sitemaps, and JSON-LD
• AI — AI integration utilities
• Webhooks — Inbound and outbound webhook handling
• Collaboration — Real-time features with avatars and live cursors
• Feature Flags — Feature flag management
• Cron — Scheduled job management
• Storage — File upload and management
• Internationalization — Multi-language support
• Notifications — In-app notification system

Getting Started Copy Chapter

Prerequisites Copy Section

• Node.js 20+
• Bun (or npm/yarn/pnpm)
• Stripe CLI for local webhook testing

Installation Copy Section

Create a new next-forge project:

npx next-forge@latest init

Setup Copy Section

1. Configure your environment variables
2. Set up required service accounts (Clerk, Stripe, Resend, etc.)
3. Run the development server

For detailed setup instructions, read the documentation.

Structure Copy Chapter

next-forge uses a monorepo structure managed by Turborepo:

next-forge/
├── apps/           # Deployable applications
│   ├── web/        # Marketing website (port 3001)
│   ├── app/        # Main application (port 3000)
│   ├── api/        # API server
│   ├── docs/       # Documentation
│   ├── email/      # Email templates
│   └── storybook/  # Component library
└── packages/       # Shared packages
    ├── design-system/
    ├── database/
    ├── auth/
    └── ...

Each app is self-contained and independently deployable. Packages are shared across apps for consistency and maintainability.

Documentation Copy Chapter

Full documentation is available at next-forge.com/docs, including:

• Detailed setup guides
• Package documentation
• Migration guides for swapping providers
• Deployment instructions
• Examples and recipes

Contributing Copy Chapter

We welcome contributions! See the contributing guide for details.

Contributors Copy Chapter

Made with contrib.rocks.

License Copy Chapter

MIT

File: apps/storybook/README.md Copy Chapter

This is a Next.js project bootstrapped with create-next-app.

Getting Started Copy Chapter

First, run the development server:

bun dev
# or
npm run dev
# or
yarn dev
# or
pnpm dev

Open http://localhost:3000 with your browser to see the result.

You can start editing the page by modifying pages/index.tsx. The page auto-updates as you edit the file.

API routes can be accessed on http://localhost:3000/api/hello. This endpoint can be edited in pages/api/hello.ts.

The pages/api directory is mapped to /api/*. Files in this directory are treated as API routes instead of React pages.

This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.

Learn More Copy Chapter

To learn more about Next.js, take a look at the following resources:

• Next.js Documentation - learn about Next.js features and API.
• Learn Next.js - an interactive Next.js tutorial.

You can check out the Next.js GitHub repository - your feedback and contributions are welcome!

Deploy on Vercel Copy Chapter

The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.

Check out our Next.js deployment documentation for more details.

File: apps/docs/api-reference/introduction.mdx Copy Chapter

title: 'Introduction' Copy Chapter

Welcome Copy Chapter

There are two ways to build API documentation: OpenAPI and MDX components. For the starter kit, we are using the following OpenAPI specification.

<Card
title="Plant Store Endpoints"
icon="leaf"
href="https://github.com/mintlify/starter/blob/main/api-reference/openapi.json"

View the OpenAPI specification file

Authentication Copy Chapter

All API endpoints are authenticated using Bearer tokens and picked up from the specification file.

"security": [
  {
    "bearerAuth": []
  }
]

File: apps/docs/essentials/code.mdx Copy Chapter

title: 'Code Blocks' icon: 'code' Copy Chapter

Basic Copy Chapter

Inline Code Copy Section

To denote a word or phrase as code, enclose it in backticks (`).

To denote a `word` or `phrase` as code, enclose it in backticks (`).

Code Block Copy Section

Use fenced code blocks by enclosing code in three backticks and follow the leading ticks with the programming language of your snippet to get syntax highlighting. Optionally, you can also write the name of your code after the programming language.

class HelloWorld {
    public static void main(String[] args) {
        System.out.println("Hello, World!");
    }
}

```java HelloWorld.java
class HelloWorld {
    public static void main(String[] args) {
        System.out.println("Hello, World!");
    }
}
```

File: apps/docs/essentials/images.mdx Copy Chapter

title: 'Images and Embeds' icon: 'image' Copy Chapter

Image Copy Chapter

Using Markdown Copy Section

The markdown syntax lets you add images using the following code

Note that the image file size must be less than 5MB. Otherwise, we recommend hosting on a service like Cloudinary or S3. You can then use that URL and embed.

Using Embeds Copy Section

To get more customizability with images, you can also use embeds to add images

Embeds and HTML elements Copy Chapter

iFrames Copy Section

Loads another HTML page within the document. Most commonly used for embedding videos.

File: apps/docs/essentials/markdown.mdx Copy Chapter

title: 'Markdown Syntax' icon: 'text-size' Copy Chapter

Titles Copy Chapter

Best used for section headers.

## Titles

Subtitles Copy Section

Best use to subsection headers.

### Subtitles

Text Formatting Copy Chapter

We support most markdown formatting. Simply add **, _, or ~ around text to format it.

You can combine these. For example, write **_bold and italic_** to get bold and italic text.

You need to use HTML to write superscript and subscript text. That is, add <sup> or <sub> around your text.

Linking to Pages Copy Chapter

You can add a link by wrapping text in [](). You would write [link to google](https://google.com) to link to google.

Links to pages in your docs need to be root-relative. Basically, you should include the entire folder path. For example, [link to text](/writing-content/text) links to the page "Text" in our components section.

Relative links like [link to text](../text) will open slower because we cannot optimize them as easily.

Blockquotes Copy Chapter

Singleline Copy Section

To create a blockquote, add a > in front of a paragraph.

Dorothy followed her through many of the beautiful rooms in her castle.

> Dorothy followed her through many of the beautiful rooms in her castle.

Multiline Copy Section

Dorothy followed her through many of the beautiful rooms in her castle.

The Witch bade her clean the pots and kettles and sweep the floor and keep the fire fed with wood.

> Dorothy followed her through many of the beautiful rooms in her castle.
>
> The Witch bade her clean the pots and kettles and sweep the floor and keep the fire fed with wood.

LaTeX Copy Section

Mintlify supports LaTeX through the Latex component.

8 x (vk x H1 - H2) = (0,1)

<Latex>8 x (vk x H1 - H2) = (0,1)</Latex>

File: apps/docs/essentials/navigation.mdx Copy Chapter

title: 'Navigation' icon: 'map' Copy Chapter

The navigation menu is the list of links on every website.

You will likely update mint.json every time you add a new page. Pages do not show up automatically.

Navigation syntax Copy Chapter

Our navigation syntax is recursive which means you can make nested navigation groups. You don't need to include .mdx in page names.

"navigation": [
    {
        "group": "Getting Started",
        "pages": ["quickstart"]
    }
]

"navigation": [
    {
        "group": "Getting Started",
        "pages": [
            "quickstart",
            {
                "group": "Nested Reference Pages",
                "pages": ["nested-reference-page"]
            }
        ]
    }
]

Folders Copy Chapter

Simply put your MDX files in folders and update the paths in mint.json.

For example, to have a page at https://yoursite.com/your-folder/your-page you would make a folder called your-folder containing an MDX file called your-page.mdx.

"navigation": [
    {
        "group": "Group Name",
        "pages": ["your-folder/your-page"]
    }
]

Hidden Pages Copy Chapter

MDX files not included in mint.json will not show up in the sidebar but are accessible through the search bar and by linking directly to them.