Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/luigitemu/pikante-landing/llms.txt

Use this file to discover all available pages before exploring further.

Pikanté Landing is a fully static site. Running npm run build produces a self-contained ./dist/ folder of HTML, CSS, JavaScript, and media files — no server runtime, no serverless functions, and no environment variables. Any platform that can serve static files will work; the three most common are covered below.

​
Production build

Before deploying, generate the production build locally to confirm everything compiles cleanly: 
npm run build
Astro writes all output to ./dist/. You can preview that build with: 
npm run preview
This serves ./dist/ at http://localhost:4321 so you can verify the final output before it goes live.

​
Deploy targets

Vercel auto-detects Astro projects and pre-fills the correct settings. You can deploy via the Vercel dashboard or the CLI.Dashboard (recommended)
  1. Push the repository to GitHub, GitLab, or Bitbucket.
  2. Open vercel.com/new and import the repository.
  3. Vercel detects the Astro framework preset automatically. Confirm the settings:
SettingValue
Framework PresetAstro
Build Commandnpm run build
Output Directorydist
  1. Click Deploy. Vercel runs the build and publishes dist/.
CLI
# Install the Vercel CLI once
npm install -g vercel

# From the project root
vercel
Follow the interactive prompts. On the first run, Vercel links the project and detects the Astro preset. Subsequent deploys use vercel --prod.

​
Static output — no adapter required

No adapter needs to be added to astro.config.mjs for these deployments. Astro’s default output mode is static, which is exactly what all three platforms expect. Adding a server adapter (e.g. @astrojs/vercel) is only necessary if you need server-side rendering — Pikanté Landing does not.
The current astro.config.mjs is intentionally minimal:
astro.config.mjs
// @ts-check
import { defineConfig } from 'astro/config';

import react from '@astrojs/react';

import tailwindcss from '@tailwindcss/vite';

// https://astro.build/config
export default defineConfig({
  integrations: [react()],

  vite: {
    plugins: [tailwindcss()]
  }
});
No output: 'server', no adapter — Astro defaults to output: 'static' and generates a fully pre-rendered site.

​
Bandwidth considerations

The public/assets/prep-video.mp4 file (~4 MB) is included in the static build and served directly as a binary asset. On free-tier hosting plans, large binary files count against your bandwidth quota. Keep the following in mind:
  • Vercel free tier has a 100 GB/month bandwidth limit — the video should be fine for moderate traffic.
  • Netlify free tier includes 100 GB/month; after that, charges apply.
  • Cloudflare Pages does not charge for bandwidth, making it the most cost-efficient option for a media-heavy static site.
If traffic spikes significantly (e.g. a viral social post), the 4 MB video will dominate your bandwidth consumption. Consider hosting the video on a CDN (Cloudflare Stream, Bunny.net, or a similar service) and swapping the <video src> to an external URL to eliminate the file from your static build.

Build docs developers (and LLMs) love

Get started for freeTalk to us