zevoratech/zevoratech-site

Purpose and delivery model

ZevoraTech is a plain static marketing website for the ZevoraTech brand. It has no build pipeline, application server, database, or backend API. The deployable unit is the repository root: HTML pages, shared CSS/JS, and static assets.

Relevant paths: index.html, styles.css, script.js

Browser entry points and page structure

Each HTML document is independently addressable and served directly by the host. index.html is the primary landing-page entry point; the remaining pages represent site sections navigated through normal document links.

• Home: index.html

• Product placeholder / coming-soon page: products.html

• Company information: about.html

• Contact page: contact.html

This is multi-page static navigation rather than a client-side router or single-page application.

Shared presentation layer

styles.css is the central visual-system boundary: it provides styling shared by all pages, including responsive behavior and likely common layout elements such as navigation, footer, and page sections. HTML pages own their content and semantic structure; CSS owns presentation.

Relevant paths: styles.css, index.html, products.html

Lightweight client behavior

script.js provides the site’s only client-side behavioral layer. Its defined responsibilities are mobile-menu interaction and dynamically setting the footer year. It does not represent a data-fetching, state-management, or application-runtime layer.

Relevant paths: script.js, index.html, contact.html

Asset boundary

Brand media is packaged locally under assets/ and referenced by static pages rather than fetched from an external asset service. The known primary asset is the logo.

Relevant paths: assets, assets/logo.png, index.html

Contact flow and backend boundary

The contact experience intentionally has no server-side submission handling. The contact form opens the visitor’s configured email client, making mail composition the external handoff boundary. There is no form-processing service, persistence layer, validation API, or email-delivery integration in this repository.

Relevant paths: contact.html, script.js

Hosting and infrastructure

The intended production runtime is a static-file host with HTTPS. Cloudflare Pages is the recommended deployment target, using asset upload and optional custom-domain/DNS configuration for zevoratech.in; GitHub Pages is an alternative. Hosting is responsible only for serving files, DNS/domain attachment, and TLS certificates—not application execution.

Relevant paths: README.md, index.html, assets