Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/luislopez-stack/landing-pages/llms.txt

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

Vercel is the recommended hosting platform for this template — the original portfolio is live at soumyajit.vercel.app and serves as the canonical live reference. Vercel automatically detects Create React App projects, sets the correct build command and output directory without any manual configuration, provisions HTTPS on every domain, and generates a unique preview URL for every branch push or pull request.

Prerequisites

Before deploying, make sure you have the following in place:
  • A GitHub, GitLab, or Bitbucket account with the landing-pages repository pushed to a remote.
  • A Vercel account — sign up at vercel.com. The free Hobby tier is sufficient for personal portfolios.

Deploy via Vercel dashboard

The dashboard is the quickest path from repo to live URL.
1

Create a new Vercel project

Go to vercel.com/new and click Add New Project. Sign in with your Git provider if prompted.
2

Import the repository

Find the landing-pages repository in the list and click Import. Grant Vercel access to the repo if this is your first time connecting it.
3

Confirm the build settings

Vercel automatically detects Create React App and pre-fills the correct settings. Verify the following values and leave them unchanged:
SettingValue
Framework PresetCreate React App
Build Commandnpm run build
Output Directorybuild
Install Commandnpm install
If you have environment variables to inject at build time, add them under Environment Variables on this screen before clicking Deploy.
4

Deploy

Click Deploy. Vercel installs dependencies, runs npm run build, and uploads the build/ directory to its global edge network. Once the build finishes you will receive a *.vercel.app URL — your site is live.

Deploy via Vercel CLI

If you prefer working in the terminal, the Vercel CLI provides the same functionality without leaving your editor. Install the CLI globally:
npm install -g vercel
Run the following command from the project root to launch the interactive setup wizard. It will ask for your Vercel account, project name, and whether to link to an existing project:
vercel
The CLI deploys to a preview URL by default. When you are ready to push to the production domain, run:
vercel --prod
Re-running vercel --prod on subsequent deploys skips the setup wizard and goes straight to building and deploying because the project is already linked.

Custom domain

To serve the site from your own domain instead of *.vercel.app:
  1. Open your project in the Vercel dashboard and navigate to Settings > Domains.
  2. Enter your domain (e.g. www.myportfolio.com) and click Add.
  3. Vercel displays the DNS records you need to create — either an A record or a CNAME record depending on whether you are using an apex domain or a subdomain.
  4. Log in to your domain registrar and add those DNS records. Propagation typically takes a few minutes to an hour.
  5. Vercel automatically provisions and renews a free TLS/SSL certificate via Let’s Encrypt once DNS propagation is confirmed. No manual certificate management is required.

Environment variables on Vercel

REACT_APP_* environment variables are embedded into the JavaScript bundle at build time, not at runtime. Set them in the Vercel dashboard so they are available during every build:
  1. In your project, go to Settings > Environment Variables.
  2. Add each variable with its name (e.g. REACT_APP_CONTACT_EMAIL) and value.
  3. Select which environments the variable applies to: Production, Preview, and/or Development.
  4. Click Save, then trigger a new deployment — the variable will be baked into the next build.
Because these values are embedded at build time, they are visible in the compiled JavaScript bundle. Never store private API keys or passwords in REACT_APP_* variables. Use server-side secrets management for sensitive credentials.

Automatic deploys

Once the repository is connected to Vercel, deployments are fully automated:
  • Production deploys — every push to the main branch (or whichever branch you designate as production) triggers a fresh build and deploys to your production URL.
  • Preview deploys — every push to any other branch, and every pull request, generates an isolated preview URL (e.g. landing-pages-git-feature-xyz.vercel.app). Share these links with collaborators for review before merging.
  • Instant rollbacks — if a deploy introduces a problem, you can roll back to any previous deployment in one click from the Deployments tab in the dashboard.
The original Soumyajit Landing Pages template is deployed and publicly accessible at https://soumyajit.vercel.app/. You can use it as a live reference to compare your own deployment’s appearance and behaviour before going live.
Before deploying to a public URL, personalise the site’s branding — name, colours, social links, and section content. See the Branding & Customization guide for a full walkthrough.

Build docs developers (and LLMs) love