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.

Invitaciones Digitales is a Next.js 16 static-export platform that creates beautiful, fully animated digital invitations for Spanish-language celebrations. Each invitation is a standalone, personalized web experience — complete with photo galleries, countdown timers, RSVP sections, background music, and interactive maps — deployed and publicly accessible at invitaciones.unaideamas.com.

The Problem It Solves

Traditional paper invitations are expensive to print, impossible to update after distribution, and offer no interactivity. Invitaciones Digitales replaces them with rich, mobile-first web experiences that guests open instantly on any device. Couples, families, and schools get a shareable URL instead of an envelope — one that can include embedded video, animated countdowns, gift registries, and a live Google Maps pin, all without any app download.

Event Categories

The platform organizes invitations into five event categories, each with its own URL namespace under the root domain.

Bodas — Weddings

Wedding invitations at /bodas/[couple]/. Includes ceremony and reception details, dress code, gift registry, and a full photo gallery for the couple.

Quinceañeras — Quinces

Quinceañera invitations at /quinces/[name]/. Features godparent listings, animated presentations, gallery carousels, and RSVP confirmations.

Bautizos — Baptisms

Baptism invitations at /bautizos/[name]/. Covers ceremony venue, godparents, and celebration reception details in a soft, celebratory layout.

Escolar — Graduations

School graduation invitations at /escolar/[name]/. Supports kindergartens, primary schools, secondary schools, and high schools. A parallel /escolar-2026/ namespace covers upcoming 2026 ceremonies.

Festejos — Celebrations

General celebration invitations at /festejos/[name]/. Suitable for birthdays, first communions, anniversaries, and other milestone events.

Technology Stack

Invitaciones Digitales is built on a carefully chosen set of libraries that handle animation, media display, UI, and smooth scrolling.
LibraryVersionPurpose
Next.js16.2.6App Router, static export
React19.xComponent model
Framer Motion12.xSection entrance animations
Swiper12.xTouch-friendly slide carousels
@splidejs/react-splide0.7.xAlternative carousel/slider
react-photo-album3.xResponsive photo grid layouts
yet-another-react-lightbox3.xFull-screen image lightbox
react-spring-lightbox1.xSpring-animated image lightbox
NextUI2.xAccessible UI components
Flowbite / flowbite-react4.x / 0.12.xAdditional UI elements
Tailwind CSS3.xUtility-first styling
Lenis1.xSmooth scroll behavior
react-canvas-confetti2.xCelebratory confetti effects
@number-flow/react0.6.xAnimated number counters
react-player2.xEmbedded video playback
react-icons5.xIcon library
styled-components6.xCSS-in-JS component styling

How It Works

Every invitation follows the same three-layer pattern:
  1. Route — Each invitation is a dedicated Next.js App Router route under its category, for example src/app/quinces/daniela/. The route’s page.tsx renders a single root component (<Main />), which composes all invitation sections in order.
  2. Components — Each invitation ships its own components/ folder containing isolated section files (Header.tsx, Ceremony.tsx, Gallery.tsx, Confirm.tsx, etc.), a shared Animations.ts file with Framer Motion variants, and a Fonts.ts file for per-invitation next/font configurations.
  3. Assets — Images, audio files, and other media for each invitation are stored in public/img/[category]/[name]/. For example, all photos for daniela live in public/img/quinces/daniela/. Background music tracks are stored in public/media/. Custom decorative fonts shared across invitations are placed in public/fonts/.
At build time, Next.js crawls every route and emits a static HTML file for each one into the out/ directory. The result is a zero-server deployment that can be hosted on any static CDN.
All routes in this application produce static HTML at build time. There is no server-side data fetching, no API routes, and no runtime Node.js process. Invitation content (dates, names, venues, images) is hardcoded directly into each route’s component files. Updates require a new build and redeployment.

Build docs developers (and LLMs) love