Skip to content
Sign inJoin waitlist

Going live — Marai Neesu HTML

Publishing the Marai Neesu HTML edition means replacing the demo’s name, details and pictures, pointing the forms at you and uploading the folder to any static host.

There is no build command and no server software: the folder you edited is the site.

Where
Demo domain replaced by yours Every .html file, sitemap.xml, robots.txt: find https://marai-neesu-html-marcframe.vercel.app (Editing the site)
Your name instead of “Marai Neesu” and “Neesu”: the logo, the copy, the CV, the testimonials’ quotes, the titles Search the folder for “Neesu”
Your place and your clock (“Dubai, UAE”, the footer’s “Dubai” and Asia/Dubai) Every page (Editing the site)
Your e-mail (hello@example.com is a placeholder) The footer of every page, Home, Services, Course
Social links and the footer’s profiles (they open the networks’ home pages) The Home hero, the footer of every page
The links of the services, products and course (contra.com, example.com, youtube.com, podia.com) Editing the site
The footer’s “Marcframe templates” link Every page: your own link, or delete it
Titles and descriptions written for your work Each page’s <head>; Home’s describe the demo person
Avatar, icons and share image replaced assets/images/avatar.png, icon.png, apple-icon.png, opengraph-image.png (2400 × 1260; 1200 × 630 or larger) and its description, og:image:alt
Demo photos, client logos and tool logos replaced assets/images/
Your own projects, services, products, posts, experiences and testimonials The pages and their lists (Editing the site)
Your course, or the Course page removed course.html, the banner on Home (Editing the site)
Your CV: education, contact rows, certifications cv.html
The contact form’s interests match your services contact.html (Forms)
The forms deliver to you assets/js/config.js (Forms)
A privacy notice, if your forms collect personal data A page of your own (Forms)
Style guide kept or deleted style-guide.html
Stylesheet rebuilt if you changed the theme or used new classes npm run build:css (Making it look like your brand)

Leaving “Neesu”, the sample e-mail, the sample links, the testimonials, the products or the sample client logos on a live site is the most common mistake: search the folder for “Neesu”, “example.com”, “contra.com” and “Dubai” one last time (the placeholder your@company.com in the contact form can stay).

Everything except the tools and the documentation:

Upload Leave out
The .html pages, project/, product/, blog/ node_modules/, src/, docs/
assets/ package.json, package-lock.json
icon.png, apple-icon.png, opengraph-image.png README.md, CHANGELOG.md, LICENSE.md
sitemap.xml, robots.txt Documentation.html, Documentation.pdf

Uploading the extra files does no harm, but there is no reason to publish them.

Host How
Netlify Drag the folder onto Netlify Drop. Done; then add your domain.
Cloudflare Pages, Vercel Upload the folder or connect a Git repository; no build command, the output folder is the root.
GitHub Pages Push the folder to a repository and enable Pages.
Shared hosting (cPanel, Plesk…) Upload through the file manager or FTP into public_html (or www).

Pages link to each other with their file names (about.html, project/goeboek-real-estate-and-property.html), so no server configuration is needed. Most hosts serve 404.html for unknown addresses automatically; on Apache, add ErrorDocument 404 /404.html to .htaccess. The paths in 404.html start at the site’s root (/assets/css/style.css, /index.html), because hosts show it at any address: if your site lives in a sub-folder of its domain (example.com/portfolio/, or a GitHub Pages project site), add that folder to those paths.

Add it in the host’s domain settings and point your DNS where they tell you (usually an A record or a CNAME). Turn on HTTPS: every host above does it for free.

  1. Check the pages. Click through every page on a phone and a laptop:
    • the header on a desktop: scroll down and up, and hover the logo; the phone menu;
    • the rolling roles, the e-mail and the social tiles on Home;
    • the service cards’ photos, the testimonials (the slideshow on a phone) and the product cards’ hover;
    • the client logos on Projects, a project page and its Go Back pill;
    • the FAQ on Services and Course, and the course modules;
    • the Blog’s “Load More”, a post, a product page;
    • the footer’s clock;
    • the 404 page (open an address that doesn’t exist).
  2. Send yourself a test from each form (an inquiry, a newsletter sign-up) and reply to the inquiry.
  3. Verify the share card. Paste the URL of the home page and of a post into https://www.opengraph.xyz or a chat window, and confirm the image and title.
  4. 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.
  5. Analytics, if you want it. Paste your snippet before </head> in every page (find and replace on </head> does it at once), or use your host’s built-in analytics (Cloudflare Web Analytics, Plausible, Fathom). None of them need a cookie banner.
  6. Keep the work current. Add projects, products and posts as described in Editing the site, and keep sitemap.xml in step.

The pages ship with what search engines look for:

  • real 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.txt and share cards; the 404 page and the style guide are kept out of search results (noindex);
  • lazy-loaded images below the top of each page, with their size written so that they keep their space while they load.

Each image is one file, used at every screen size. Keep the site fast by exporting photos at the size they are shown and compressing them; the photos at the top of each page (the Home portrait, the About photos, the project covers and the post covers) matter most on phones.