FIRST-PARTY PROJECT · OUR OWN WEBSITE

How we built the Zenvix website to accept digital project inquiries.

This case study documents work on Zenvix Creative Studio's own website. It is not a third-party customer testimonial, paid client result or claim of increased sales.

Tell us about your project ↗

The goal was to present the studio's services clearly, let visitors submit meaningful project requests and support the owner's day-to-day handling of inquiries through an independently managed hosting setup.

Evidence label: This is a first-party Zenvix platform build, not an independent client testimonial or measured sales case study. Claims are limited to directly checked technical implementation and availability.

Challenge and requirements

A service business needs more than a visually attractive homepage. Visitors should understand what is offered, how to request a quote and what happens next. The owner also needs a reliable way to receive new inquiries without exposing internal administrative systems to the public.

  • Clear service groups and dedicated category pages
  • A responsive contact form collecting project requirements
  • A practical handoff to the studio's email and private alert workflow
  • Public pages separated from the protected administration interface

Implementation and technology

The website runs a Django application in Docker behind a reverse proxy and HTTPS connection. Service content is organized in crawlable pages. A private notification flow was set up for the owner's operational alerts; these notifications are not public customer messaging.

  • Django site and service directory with public, semantic HTML pages
  • Cloudflare Tunnel and HTTPS for the public domain
  • Product and inquiry administration kept behind private access controls
  • Email and private push alerts for new customer inquiries
  • Sitemap, canonical URLs, navigation links and appropriate schema markup

What was tested

Checks verified the public homepage, service pages, sitemap and static assets through HTTPS. The private admin URL continued to return a denied response over the public domain, and a WebSocket notification handshake returned the expected upgrade response.

  • Public website pages and assets returned successful HTTP responses
  • Crawlable service groups were linked internally and present in the sitemap
  • Protected management routes were not publicly accessible
  • Mobile notification channel handshake completed successfully

What this case study does not claim

Technical tests do not prove commercial performance. Zenvix has not published verified growth figures, independent reviews or customer conversion percentages for this project. Search Console metrics should be assessed once sufficient search data is available.

  • No fabricated client testimonials or invented project results
  • No unverified Google ranking or traffic claims
  • No public exposure of credentials, customer details or internal host addresses
  • Ongoing improvements are evaluated against real inquiries and available data

Frequently asked questions

Is this a real client case study?

It is a first-party account of work on Zenvix's own website, not an external client engagement.

Can a similar workflow be built for my business?

Requirements can be reviewed, but integrations, platforms and data handling depend on the specific project and access available.

Do these technical changes guarantee leads?

No. The setup makes the inquiry process available; actual visibility and customer demand depend on many external factors.