This repository is for the public UUG.AI website.
It is not a design system repository. Do not use this repo to document shared UI primitives, tokens, or component-library conventions unless that work is directly required by the public site.
This repo contains the website delivery and release configuration for the public UUG.AI presence, including:
- GitHub Pages deployment for the main site
- Container image builds for tagged releases
- GitOps updates for the staging website deployment
Pushes to main trigger the GitHub Pages workflow in .github/workflows/deploy.yml.
That workflow:
- installs Node.js dependencies with
npm ci - builds the site with
npm run build:all - uploads
dist/as the Pages artifact - deploys the generated site to GitHub Pages
Creating a GitHub release triggers .github/workflows/release-create.yml.
That workflow delegates to the shared UUG.AI release workflow to:
- build and publish
ghcr.io/uug-ai/website:<tag> - update the staging GitOps manifest in
uug-ai/gitops
Pull requests run the shared JavaScript build workflow defined in .github/workflows/pr-build.yaml.
The automation in this repository expects a Node.js-based website build.
Typical local commands are:
npm ci
npm run build:allIf the website application files are not present in your checkout, those commands will not run successfully until the missing source files are added. The CI configuration and Docker build both assume the site source includes package.json, package-lock.json, and the corresponding build scripts.
The Docker image defined in Dockerfile uses a multi-stage build:
- a Node.js build stage that installs dependencies and builds the site
- an NGINX runtime stage that serves the generated
dist/output
When updating this repository, optimize for the public website:
- website content and structure
- production build output
- deployment and release automation
Avoid framing changes as design-system work unless the change is explicitly about the public site experience.
MIT License. See LICENSE.