Skip to content
New: Customize your theme with an AI assistant. Read the guide

Deployment & Launch

Givo builds a static site into dist/, so it runs on any static host. It ships ready-made settings for Netlify (netlify.toml), Vercel (vercel.json, vercel.sh), and Cloudflare Pages (wrangler.toml). The three editions all build a static site. See Theme Editions and the settings for your edition below.

SettingValue
Build commandnpm run build
Output directorydist
Node.js version22.12 or later. The Tina edition needs 22 (22.12 or later) or 24
Package managernpm (package-lock.json)

Settings For Your Edition

Astro: nothing extra. The site needs no account or environment variables.

Tina: a deployed site has no live editor. Its /admin/ page says online editing is off until you run npm run setup:tina, and your site works the same either way. To edit online, give your host PUBLIC_TINA_CLIENT_ID and TINA_TOKEN from your own Tina Cloud project. See Tina.

Sanity: give your host PUBLIC_SANITY_PROJECT_ID, PUBLIC_SANITY_DATASET, and PUBLIC_SANITY_STUDIO_URL. Don’t set SANITY_API_READ_TOKEN or SANITY_VISUAL_EDITING there. .env.example explains every variable. Most items in the list below are in the Studio instead of config.toml, such as Site settings > Site > Base URL and Site settings > Organization. The site must rebuild to show what you publish. See Sanity.

Before You Launch

Go through this list once. Each item links to the page that explains it.

Address and identity

  • [site] baseUrl is your real address, not the shipped https://example.com placeholder, and npm run build shows no [site] warning (SEO & AI Visibility)
  • title and logoText in [site], author and keywords in [seo], and seo.tagline and seo.siteDescription in each src/i18n/<language>.json describe your organization. The tagline is added to every page title (Site Identity & Logo)
  • The logo, favicons (npm run generate-favicons), social image (npm run generate-og-image, after the two items above), colors in theme.css, and fonts in fonts.json are yours (Colors & Fonts)

Organization details

  • [organization] in config.toml has your name, legal name, registration number, phone, email, address (or show = false if you have no public address), office hours, time zone, and closed dates, and the build prints no [organization] warning (Organization Info)
  • nonprofitStatus and foundingYear in [organization] are yours, or empty
  • taxNote in [organization] is false if gifts to your organization are not tax-deductible, and the “Tax-deductible” stamp in donate-section.md is true for your organization or removed

Donations

  • The donation form is connected: the form block in every src/content/donate/<language>/-index.md has your provider’s endpoint (mode: "form") or your hosted checkout processorUrl (mode: "redirect"), and the build prints no [forms] line for the donate form (Donation Form)
  • currency, the preset amounts, minimum, coverFeesPercent, the impact map, and the monthly tiers are yours, with the same numbers in every language (no [donate] warning) (Giving Tiers & Receipt)
  • The receipt stamps in donate-section.md (“Tax-deductible”, “100% to programs”) are true for your organization, or changed
  • The thank-you page (src/content/pages/<language>/donate-thanks.md) says what really happens after a gift

Causes and figures

  • The sample causes are replaced with yours, with real goals, amounts raised, donor counts, and deadlines, the same in every language (Causes & Campaigns)
  • The Causes mega menu, its featured cause (cta.cause), and the causes listed on the homepages point at your causes (Menus)
  • The figures on /impact/, the “where your money goes” split on the main homepage, and the spending line on /donate/ are yours and match each other (Impact & Transparency)
  • You have a daily rebuild planned while appeals are running, so the days left stay current (see Keep The Days Left Current below)

Forms

  • contactFormAction and contactFormProvider post to your own account (Formsubmit, Formspree, or Netlify Forms). The contact, volunteer, and fundraise forms use them (Forms)
  • The Mailchimp formAction under [settings.subscription] is your list, or enable = false there if you don’t send a newsletter
  • The sample inboxes in src/content/sections/<language>/contact-options-section.md ([email protected], [email protected], and others) are yours

Sample content

  • Sample facts are replaced: events, impact figures, team members, supporter quotes, partner names and logos, job roles, and stories. They are marked # sample in the content files (Collections)
  • Every sample photo is replaced. IMAGE-CREDITS.md lists them all (Icons & Images)
  • A project-wide search for example.com, example.org, and 555 finds nothing you still need to change

Pages and menus

  • The privacy policy, terms, cookie policy, donation and refund policy, and safeguarding policy in every language folder of src/content/pages/ are rewritten for your organization and reviewed. They ship as sample text with a notice at the top
  • The Pages demo menu is hidden ("enable": false in every menu file), and the menus point at your pages (Menus)
  • The demo homepages you don’t use are deleted (Homepages), and /elements/ and /components/ are removed if you don’t want the layout and shortcode galleries online (Pages)
  • [settings.layoutSwitcher] enable = false, and the build doesn’t set PUBLIC_DEMO_MODE
  • footer.description and footer.copyright in src/i18n/<language>.json describe your organization, and the links in src/config/social.json are yours

Analytics and checks

  • Analytics tags are in [head], marked with data-consent while the cookie banner is on (Cookies & Analytics)
  • npm run astro-check and npm run build finish without errors, and you have looked at every page whose section files you changed (astro-check doesn’t check section files or the contact page file)
  • The Arabic text has been reviewed by a native speaker, if you keep Arabic: it ships as a machine translation
  • You checked the site at phone width, in dark mode, and in every language you keep

Deploy

  1. Push your project to GitHub, GitLab, or Bitbucket.
  2. In Netlify, choose Add new site → Import an existing project and pick the repository.
  3. Netlify reads netlify.toml: build command npm run build, publish folder dist, 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/... and /ar/... URLs to that language’s 404 page. When you add a language, add its own block by hand.

Using Netlify Forms? Set contactFormProvider = "netlify" and contactFormAction = "/", enable form detection under Forms in the Netlify dashboard, and redeploy.

Keep The Days Left Current

The days left on each cause, the “Last day” and “Ended” labels, and the list of upcoming events are worked out when the site is built. A site that is not rebuilt keeps showing the count of its last build. While an appeal or an event is coming up, rebuild the site once a day.

Most hosts give you a deploy hook: a private URL that starts a new build when it is called. Create one in your host’s settings, then call it once a day from a scheduler you already use (for example a scheduled GitHub Actions workflow, or your host’s own scheduled builds if it has them). Keep the hook URL private: anyone who has it can start a build.

After You Launch

  1. Open the live site and click through the main pages, on a computer and on a phone, including the mobile menu, the Causes mega menu, the Donate bar, and dark mode.
  2. Make a small real donation, one-time and monthly, and check that it reaches your payment provider, that the donor lands on the thank-you page, and that your provider’s receipt email arrives. Refund it afterwards.
  3. Send a test message through the contact form, the volunteer form, and the fundraise form, and check that each one arrives.
  4. Open an event and add it to your calendar with the add to calendar link, and check the date and time.
  5. Submit https://your-domain/sitemap-index.xml in Google Search Console and Bing Webmaster Tools.
  6. Check the homepage, a cause page, and an event page with Google’s Rich Results Test.
  7. Share a link in a chat app to check the preview image.

Tell Search Engines About Changes With IndexNow

IndexNow tells Bing, Yandex, Seznam, and Naver which pages changed, so they visit them sooner. Bing also feeds ChatGPT search and Copilot. It is off until you set a key:

  1. In config.toml, set indexNowKey under [seo.ai] to a key of 8 to 128 letters, numbers, or dashes that you make up:

    [seo.ai]
    indexNowKey = "a1b2c3d4-your-own-key"
  2. Build and deploy. The build publishes the key file at https://your-domain/<key>.txt, which the search engines check.

  3. After each deploy is live, run from your computer:

    Terminal window
    npm run build
    npm run indexnow # pages changed in the last 7 days
    npm run indexnow -- --all # every page: use it after your first launch

    npm run indexnow -- --dry-run lists the pages without sending them.

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.

Type something to search...