Going live — Marai Neesu Astro
Before the Marai Neesu site goes public, replace the demo’s person and content with yours and point the forms at you; then build it, upload the static files to any host and check it again.
Replacing the demo means its name, photos, links, projects, products and posts; pointing the forms at you means giving both a destination. Once the site is deployed, click through the live address once more.
Before you deploy
Section titled “Before you deploy”| Where | |
|---|---|
Your domain in site.url (until you change it, it is the demo’s address) |
src/content/site.json. Share links, sitemap.xml and robots.txt are built from it. |
| Name, title and description (they describe the template: write yours) | site in src/content/site.json; the share image’s description, shareImage.alt, in src/lib/meta.ts |
| You as the logo: photo, name, city | person in src/content/site.json |
| Your name instead of “Marai Neesu” and “Neesu”, your city instead of “Dubai”: the copy, the CV, the testimonials’ quotes | Search src/content/ for them (Editing the content) |
Your e-mail (hello@example.com is a placeholder), in both places |
contact.email and the “Email” link of footer.reach in src/content/site.json |
| The footer’s city and time zone | footer.city and footer.timeZone in src/content/site.json |
Your profiles and links (they open the networks’ home pages or example.com) |
footer.reach and footer.profiles in src/content/site.json; socials.json; contact.links in src/content/pages/cv.json |
| The services’ “More Details” links (they open contra.com) | url of each service in src/content/collections/services.json |
Your products with their own buy and demo links (the demo’s point to example.com) |
src/content/collections/products.json |
| Your course, its price and its links (“Enroll Today” opens podia.com, “Free Preview” youtube.com), or the course removed | src/content/pages/courses.json, the banner course in home.json |
Your CV: education, certifications, jobs (their links open example.com) |
src/content/pages/cv.json, src/content/collections/experiences.json |
| Your tools in the Stack, with their logos | src/content/collections/tools.json |
| Testimonials from your own clients | src/content/collections/testimonials.json |
| Your projects and posts | src/content/collections/ |
| Your clients’ logos on the Projects page (the demo’s are samples) | clients.logos in src/content/pages/projects.json, the files in src/assets/images/ |
| Browser icons replaced | public/icon.png, public/apple-icon.png |
| Share image replaced and described | public/opengraph-image.png, its description in src/lib/meta.ts |
| Demo photos replaced | src/assets/images/ |
| Page titles and descriptions written for your work | The meta of each file in src/content/pages/ (contactPage.meta in contact.json, products.meta in products.json, blog.meta in blog.json) |
| The two forms deliver to you | Forms |
| A privacy page, if your country asks for one (the template has none) | Pages and sections |
| Style guide kept or deleted | src/pages/style-guide.astro |
npm run check and npm run build pass, and npm run preview looks right |
— |
The demo content is there to be replaced. Leaving “Marai Neesu”, the sample e-mail, the demo’s products and their links, the course, the testimonials or the sample client logos on a live site is the most common mistake.
Deploy
Section titled “Deploy”npm run build writes a complete static site to dist/: HTML files, one stylesheet, a few small scripts, the font
files and optimised images. Any host that serves files can run it, with no Node.js needed on the server (unless you
chose server-mode forms).
Vercel, Netlify or Cloudflare Pages (free for most sites)
Section titled “Vercel, Netlify or Cloudflare Pages (free for most sites)”- Push the project to GitHub, GitLab or Bitbucket.
- Import the repository. Astro is detected: build command
npm run build, output folderdist. - Add your form variables (
PUBLIC_FORM_ENDPOINT, …) in the host’s environment settings, then deploy. - Add your domain in the host’s Domains settings and follow the DNS instructions.
Pages are built as files (about.html, project/goeboek-real-estate-and-property.html) and served at clean addresses
(/about). Netlify and Cloudflare Pages do that by default. On Vercel, add a vercel.json next to package.json:
{ "cleanUrls": true }Any other host (shared hosting, S3, a VPS)
Section titled “Any other host (shared hosting, S3, a VPS)”npm run buildUpload the contents of dist/ to the web root. For clean addresses, make the server try <path>.html:
-
Apache (
.htaccess):RewriteEngine OnRewriteCond %{REQUEST_FILENAME}.html -fRewriteRule ^(.+)$ $1.html [L]ErrorDocument 404 /404.html -
nginx:
try_files $uri $uri.html $uri/ =404;anderror_page 404 /404.html;
Server-mode forms
Section titled “Server-mode forms”If you set PUBLIC_FORM_MODE=server, add your host’s adapter first (npx astro add vercel, netlify, cloudflare or
node). Only the form route runs on the server; every page stays static.
After it is live
Section titled “After it is live”- Check the pages. Click through every page on a phone and a laptop:
- the menu, the phone menu, and on a laptop the header that fades as you scroll down and comes back as you scroll up;
- the e-mail and the social tiles of the Home hero, and the service cards’ photos rolling under the pointer;
- the testimonials (a slideshow on a phone), the questions of Services and Course, the course modules;
- “Load More” on the Blog, and “Go Back” on a project, a product and a post;
- the footer’s clock, which should show the time of your city;
- the Contact form and the newsletter.
- Send yourself a message from both forms on the live site and reply to it.
- Verify the share card. Paste the URL of the home page and of a project into https://www.opengraph.xyz or a chat window, and confirm the image and title.
- Tell Google. Add the site to Search Console, verify ownership and
submit
https://yourdomain.com/sitemap.xml. Bing has the same thing in Webmaster Tools. - Analytics, if you want it. Add your snippet to the
<head>insrc/layouts/Layout.astro, or use your host’s built-in analytics (Vercel Analytics, Cloudflare Web Analytics, Plausible, Fathom). None of them need a cookie banner. - Keep it current. A new project is one entry in
src/content/collections/projects.json, a new post one entry at the top ofposts.json; see Editing the content, and rebuild. Connect a CMS (Using a headless CMS) if someone else will publish.
Performance and SEO
Section titled “Performance and SEO”The template ships with what search engines look for:
- static HTML, with links in it to every page (the posts behind “Load More” included);
- one
<h1>per page, and a title and description for every page; - canonical links,
sitemap.xml,robots.txtand share cards; - resized, lazy-loaded images that keep their space while they load.
Keeping the site fast is mostly about images. Astro resizes the photos, but export them at the size they are shown, not the size your camera produced: a 12 MB camera file still slows the build. The placeholders show the size each one was designed for.