Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/gus-16710/invitations/llms.txt

Use this file to discover all available pages before exploring further.

This guide walks you through cloning the repository, installing dependencies, and opening a live invitation preview in your local browser. By the end you will have a fully functional development server running and understand how to build the project for static deployment — all in under five minutes.

Prerequisites

Before you begin, make sure you have the following installed:
  • Node.js 18 or laternodejs.org/en/download
  • npm (bundled with Node.js) or an alternative package manager (yarn, pnpm, or bun)
You can verify your Node.js version with:
node --version

Setup Steps

1

Clone the repository

Clone the project from GitHub and navigate into the project directory:
git clone https://github.com/gus-16710/invitations.git && cd invitations
2

Install dependencies

Install all required packages using your preferred package manager:
npm install
This installs Next.js 16, React 19, Framer Motion, Swiper, NextUI, Tailwind CSS, Lenis, and all other dependencies listed in package.json.
3

Start the development server

Launch the Next.js development server:
npm run dev
The server starts on http://localhost:3000. You will see the platform’s landing page, which showcases all available invitation categories with a live confetti demo and an animated feature overview.
4

Open an existing invitation

Navigate directly to any invitation route in your browser. Here are several examples you can try immediately:Each URL loads a fully self-contained invitation page with its own fonts, animations, photo gallery, and section layout.
trailingSlash: true is enabled in next.config.js, so every URL ends with a /. The dev server handles both forms transparently, but the production static build requires the trailing slash for correct asset resolution.
5

Build for production

When you are ready to deploy, generate the full static export:
npm run build
Next.js crawls every route in the app and emits a complete set of static HTML, CSS, and JavaScript files into the out/ directory at the project root. The contents of out/ can be deployed to any static hosting provider (Vercel, Netlify, Cloudflare Pages, S3, etc.) with zero server configuration.
images.unoptimized: true is set in next.config.js. This is required for static export because Next.js’s built-in image optimization relies on a server-side API route, which is unavailable in output: 'export' mode. All <Image /> components render standard <img> tags at build time.

Available Scripts

The following npm scripts are defined in package.json:
ScriptCommandDescription
Development servernpm run devStarts Next.js in development mode with hot reload at http://localhost:3000
Production buildnpm run buildRuns next build and outputs static files to the out/ directory
Production servernpm run startStarts a Next.js server for local testing (requires a standard build, not the static out/ export)
Linternpm run lintRuns ESLint across the codebase using Next.js’s built-in ESLint configuration

Build docs developers (and LLMs) love