ZENOVA Labs logo
ZENOVA LabsCloud / Networking / IoT / AI

Use case

zenova.sk as an end-to-end Azure web delivery reference

This reference shows the full flow from architecture and HLD decisions, through VS Code implementation, validation and GitHub Actions workflows, to deployment and live operation in Azure.

Public repository on GitHub
Project typeproduction website plus public end-to-end delivery reference
HostingAzure Static Web Apps Standard
IaC directionBicep and documented decision records
Language model`/` and `/en/` without domain-routing overkill

Architecture snapshot

How this website works as a small but presentable Azure project

The goal was not to add as many layers as possible. The goal was to show a clean path from HLD and repository decisions, through local implementation and workflows, to a production website with Slovak and English branches in Azure.

Source of truth Public GitHub repo

Content, frontend, decision records and public workflow direction in a single repository.

Delivery layer Build and CI/CD foundation

Static build, configuration validation and a prepared path for test and production delivery.

Hosting Azure Static Web Apps Standard

A production-ready hosting model without unnecessary edge complexity for this website scope.

Experience layer zenova.sk and /en/

Stable SEO URL branches, responsive frontend and use cases as the proof-driven content layer.

Delivery model

How this project moves from local work to the production website

Local

npm start

Local development in the dev container with fast verification of layout, SEO routing and detailed use cases on `localhost:8000`.

PR preview

SWA preview

Pull-request review layer powered by Azure Static Web Apps preview environments, activated after bootstrap phase 2.

Test

OIDC + staged bootstrap

A stable non-production environment through `deploy-test.yml`, public parameter files, enterprise edge direction and the GitHub Environment `test`.

Production

zenova.sk

A controlled staged release path through `deploy-prod.yml`, SWA Standard and the canonical `zenova.sk` domain with `/` and `/en/` branches.

Context

The goal was not only to rebuild a company website. The goal was to create a small but representative web project that works in production and at the same time serves as a public end-to-end reference for Azure web design, delivery and operations.

  • no CMS and no database
  • public GitHub repository without internal secrets
  • a need to separate the production website from internal planning while preserving the public technical value of the project

Proposed solution

The website is built as a static multi-page frontend with separate Slovak and English branches, hosted on Azure Static Web Apps Standard with an enterprise edge direction. Architectural decisions are documented directly in the repository and the infrastructure direction is prepared for staged Bicep bootstrap and further CI/CD expansion.

  • Azure Static Web Apps Standard with enterprise edge direction as a practical production foundation
  • a multi-page model instead of one overloaded landing page
  • SEO-friendly URL branches via `/` and `/en/`
  • documented decisions for edge and IaC direction

Delivery model in practice

The repository already shows a public delivery foundation without exposing secrets. The Bicep foundation, workflows and documentation live in the repo, while environment variables, OIDC federation and SWA deployment tokens stay outside it and the first bootstrap is intentionally staged.

  • subscription-level `infra/main.bicep` with public `test` and `prod` parameter files
  • `ci-validation`, `infra-whatif`, `deploy-test`, `deploy-prod` and `preview-pr` workflows
  • a clean separation between phase 1 infra bootstrap, phase 2 app deploy and manual environment setup outside the repo

Why this is interesting as a use case

The project shows that even a small company website can be designed as a technically clean Azure use case. The value is not only in hosting, but also in how decision records, public documentation, baseline infrastructure imports and a gradual delivery model are combined.

  • a production website and a technical reference asset in one
  • a right-sized scope without unnecessary enterprise over-engineering
  • a clear upgrade path for IaC, test/prod environments and future use cases

Outcome

zenova.sk becomes not only the company’s sales and SEO layer, but also proof that ZENOVA Labs can design and communicate an Azure web project end-to-end. That is exactly why the public GitHub repository is part of the case itself.

  • a clearer website structure for both search and sales communication
  • a real link between the website, Azure architecture and repository documentation
  • a public project that can be shown to clients and reused as a technical reference asset

Repository and next step

If you want a similar static Azure website or a public showcase project, we can shape the same delivery model for your environment

This use case includes a public GitHub repository where the decisions, documentation, workflows and implementation are visible as part of the delivery story.

Open GitHub repo Contact ZENOVA Labs