A static site is not a poor site
Mehdi Messaoudene1 min readWebsites, catalogues and SEO

A static export removes any application server to maintain: only HTML, CSS and JavaScript remain. The BioInteraction DZ catalogue moved this way to Supabase and shared hosting. The trade-off: no API routes left, so all the server logic had to be redesigned.
- No application server to maintain: only HTML, CSS and JavaScript files.
- Trade-off: no API routes left in the application, server logic moves to on-demand functions.
- Deployment fits in an incremental SFTP script and an .htaccess file.
What is a static export?
The BioInteraction DZ catalogue, 418 references and 19 analysers, moved from a Firebase and Vercel stack to Supabase and OVH shared hosting, as a full static export. There is no application server left to maintain: the site is a set of HTML, CSS and JavaScript files, served as they are.
For a catalogue whose pages rarely change, that is a clear advantage: fewer parts that can fail, a simpler hosting bill, pages that load fast.
What the migration cost
The trade-off is real: there are no API routes left in the application. That is what made the migration interesting, because all the server logic had to be redesigned as Supabase functions called on demand.
The unexpected benefit is a much clearer boundary between what is public and what is not. Nothing secret sits in the code sent to the browser.
How the site is delivered
Deployment is a Node script that sends changed files over SFTP, incrementally. The rest fits in a single .htaccess file:
- 301 redirects;
- forced HTTPS;
- security headers;
- a rewrite that fixes Next.js prefetch paths.
That last point is the classic trap of static export on Apache: without this rule, files the browser asks for do not exist at the expected address.
When to choose this approach
Many applications pay for a permanent application server to serve pages that could be static. If that is your case, the saving is often immediate and structural. The condition: know precisely where each piece of logic that cannot be static lives, and put it there before the migration rather than after.
Frequently asked questions
Can a static site have a customer area?
Yes, as long as everything that changes is handled elsewhere. On BioInteraction DZ, Supabase handles what moves (accounts, data) and on-demand server functions carry the private logic.
What makes static export tricky on Apache?
Next.js prefetch paths. A rewrite rule in the .htaccess fixes them: it is the classic trap of static export on Apache.
Cet article existe aussi en anglais
Discussion
Comments use a GitHub account.


