babuni.dev
An interactive creative portfolio and digital workshop.
Projects appear as engraved stone tiles with colored portal windows. An endlessly recyclable grid slowly shifts around the visitor. Projects unfold from small previews into fully explorable galleries, documents, videos, and development histories.
The website itself is intended to become one of its exhibits: a record of its concepts, design experiments, code, decisions, and human–AI collaboration.
Project status
Living-grid portfolio prototype with multiple depths of exploration. Astro 7 and the mechanical grid are on main: screen-centered dragging, autonomous shifting and 42 retained project tiles and three unique neutral decorative identities. Visitors can explore three-point topic bubbles, open a small bloom of up to eight neighboring modules, expand into a larger grid-native bloom, and read full documentation or open galleries, videos and source links. All forty-two active projects have supplied 512 × 512 WebP portal artwork files, while other candidate tiles remain provisional. The repository-backed content pipeline currently maps 35 retained tiles to 35 public repositories, including BABUNI.DEV itself; other tiles remain explicitly unresolved or provisional. Remaining candidate labels are not all verified or approved published exhibits. Full public project documents are built as separate static assets and loaded only when opened in the reader, keeping the initial grid bundle lighter. The Projects menu groups the 42 projects under World of Warcraft, Morkahja, AI, Games and Music; categories do not rearrange the grid. Three neutral identities never repeat in view, while real projects may repeat when necessary. The work remains an active prototype, with milestones 1–4 physically tested and accepted by Babuni.dev on 2026-10-29. Production hosting, discoverability and owner publishing controls remain next.
The first spiral is sorted newest-first by the latest commit on each connected public repository branch. Private-code projects use their public documentation edition dates. Each build refreshes public activity; ties and undated projects keep catalog order, and an active page never re-sorts. Offline/rate-limited builds warn and retain last-verified dates.
Local development
Requires Node.js >=22.23.4 (the version range declared by the project and locked Astro package) and npm. Run these commands from the repository root:
npm ci
npm run dev
Open the local address printed by Astro (normally http://localhost:4321). For agents, use npm run dev -- --background; manage it with npm run astro -- dev status, npm run astro -- dev logs, and npm run astro -- dev stop.
npm run activity:sync refreshes public commit metadata for local preview; add -- --save-baseline only when deliberately updating the checked-in fallback for review. Normal builds update only ignored generated metadata, so they do not dirty the checkout. Dev/test startup uses the last verified cache without network access.
npm run test:grid runs the regression suite. npm run build validates content, prepares the public document assets and creates the static site in dist/. npm run preview serves that build locally. npm run content:prepare rebuilds local preview metadata/static Markdown from reviewed sources without network access; it is invoked automatically before dev, tests and builds.
Babuni.dev's 2026-10-27 local terminal output verified 92 passing tests and a successful build on the preceding version, with a >500 kB JavaScript chunk warning. An earlier optimized version passed 97 tests and a clean GitHub Actions build (2026-10-27); the subsequent development journal reports 126 passing Node tests and a production build for the persistent-navigation update, with browser observations recorded separately. The client JavaScript measures 584.7 KiB raw / 174.0 KiB gzip, and Vite's >500 KiB raw-chunk warning remains; actual browser load-time acceptance is still open. GitHub Actions now runs tests and the production build on main pushes and pull requests; check the workflow result before relying on a change. A separate full type-check command is not yet configured; see foundation review.
Documentation
- Concept — the vision and agreed design direction
- Roadmap — milestones, priorities, and status
- Changelog — verified repository changes
- Agent rules — requirements for all coding agents
- Development journal — the creative process and experiments
- Decision register — decisions and alternatives
- Design reference — interaction and visual behavior
- Architecture — technical approach and constraints
- Content model — project data and media modules
- Module authoring — previews, full source documents and media authoring
- Repository connections — public sources and unresolved candidates
- Candidate project inventory — provisional creative-work memory for prototype content; not approved publication data
- Human–AI collaboration — attribution and evidence rules
- ChatGPT project instructions — instructions to paste into the ChatGPT project's settings
Intended technology
The implemented prototype uses Astro 7, TypeScript/native browser DOM modules and Marked for safely rendered Markdown; Svelte is only a potential future option, not a current dependency. GitHub-backed content and eventual deployment to the owner's VPS at babuni.dev remain part of the plan.
Working principles
Explore before explaining. Delight without obscuring usability. Record not just what was made, but who directed it, what choices were examined, and how the result was verified. Never treat generated mockups as implemented features.
License
No software license has been selected. Public visibility does not imply permission to reuse the source code.
Documentation audit #28 — 27 October 2026
The 11 core portfolio documents already contain a detailed, evidence-backed record. This audit preserves the original toy-box metaphor, endlessly recycled engraved-stone grid, contextual portal bubbles, grid-native small and big blooms, and a separate reader. It does not redesign those interactions or promote unapproved ideas into features.
Current release checkpoint (2026-10-29): 42 retained projects, 42 assigned 512px WebP portal images, three optional unique neutral tile identities, and 35 connected public repository sources. Milestones 1–4 are physically tested and accepted by Babuni.dev, including responsive use, keyboard/reduced motion and long sessions. Content review continues as living work. All current projects are authorized public; readable project/module pages, sitemap, metadata and on-demand module loading are built. A future publishing UI and production VPS/domain/HTTPS deployment remain separate work. See release-readiness audit for measured artifact sizes and verification limits.
Documentation publication dependency: The portfolio's imported project documents are revision-pinned static snapshots, not automatically live GitHub content. Changes just committed to other Babuni.dev repositories will not appear in project blooms until a deliberate npm run content:sync, npm run content:check, npm run test:grid and npm run build cycle is reviewed and the resulting content snapshot is committed. This audit edits Markdown only; it does not sync generated snapshots or deploy the site.
Document information
Author: Babuni.dev