Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/gcsconsultores/gcs-website/llms.txt

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

This guide walks you through cloning the GCS Consultores Empresariales website repository, installing dependencies, configuring the required environment variables, and launching the local development server. By the end you will have the full Next.js 16 application — including the Sally AI assistant, the CRM lead form, and all six strategic centers — running at http://localhost:3000.

​
Prerequisites

Before you begin, make sure the following are available on your machine:
  • Node.js 18+ — The app targets the Node.js runtime expected by Next.js 16. Use nvm or fnm to manage versions.
  • pnpm — Preferred package manager; a pnpm-lock.yaml lockfile is committed to the repository. npm and Yarn are also supported.
  • Git — Required to clone the repository.

​
Setup Steps

1

Clone the repository

Clone the project from GitHub and change into the project directory:
git clone https://github.com/gcsconsultores/gcs-website.git
cd gcs-website
2

Install dependencies

Install all Node.js dependencies. pnpm is recommended because the committed lockfile (pnpm-lock.yaml) guarantees reproducible installs.
pnpm install
pnpm-lock.yaml is the source of truth for dependency resolution. If you install with npm or Yarn, your local node_modules may differ from the CI/Vercel environment. Always use pnpm when contributing to keep the lockfile consistent.
3

Configure environment variables

Create a .env.local file at the project root. The site reads the following variables at build time and runtime:
# .env.local

# CRM integration — required in production to receive leads from the contact form
CRM_API_URL=https://your-crm-endpoint.example.com/api
CRM_API_KEY=your_crm_api_key_here
VariableRequiredPurpose
CRM_API_URLProduction onlyBase URL for the CRM lead submission API
CRM_API_KEYProduction onlyAuthentication key for the CRM API
CRM_API_URL and CRM_API_KEY are optional during local development — the contact form will still render and validate, but lead submissions will fail gracefully without a connected CRM endpoint. The Sally AI assistant relies on the Vercel AI Gateway, which is zero-config in Vercel and v0 environments. For production deployments outside Vercel, you must supply the appropriate AI Gateway credentials separately.
4

Start the development server

Launch the Next.js development server with hot module replacement:
pnpm dev
Once the server starts, open your browser and navigate to:
http://localhost:3000
You should see the GCS Consultores Empresariales homepage with the Hero section, Solutions, Sectors, Strategic Centers, Insights, and the Sally AI chat widget active in the bottom corner.

​
Available Scripts

All scripts are defined in package.json and can be run with pnpm, npm, or Yarn: 
{
  "scripts": {
    "dev":   "next dev",
    "build": "next build",
    "start": "next start",
    "lint":  "eslint ."
  }
}
ScriptCommandDescription
devpnpm devStarts Next.js in development mode with HMR at localhost:3000
buildpnpm buildCompiles and optimizes the application for production
startpnpm startRuns the production build (requires build first)
lintpnpm lintRuns ESLint across the entire project
The project sets typescript.ignoreBuildErrors: true in next.config.mjs. This means pnpm build will succeed even if TypeScript errors are present. Run tsc --noEmit separately to surface type errors before opening a pull request.

​
Next Steps

Architecture

Deep-dive into the component-oriented page structure, the App Router layout, and how sections are assembled in app/page.tsx.

Site Data

Understand the single-source-of-truth pattern in lib/site-data.ts and learn how to add or modify content without touching JSX.

Build docs developers (and LLMs) love

Get started for freeTalk to us