Question 1

What is this repository?

Accepted Answer

It is an Astro + shadcn/ui landing template: sections, layouts, MDX blog, i18n routes, and GDPR-oriented analytics wiring. It is meant to be copied and customized per brand.

Question 2

Where do I change colors and fonts?

Accepted Answer

Start in src/styles/global.css (CSS variables) and src/docs/brand.json. Geist loads from BaseLayout—adjust @theme --font-sans there.

Question 3

Is it production-ready?

Accepted Answer

Technically yes after you replace placeholder copy, legal pages, form endpoints, GTM/insights IDs, and social URLs in i18n. Run your own accessibility and Lighthouse pass on the final content.

Question 4

How do I add or remove sections?

Accepted Answer

Edit src/pages/index.astro (or [lang]/index.astro). Each section is a component under src/components/sections—duplicate or comment blocks as needed.

Question 5

How does multilingual routing work?

Accepted Answer

Default locale can hide the /en prefix (see src/lib/i18n.ts). Other locales live under /de, /fr, /it. Keep translation JSON files in sync when you add keys.

Question 6

How do I connect the contact form?

Accepted Answer

The template uses Web3Forms: add your access key in src/lib/web3forms.ts and allowlist your domains at web3forms.com. Adjust from_name via brandName in i18n; optional fields and copy live under contact.form in each locale JSON.

Question 7

Why is there a credit link in the footer?

Accepted Answer

Optional attribution to the template maintainers. Remove or replace the built-by row in FooterSection.astro if you do not need it.

Template FAQ (replace when you fork)

Contact