This website.
This is uh... this website... :) A small static GitLab Pages site for International Duck Incorporated, with live organization data, project pages, member profiles, and a frankly excessive amount of glass.
It is the website.
There is no secret product behind this page. This repository is the product page, project directory, people directory, and occasional excuse to add another animated background.
Small, static, live.
- Plain HTML pages with no framework dependency
- Responsive glass UI with local assets
- Client-side GitLab API synchronization
- GitLab Pages deployment from the main branch
Open by default.
The source, content, and design live in the public repository. Browse the files, inspect the styles, or improve the next weird little page.
Open on GitLabStill being tinkered with.
Projects, people, releases, and the copy can change as the organization changes. The page is intentionally more alive than a README, but less serious than a product launch.
Architecture
Simple files, clear responsibilities.
The site stays deployable without a package manager, framework runtime, or generated bundle.
Documents
Each destination is a real HTML document with semantic landmarks, metadata, readable fallback content, and extensionless public links.
Presentation
A shared stylesheet provides layout, glass surfaces, responsive behavior, project components, and accessible motion preferences.
Enhancement
Shared JavaScript adds navigation behavior, reveal transitions, live public data, and optional page-specific backgrounds.
Data strategy
Useful before the API responds.
Checked-in content is the baseline; public APIs enhance it when they are available.
Static first
Project cards, profiles, release summaries, and navigation remain usable if a network request is blocked or rate-limited.
Live where helpful
GitLab provides organization, repository, activity, release, and contributor updates without controlling the core page layout.
Host-aware links
GitLab projects point to GitLab, while personal profiles that remain on GitHub keep their original destinations.
Local visual assets
Logos, member images, scripts, and styling ship with the repository so the interface does not depend on a third-party CDN.
Deployment
One repository, one Pages pipeline.
Changes merged into the primary branch are published through GitLab Pages. With no compilation step, the deployed output stays close to the source contributors review.