Local Preview

Norio uses GSAP scroll effects and Three.js WebGL (project galleries, glass/grid textures, and similar sections). Those features need a normal browser origin. How you open the HTML files matters.

Recommended: run a local server

Always preview the template over HTTP (http://localhost), not by double-clicking files. A local server gives the full experience in every modern browser (Chrome, Edge, Firefox, Safari).

Option A — VS Code / Cursor Live Server

Open the HTML template folder (for example 1.norio-html-template).
Install the Live Server extension if needed.
Right-click index.html → Open with Live Server.

Option B — Node / Python one-liner

From the template root (the folder that contains index.html and assets/):

    
npx --yes serve .
# or
python -m http.server 8080

Then open http://localhost:3000 (or the port shown / 8080) in your browser.

Option C — Vite source kit

If you are working in norio-html-dev, use the built-in server:

    
cd norio-html-dev
npm install
npm run dev

Preview at http://localhost:3000. See also Development.

Opening files with `file://`

You can open HTML from disk (file:///...), but browsers treat local files under a strict security model. That can block or degrade WebGL textures and some effects.

If you open the template via file://, use Google Chrome (or Microsoft Edge). Chromium-based browsers are the most reliable for local WebGL previews. Firefox often blocks image textures on file:// (The operation is insecure) and falls back to a simpler layout without the full 3D gallery.

What works on `file://`

Layout, typography, dark/light mode, most CSS animations
GSAP scroll and UI motion (when scripts load)
WebGL project showcases in Chrome / Edge (with the shipped ThemeForest package)

What may fail or look incomplete

Firefox / Safari on file:// — WebGL textures from local images are restricted
Some advanced texture / deform effects that require a normal HTTP origin

Quick checklist

Best: local server → any modern browser
Quick peek without a server: open with Chrome or Edge
Hard-refresh (Ctrl+F5) after copying a new package so cached assets do not stick
Keep the folder structure intact — index.html and assets/ must stay siblings

Note

Production sites should always be deployed on a real host (Netlify, Cloudflare Pages, Vercel, shared hosting, etc.). The notes above are only for local preview before upload.