Studio dossier / File 001

Name
Rendani Manugeni
Practice
Function Psi
Base
South Africa / remote
Filed
November 2026
Open for select projects

Not a bio.
A dossier.

I’m Rendani Manugeni. I build interactive things for the browser — the kind that need a camera, a timeline, and a reason. Function Psi is the name I do it under.

Open a channel
01

The practice

Function Psi is not an agency with a meeting room and a fruit bowl. It’s me, a laptop, and whoever I rope in when a project needs another brain.

I work from South Africa, usually with people in other time zones, usually on things that don’t have a reference yet. Some of it is a product launch. Some of it is a tool that only needs to exist for one person. The common thread is that the browser is the material, not just the delivery method.

Based South Africa SAST / UTC+2
Working Remote worldwide Async-friendly
Focus 3D · Web3D · Web Design and build
Status Open for select projects A small number at a time
02

Origin

I got into this the usual way: opening dev tools on sites I liked and refusing to leave until I understood how they moved. That turned into a habit of building the thing instead of describing it. The habit never wore off.

The name comes from two ideas I keep bumping into. A function is input, rule, output. Psi is the symbol psychology uses for the mind, and physics uses for a wavefunction. I liked that one letter could mean a system and a hunch. That is the job.

“The work should feel inevitable after you see it. Not before.”

What I’m not interested in: templates with the serial numbers filed off, motion that exists because the timeline was empty, and websites that make you wait through a showreel before they tell you what they do.

03

Method

01

Find the one move.

Before layout, before code: what is the single thing someone should remember? A camera move, a piece of type, a sound, a joke. Everything else supports it.

02

Build the skeleton in the browser.

I prototype with real type, real scroll, and real performance. A static comp can lie about rhythm. A browser cannot.

03

Make the machine behave.

Responsive, keyboard, reduced motion, slow devices, no WebGL. The polish is in the fallbacks as much as the showpiece.

04

Cut the extra.

If a transition does not explain hierarchy or earn a smile, it goes. Restraint is part of the art direction.

04

Toolkit

The stack is whatever gets the idea into the browser without sanding off the interesting edges. These are the tools I reach for most, and the ones currently on the bench.

Daily HTML, CSS, JavaScript, Git The floor
3D Blender, Three.js, GLSL The depth
Motion GSAP, ScrollTrigger, Lenis The timing
Sound Web Audio, synthesis, reactive systems The pulse
Design Figma, type, art direction The argument
Shipping GitHub Pages, static-first, performance budgets The proof
On the bench

WebGPU, compute shaders, procedural type, and a small pile of ideas that are not ready to be pages yet.

05

Colophon

This site is the portfolio and the proof. It is hand-written HTML, CSS, and JavaScript — no page builder, no template, no theme with the name changed. The 3D opening is a real-time Three.js scene. The motion runs on GSAP and ScrollTrigger, with Lenis for the scroll. The type is Bricolage Grotesque, Instrument Serif, and DM Mono.

Build
Static files / GitHub Pages
3D
Three.js 0.170 / custom GLSL
Motion
GSAP 3.13 / ScrollTrigger / Lenis
Type
Bricolage Grotesque / Instrument Serif / DM Mono
Data
GitHub REST API / no analytics

No tracking pixels. No advertising cookies. No mystery scripts. If something feels expensive, it is probably because someone spent time on the easing.

06

Contact

Have a strange idea, a sharp constraint, or a project that does not have a reference yet? Good. Those are the ones worth opening.

The console on the contact page builds a short brief in your browser, then copies it so you can paste it into a DM on X. Nothing is submitted to a server, and there is no email address to forget.

Replies usually within 48 hours / South Africa / remote worldwide