Skip to content
Academy · Guides

Before publishing, test exactly what you will upload and review what visitors and search engines will see.

By Arrmma editorial team · Published · 40 min · Level: Beginner

Tested on November 8, 2026 with Pliegue 1.1.0, Node.js 24.22.1 and npm 11.19 on macOS.

Short answer

To publish your project: run npm run build, test the dist/ folder with npm run preview, add your own title and meta description, replace all sample content, review robots.txt and licenses, and upload dist/ to static hosting (on Vercel, by importing the repository: vercel.json already sets npm ci, npm run build and dist). Then connect your domain and check the public URL on mobile.

What you need

  • The customized project (previous guides).
  • An account with a static host (Vercel, Netlify or another) and, optionally, your domain.

Steps

  1. Build the final version

    npm run build creates dist/: a static site with pre-rendered HTML, readable even if JavaScript is slow or fails.

    npm run build

    Check: dist/index.html exists and contains your copy (search for it in the file).

  2. Test exactly what you will upload

    Preview serves the dist/ folder as it will be published.

    npm run preview
    # open http://localhost:4173

    Check: The page responds and looks the same as in development.

  3. Add a title and description

    The package has a <title> but no meta description: the summary search engines often show. Write it in your own words.

    <meta name="description" content="Marea Estudio designs brands and websites with its own way of seeing the world.">

    Check: After building, dist/index.html contains your meta description.

  4. Review content, licenses and robots.txt

    Replace sample names, copy and images; follow LICENCIAS-Y-AVISOS.md. The package robots.txt allows crawling (Allow: /). Sample forms are not connected.

    Check: No sample copy, client or image that is not yours remains.

  5. Publish to static hosting

    On Vercel: push the project to a repository and import it; vercel.json already sets npm ci, npm run build and the dist folder. Elsewhere: upload the contents of dist/. If you publish in a subfolder, set base in vite.config.js.

    Check: The host finishes the deployment without errors and gives you a public URL.

  6. Connect your domain and check on mobile

    Follow your host’s DNS instructions. Open the public URL on your phone.

    Check: Your domain loads over https and the page looks right at 390 px.

Our example

dist/ was 2.2 MB (HTML, CSS, JS, WebP images, fonts and licenses).

npm run preview answered 200 on / and on /robots.txt.

We added the meta description and confirmed it appears in dist/index.html. We did not publish the example to a host: that step depends on your account.

Common mistakes

  • Uploading the project folder instead of dist/ to static hosting.
  • Publishing in a subfolder without setting base: images and fonts return 404.
  • Forgetting the meta description or keeping the sample title.
  • Assuming Google will index the page as soon as it is published: it can take time and is not guaranteed.

Find your next design.

Get Arrmma updates.