Skip to main content

Documentation Index

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

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

GCS Centros Estratégicos is a standard Next.js 16 application designed to deploy on Vercel. It includes Vercel Analytics out of the box — enabled automatically in production with zero configuration — and can be embedded as an iframe in any CMS, including WordPress/DIVI, making it straightforward to surface the virtual office inside an existing corporate website.

​
Deploy to Vercel

The fastest path to production is a direct import from GitHub into Vercel. The entire process takes under five minutes once your environment variables are ready.
1

Push the repository to GitHub

The source code lives at github.com/gcsconsultores/centros-estrategicos-gcs. If you are working on a fork, push your branch before importing.
2

Import the repository into Vercel

Go to vercel.com/new and click Import next to the centros-estrategicos-gcs repository.
3

Verify the framework preset

Vercel auto-detects Next.js and pre-fills the build and output settings. No manual changes are needed here.
4

Add all required environment variables

Before clicking Deploy, expand the Environment Variables section and add every variable listed in the Environment Variables reference. Skipping this step will cause the build to succeed but Sally’s chat and Microsoft 365 integrations will not work in production.
5

Click Deploy

Vercel builds the project with next build and publishes it. The first build typically completes in two to three minutes.
6

Access your deployment URL

Vercel assigns a default URL such as https://centros-estrategicos-gcs.vercel.app. You can add a custom domain at any time from Settings → Domains.

​
Build Configuration

The project ships with four npm scripts that cover the full development and production lifecycle. 
{
  "scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "next start",
    "lint": "eslint ."
  }
}
Vercel runs next build automatically on every push to the production branch. next start serves the optimised production build when self-hosting. No special vercel.json or custom build configuration is required — the defaults in next.config.mjs are sufficient for a Vercel deployment.
next.config.mjs sets typescript.ignoreBuildErrors: true and images.unoptimized: true. This means TypeScript errors will not block CI builds and images are served as-is without Vercel’s Image Optimisation API. Both settings can be tightened once the codebase reaches production stability.

​
Vercel Analytics

@vercel/analytics (v1.6.1) is installed as a production dependency and wired into the root layout. It loads only when NODE_ENV equals production, so local development and preview builds are never polluted with analytics traffic. 
// app/layout.tsx — Analytics component only loads in production
{process.env.NODE_ENV === 'production' && <Analytics />}
No additional configuration is needed. Once the first production deployment receives traffic, page-view data appears automatically in the Analytics tab of your Vercel project dashboard.

​
Custom Domain

1

Open Vercel project settings

In your Vercel dashboard, navigate to the project and click Settings → Domains.
2

Add your domain

Type in your desired domain — for example, oficina.consultoresgcs.com — and click Add.
3

Update DNS records

Vercel displays a CNAME or A record value. Log in to your DNS provider and add the record exactly as shown.
4

Wait for SSL provisioning

Vercel provisions a TLS certificate via Let’s Encrypt automatically once DNS propagates. No manual certificate management is required.

​
WordPress / DIVI Embedding

The virtual office is designed to run inside an <iframe>, making it easy to embed on any WordPress page or DIVI layout without modifying the Next.js app. Add the following snippet to a DIVI Code Module or a WordPress Custom HTML block on the page where you want the office to appear: 
<!-- Add to a DIVI Code Module or WordPress Custom HTML block -->
<iframe 
  src="https://oficina.tudominio.com"
  width="100%"
  height="900px"
  frameborder="0"
  allow="camera; microphone; fullscreen"
  style="border: none; border-radius: 8px;">
</iframe>
A few things to keep in mind when embedding:
  • Replace https://oficina.tudominio.com with your actual Vercel deployment URL or custom domain.
  • Adjust height to suit your layout. 900px works well for most desktop views; consider 700px for pages with a fixed header or sidebar.
  • The allow attribute enables microphone access (reserved for future voice features) and the browser’s native fullscreen API.
  • DIVI’s Fullwidth Section type gives the iframe the most horizontal space and the best visual result.

​
Production Checklist

Work through each item before announcing the virtual office to clients.
  • ✅ All environment variables set in the Vercel dashboard
  • ✅ Azure AD app registration created with the correct Microsoft Graph API permissions
  • ✅ SharePoint list created with all required columns for lead storage
  • ✅ DEFAULT_ORGANIZER_EMAIL set to a licensed Microsoft 365 user with Teams meeting creation rights
  • ✅ Custom domain configured and SSL certificate issued (if applicable)
  • ✅ Test lead capture: submit a contact form and verify the item appears in the SharePoint list
  • ✅ Test meeting creation: schedule a meeting through the Sala Ejecutiva and verify the Teams join URL is real
  • ✅ Test Sally chat: open the chat panel and verify streaming responses arrive from Gemini
NODE_ENV=production is set automatically by Vercel for every production deployment. Do not manually override it in your environment variables — doing so can break the analytics conditional, session handling, and other production-only behaviour.
Use Vercel Preview Deployments to test changes before merging to your production branch. Set the environment variable scope to Preview (in addition to Production) so that preview builds have full access to Microsoft 365 services and you can validate the complete integration before going live.

Build docs developers (and LLMs) love

Get started for freeTalk to us