Unzip the package
Upload the contents to your web root or a subfolder. The static theme does not require a database.
Neravo HTML Template
Neravo is a fullscreen creative services HTML template with a fixed sidebar, multiple home demos, modal content views, dark visual system, responsive navigation and an optional reusable page builder called Payo Studio.
Upload the contents to your web root or a subfolder. The static theme does not require a database.
Use index.html, index-video.html, index-image.html or index-reel.html. home-demos.html is a separate preview navigator and is intentionally not part of the website navigation or Payo Studio page scan.
You may edit HTML/CSS directly in any code editor. Payo Studio is optional and is not required for the website to work.
If you use the bundled PHP contact handler, set the recipient email address inside php/contact.php.
Neravo/ ├── index.html ├── index-video.html ├── index-image.html ├── index-reel.html ├── home-demos.html ├── assets/ │ ├── css/style.css │ ├── js/main.js │ ├── media/ │ └── uploads/ # created/used by Payo Studio ├── php/contact.php ├── payo-studio/ # optional universal HTML editor │ ├── index.php │ ├── install/ │ ├── api.php │ ├── public.php │ ├── assets/ │ ├── includes/ │ └── storage/ # protected config, overrides, backups └── Documentation/index.html
Main cinematic homepage.
Video-first hero variant.
Editorial still-image hero.
Automatic visual reel.
All home demos use the same fullscreen sidebar concept and modal content views for Services, Selected Work, Studio, Journal and Contact.
home-demos.html is deliberately styled as a separate preview launcher and includes a visible “Preview launcher · not a website page” notice so it cannot be confused with a customer-facing Neravo page.The downloadable Main Files use an original procedural placeholder set so customers can replace media without licensing ambiguity. The placeholder files are intentionally simple, dark, softly blurred and slightly different from one another so the layout remains attractive while making it obvious that the final project should use the customer’s own imagery.
1600×1000 procedural editorial placeholders used throughout services, work and journal views.
Portrait/wide abstract placeholders for the studio/team areas.
Original procedural local motion placeholder; no external video is required in the Main Files package.
For the fastest swap, replace files using the same names. Payo Studio can also upload/replace images visually after installation.
Open the relevant HTML file and replace the existing text directly. Content views are stored inside <template> blocks such as view-services, view-work, view-studio and view-journal.
Replace files inside assets/media/ or update each image src. Keep descriptive alt text for accessibility.
The visual system is in assets/css/style.css. Global colors use CSS custom properties defined in :root.
Navigation, modal workspace, portfolio filtering, counters, responsive interactions and animations are in assets/js/main.js.
Optional module
Payo Studio is designed as a theme-independent page builder that can be copied into other HTML projects. It uses a file-based override layer instead of requiring a database or rewriting content on every save.
Edit through a contextual inspector, then save reusable Sections/Addons and drag them into the page.
Authenticated image uploads are MIME-checked, dimension-limited and re-encoded.
CSS color variables are detected during installation and exposed in the editor.
Copy the payo-studio folder to another HTML project and run its installer.
payo-studio/storage. Fileinfo + GD are required for secure image uploads. DOM is required for the server-side reusable-block sanitizer.Use a normal PHP-enabled web server. Payo Studio does not run from file:// URLs.
Visit https://your-domain.com/payo-studio/install/.
The first screen checks PHP version, write permissions, Fileinfo, GD, JSON and sessions.
Choose the admin username and a password of at least 12 characters. The password is stored only as a secure PHP password hash.
The installer scans HTML files and CSS color variables. It excludes its own editor folder and Documentation.
Original HTML pages are backed up. The installer adds a local bridge.css stylesheet and a local bridge.js script to connected HTML pages and creates protected file-based storage.
Open /payo-studio/ and sign in with the administrator created during setup.
The dashboard lists every connected HTML page. Click Open live editor.
Click text, an image, a button, card, section or container. The inspector identifies the element type and shows only relevant controls.
Text gets typography/content controls; images get upload/alt controls; buttons get button appearance; sections and containers get background and spacing controls.
Cancel discards unsaved preview changes and closes the inspector. Save persists and stays open. Save & Close persists and closes.
Save reusable Sections/Addons and drag them into connected HTML pages from the Library toolbar button.
After installation, open the Security section in the Payo Studio dashboard to change the administrator password. The current password is required.
Element changes are stored as JSON overrides keyed by page and selector. Reusable block insertions are stored as page layout operations. The original source remains readable, and installation backups are retained.
Choose Add Section in the live toolbar to create a new section before or after an existing block. Layouts are selected visually and generated by the authenticated server from a fixed whitelist.
Create one, two, three or four equal drop zones.
1/3 + 2/3, 2/3 + 1/3, 1/4 + 3/4, 3/4 + 1/4 and three-column combinations.
Core Heading, Text, Button, Divider and Spacer addons are available immediately, alongside reusable saved Addons.
Inserted Sections and Addons can be deleted. Native theme blocks are safely hidden via page overrides and can be restored from Views & Layers.
Heroes, feature areas, testimonials, pricing bands, content sections and similar larger containers can be saved as Sections.
Cards, image blocks, buttons, media tiles and component-like containers can be saved as Addons.
Open Library in the live editor. Drag a Section to a before/after insertion line, or drag an Addon inside a highlighted container. The inserted block can then be edited normally and removed from the page when no longer needed.
Reusable HTML is not trusted just because it comes from the browser. The server sanitizes each saved block with a DOM allowlist. Scripts, iframes, forms, inline event handlers, IDs and unsafe URL schemes are removed. Payo Studio intentionally does not provide an unrestricted HTML/JavaScript code editor.
For the full builder documentation, open Documentation/Payo-Studio.html.
Images uploaded in the editor are written to assets/uploads/YYYY/MM/ with generated filenames.
| Control | Behavior |
|---|---|
| Authentication | Uploads require an authenticated Payo Studio administrator session. |
| CSRF | Every upload request requires the active CSRF token. |
| Allowed formats | JPEG, PNG and WebP only. |
| MIME validation | Uses PHP Fileinfo and does not trust the browser Content-Type alone. |
| Dimensions | Images above 7000×7000 or above 24 megapixels are rejected. |
| Size | Default maximum is 6 MB per image. |
| Re-encoding | GD decodes and rewrites the image before it becomes public. |
| Filename | Generated random server filename; original upload name is not used. |
SVG and arbitrary file uploads are intentionally disabled by default.
During installation, Payo Studio scans CSS files inside assets/css/ for custom properties containing color values. In live editor mode, choose Theme colors from the top toolbar.
For Neravo, the main accent is --accent: #c8ff4d. Global color overrides are stored separately from style.css and applied to every connected page.
Payo Studio is intentionally designed without arbitrary PHP uploads or an unrestricted code editor. Reusable block HTML is accepted only through a server-side allowlist sanitizer.
| Area | Implementation |
|---|---|
| Password | password_hash() / password_verify(), no plain-text password storage. |
| Session | Strict-mode cookie sessions, HttpOnly, SameSite=Strict, Secure on HTTPS, session ID regeneration, idle timeout and absolute lifetime. |
| CSRF / origin | State-changing editor API requests require a random session CSRF token, same-origin validation and Fetch Metadata checks when supplied by the browser. |
| Login throttling | Repeated failed attempts are temporarily delayed/locked in the current session. |
| XSS surface | Text editing stores plain text. Reusable Sections/Addons are server-sanitized; scripts, inline event handlers, iframes/forms and unsafe URL schemes are rejected or removed. |
| URLs | Dangerous javascript:, vbscript:, data:, file: and scheme-relative URLs are rejected by the server. |
| Storage | payo-studio/storage ships with Apache deny rules and keeps config, JSON overrides, history and backups away from normal public assets. |
| Headers | Admin/API pages set no-store caching, anti-sniffing, same-origin framing/opener policy, referrer/permissions policies and a restrictive CSP with object-src none. |
.htaccess. Add the deny rule shown in the Server notes section.The editor includes payo-studio/storage/.htaccess with deny rules and hardens the public image-upload directory against script execution on Apache. Make sure your Apache configuration permits .htaccess overrides for this directory.
Add a location rule that denies direct browser access to the Payo Studio storage folder:
location ^~ /payo-studio/storage/ {
deny all;
return 403;
}A common starting point is directories 755, files 644, with the web server user owning or having write access only where needed. The installer needs temporary write access to HTML pages to inject the bridge. After installation, return HTML files to normal read-only web permissions; ongoing editor writes only need payo-studio/storage and assets/uploads.
Use HTTPS in production. The editor automatically marks its session cookie Secure when HTTPS is detected.
The included contact form posts to php/contact.php. Open that file and change both the recipient and From email addresses before publishing. The handler uses fixed configured addresses rather than deriving mail headers from the HTTP Host header. The contact handler is independent of Payo Studio.
Neravo uses a local system-font stack, so the customer package has no remote webfont dependency. Review assets/media/MEDIA-MANIFEST.txt for the included original procedural placeholders. No AI-generated preview artwork is included in the customer Main Files package.
Useful official references for security and marketplace preparation:
Temporarily allow the PHP/web-server user to modify the HTML pages. After installation, normal editing is stored in Payo Studio's storage layer.
This is expected. Payo Studio needs PHP sessions and API endpoints, so use localhost/XAMPP or a web server.
Confirm Fileinfo and GD are enabled, the file is JPEG/PNG/WebP, under 6 MB and below the dimension limit.
The generic detector exposes CSS custom properties with color values. A theme that hardcodes colors instead of using variables can still use per-element color controls.
The static HTML theme remains the source of truth. If the editor folder is not used, the original theme remains usable. To remove an installed bridge cleanly, restore the backed-up HTML files from payo-studio/storage/backups/ before deleting the editor folder.