Deployment & Launch
Consultiz builds a static site into dist/, so it runs on any static host. It ships settings files for Netlify (netlify.toml), Vercel (vercel.json, vercel.sh), and Cloudflare Pages (wrangler.toml).
| Setting | Value |
|---|---|
| Build command | npm run build |
| Output directory | dist |
| Node.js version | 22.12.0 or later |
| Package manager | npm (package-lock.json) |
Before You Launch
PUBLIC-VALUES-NEEDED.md in the theme lists the values the demo can’t know: your domain, contact details, social and review profiles, and award claims. Go through it, then through this list. Each item links to the page that explains it.
-
[site] baseUrlis your real address, andnpm run buildshows no[site]warning (SEO & AI Visibility) - Site name, logos, favicon, social image, and colors are yours (Quick Start)
- Every demo phone number, email, address, and the office list are replaced (Common Changes)
- The contact forms, the footer newsletter, and the newsletter section post to your own accounts, and the “not connected yet” notes are updated (Forms)
- Social links in
src/config/social.jsonare yours and enabled; the demo links infooter-awards.mdare replaced - Client logos, ratings, review counts, awards, statistics, and testimonials are real, or removed. Ratings use your real platform’s logo and link your profile there (Sections)
- The Home and Who we are demo menus are trimmed to the pages you keep (Menus)
- Demo pages you don’t need are deleted or set to
draft: true, for example the one-page homepages, unused solution and industry layouts, and/components/(Pages) - Demo content is replaced: solutions, people, careers, portfolio, case studies, industries, blog posts, and the webinar page. Only real, open positions are listed (Collections)
- The privacy policy and terms are reviewed for your business
- Analytics scripts are in
[head], gated on consent if the cookie banner is on (Cookies & Analytics) - The copyright line in
src/i18n/en.jsonandfr.jsonhas your name and the current year -
npm run astro-checkandnpm run buildfinish without errors, and you have looked at every page you changed
Deploy
- Push your project to GitHub, GitLab, or Bitbucket.
- In Netlify, choose Add new site → Import an existing project and pick the repository.
- Netlify reads
netlify.toml: build commandnpm run build, publish folderdist, Node.js 22. Click Deploy.
The build uses baseUrl from config.toml unless you add a SITE_URL environment variable in the Netlify site settings.
netlify.toml also sets long-term caching for /_astro/* and /images/*, and sends missing /fr/... URLs to the French 404 page. Add a block for each extra language.
Using Netlify Forms? Set contactFormProvider = "netlify" and contactFormAction = "/", enable form detection under Forms, and redeploy.
- Push your project to GitHub, GitLab, or Bitbucket.
- In Vercel, choose Add New → Project and import the repository. Framework preset: Astro.
- Vercel reads
vercel.json, which builds withsh vercel.sh. Click Deploy.
vercel.sh sets the site address (SITE_URL) for each build, and on Vercel it replaces baseUrl:
- Production builds use the
SITE_URLenvironment variable if you set one in the Vercel project settings. Otherwise they use your Vercel production domain. SetSITE_URL(for examplehttps://www.example.com) when you want one exact address, such as thewwwor the bare domain. - Preview builds use
https://staging.<your production domain>.
Edit vercel.sh if you want something else.
vercel.json also enables trailing slashes and redirects /sitemap.xml to /sitemap-index.xml.
From git: in the Cloudflare dashboard, open Workers & Pages → Create → Pages → Connect to Git, pick the repository, and set the build command to npm run build and the output directory to dist (the same folder as pages_build_output_dir in wrangler.toml).
The included wrangler.toml already sets NODE_VERSION = "22.13.1" under [vars]. Cloudflare treats this file as the source of truth for the settings in it, so change them in the file. Set your address with baseUrl in config.toml.
From your computer: Consultiz doesn’t install Wrangler (Cloudflare’s command-line tool) for you. Add it once, change name in wrangler.toml to your project name, then log in, build, and deploy:
npm install -D wranglernpx wrangler loginnpm run buildnpm run deploy:cfRun npm run build and upload the contents of dist/ to your web server or static host.
For Apache servers, public/.htaccess (copied into dist/) sets browser caching for CSS, JavaScript, images, and fonts.
After You Launch
- Open the live site and click through the main pages, on a phone and a desktop, in English and French.
- Send a test message through each contact form, and sign up for each newsletter once.
- Open
https://your-domain/sitemap-index.xmlandhttps://your-domain/robots.txtto check that they use your domain. - Submit the sitemap in Google Search Console and Bing Webmaster Tools.
- Share a link in a chat app to check the preview image.
Updating The Live Site
With a git-connected host, every push to your main branch deploys automatically. Build locally first (npm run build) to catch errors before they reach your visitors. See Updating The Theme for new Consultiz versions.