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.

Because Soumyajit Landing Pages is a standard Create React App project (powered by react-scripts 5.0.0), getting it production-ready is a single command. Running npm run build invokes Babel and Webpack in production mode, minifies all JavaScript and CSS, and writes the fully self-contained static site to the build/ directory — no server-side runtime required. Any host that can serve static files can run this template.

​
Building for production

1

Run the production build

From the project root, execute the build script:
npm run build
Create React App runs Babel to transpile modern JavaScript, Webpack to bundle and tree-shake modules, and applies production-mode minification and chunk-hashing to all JS and CSS outputs. The compiled artefacts are written to the build/ directory.
2

Inspect the build output

After a successful build the build/ directory contains everything the browser needs:
  • build/index.html — the single HTML entry point with injected script and link tags.
  • build/static/js/ — hashed JS bundles (main chunk, vendors chunk, runtime chunk).
  • build/static/css/ — hashed CSS bundles.
  • build/static/media/ — imported images and fonts that exceeded the inline threshold.
  • build/favicon.png and other public-folder assets copied verbatim.
No build step is needed again until you change source files.
3

Upload build/ to your static host

Deploy the build/ directory to any static-file hosting service. Popular choices that work with zero additional configuration include:
  • Vercel — automatic CRA detection, HTTPS, and deploy previews.
  • Netlify — drag-and-drop or Git-connected deployments.
  • GitHub Pages — free hosting for public repositories via the gh-pages package.
  • AWS S3 + CloudFront — scalable object storage with a global CDN.
  • Firebase Hosting — fast CDN-backed hosting with Firebase integration.

​
Build output

The directory structure produced by npm run build looks like this: 
build/
├── index.html
├── static/
│   ├── css/
│   ├── js/
│   └── media/
└── favicon.png
All filenames inside static/ include a content hash (e.g. main.a1b2c3d4.js) so that browsers cache aggressively and cache-bust automatically on each new deploy.

​
Environment variables

Create React App supports environment variables that are embedded into the bundle at build time. Every variable must be prefixed with REACT_APP_ — any other variable is intentionally ignored for security.
.env
REACT_APP_SITE_NAME=My Dental Clinic
REACT_APP_CONTACT_EMAIL=contact@example.com
Reference them in your source code with process.env.REACT_APP_SITE_NAME. CRA recognises the following files, applied in order of increasing specificity:
FileWhen it is loaded
.envAll environments
.env.localAll environments, local overrides (not loaded in test)
.env.developmentnpm start only
.env.productionnpm run build only
The .env and all .env.local variants are listed in .gitignore and must never be committed to version control. Secrets in committed env files become public. Use your hosting provider’s secret management (e.g. Vercel Environment Variables) for sensitive values in CI/CD pipelines.

​
Hosting options

Vercel

Zero-config deployment with automatic HTTPS and preview URLs — the platform the original template was built for.

Netlify

Drag-and-drop or Git-connected deployments with a generous free tier and built-in form handling.

GitHub Pages

Free hosting for public repos using the gh-pages package — ideal if your code is already on GitHub.

Firebase Hosting

Fast CDN-backed hosting with first-class Firebase integration for auth, Firestore, and more.

​
SPA routing

Soumyajit Landing Pages uses React Router DOM v6 for client-side navigation. When a visitor refreshes the page or navigates directly to a deep URL (e.g. /about), the host must serve index.html for that path instead of returning a 404.
  • Vercel — handles this automatically with no extra configuration.
  • Netlify — add a public/_redirects file containing /* /index.html 200.
  • GitHub Pages — requires a custom 404.html redirect workaround or use of the HashRouter.
  • Apache / Nginx — configure a rewrite rule to fall back to index.html for unknown paths.
For a complete, step-by-step walkthrough of deploying this template to Vercel — including CLI commands, custom domains, and environment variable setup — see the Vercel deployment guide.

Build docs developers (and LLMs) love

Get started for freeTalk to us