HOW THIS WEBSITE IS MADE

Wix hosts it. It doesn't build it.

People hear "Wix" and picture someone dragging boxes around in an editor. That is not how this website works. The site is written as code, kept on GitHub, built and tested by machines, and only then handed to Wix, which does one job: it keeps the servers on. Here is the whole system on one page.

How the PC NET TECHS website is changed and managedYou ask, Claude builds, GitHub keeps the website, GitHub Actions checks and ships it, Wix only hosts it, visitors see it; you manage it from PC NET DESK.YouTHE OWNERSay what the websiteshould do, in plainEnglish.ClaudeTHE BUILDERWrites the code, runsthe checks, recordsthe change.GitHubTHE WEBSITE ITSELFEvery page, everyfile, every versionsince the first.GitHub ActionsTHE RELEASE LINERuns 20 checks,builds and ships. Afew minutes.WixHOSTING ONLYServers, the domain,storage. Nothing isdesigned here.VisitorsTHE PUBLICSee the finishedwebsite atwww.pc-net-techs.com.12345Designed, built, tested and shipped here. None of this is Wix.A server and a domain.PC NET DESKTHE SITE'S OWN DASHBOARDLeads, visitors,settings. Part of thewebsite's own code.leads · visitors · settings6you read it in PC NET DESK, the site's own dashboard
How the PC NET TECHS website is changed and managedYou ask, Claude builds, GitHub keeps the website, GitHub Actions checks and ships it, Wix only hosts it, visitors see it; you manage it from PC NET DESK.YouTHE OWNERSay what the website should do, in plainEnglish.1a requestDesigned, built,tested and shippedhere. None of this isWix.ClaudeTHE BUILDERWrites the code, runs the checks,records the change.2the change, as codeGitHubTHE WEBSITE ITSELFEvery page, every file, every versionsince the first.3push to mainGitHub ActionsTHE RELEASE LINERuns 20 checks, builds and ships. A fewminutes.4the built siteA server and a domain.WixHOSTING ONLYServers, the domain, storage. Nothing isdesigned here.5pagesVisitorsTHE PUBLICSee the finished website atwww.pc-net-techs.com.PC NET DESKTHE SITE'S OWN DASHBOARDLeads, visitors, settings. Part of thewebsite's own code.leads · visitors · settings6you read it in PC NET DESK
The numbers are the steps below. Blue is the path of a change; red is how the owner reads the results. Wix appears once, as the host.
A CHANGE, STEP BY STEP

From a sentence to the live site

  1. You ask.

    A sentence in a conversation: "add a page for North Canton", "make the logo bigger", "the form should notify my phone". No editor, no login to Wix.

  2. Claude builds it.

    Claude writes the actual code of the website — the pages, the styles, the scripts, the data model — and records the change with a version number and a plain-English note.

  3. GitHub keeps it.

    The change is committed to the website's repository on GitHub. That repository IS the website: every page, every image, every version since the first. Any earlier version can be brought back.

  4. GitHub Actions ships it.

    A push to the main branch starts the release line: it runs 20 automated checks (if one fails, nothing ships), builds the finished site, and uploads it to the host. The whole run takes a few minutes and needs no one at a keyboard.

  5. Wix serves it.

    Wix receives the finished site and puts it on its servers under www.pc-net-techs.com, the way a landlord provides the building. It also stores the site's data — form submissions, the visitor log, the change log — in plain tables the website's own code reads and writes.

  6. You manage it from PC NET DESK.

    Leads, visitors, analytics, settings and the change log are read in PC NET DESK, the website's own dashboard — which is itself part of the code in GitHub, served by the host like any other page. The Wix dashboard is not part of the day.

THE HOST'S JOB

What Wix does, and what it never touches

Wix does

  • Keeps the servers running and the pages fast, worldwide.
  • Holds the domain name and the security certificate (the padlock).
  • Stores the site's data: form submissions, the visitor log, the change log, settings.
  • Handles the sign-in for the two private dashboards.

Wix does not

  • Design any page. No page of this site was drawn in the Wix Editor; it has never been opened for it.
  • Hold the layout, the copy or the pictures. Those live in GitHub, as code.
  • Supply templates, themes or add-on apps. None are used.
  • Make changes. Wix only receives the finished site; it cannot alter what it is given.
  • Decide anything. Every change starts with the owner and is carried out by Claude.

The honest summary: Wix is the landlord. It provides the building and the storage room. It did not draw the floor plan, it does not own the furniture, and it cannot rearrange it. If the lease ended, the website would move to another building intact.

"BUT ISN'T IT A WIX SITE?"

Five things people assume, and what is actually true

AssumedThe site is built in Wix.
ActuallyThe site is built in code, by Claude, and kept in GitHub. Wix receives the finished result.
AssumedChanges are made by logging in to Wix.
ActuallyA change is a conversation with Claude. The result is a commit in GitHub, and GitHub ships it. Nobody opens Wix to change the site.
AssumedWix could change the look or break the design.
ActuallyWix is handed a finished site and serves it. The design exists only in GitHub, where Wix has no hand.
AssumedIf Wix went away, the website would be gone.
ActuallyThe whole website — every page and every version — is in GitHub. The host can be swapped; the site stays, and its stored data moves with it.
AssumedSomeone must be clicking around in an editor.
ActuallyThere is no editor. There is a written record of every change, numbered, with a note saying what changed and why.

How you can tell

  • Every release has a number. This page shipped as release v5.142. Each one has a dated note saying what changed and why, kept in the repository and in the site's own change log.
  • Nothing ships unchecked. 20 automated checks run before every release: the pages, the tracking, the sitemap, the forms, the apps. If one fails, the old site stays up and nothing changes.
  • The Wix Editor has never drawn a page here. Open any page's source and you will find hand-named classes and the site's own scripts, not an editor's output.
  • The system that builds it has a name. This website was the first platform built with the Glass City Intelligence system, which is how Claude, GitHub and the release line work together here.
Back to the website Contact us