Services
Services and how we work
We are a one-person studio. We take on few projects, and every one of them starts by reading the curatorial text. Here are the three things we do best, and how a project usually runs.
- 01
Exhibition and programme websites
Festivals, biennials, forums and research platforms. Multilingual, calendars, registration, audio guides, embedded video, launched on the exhibition's own schedule.
- For
- Art festivals, biennials, international forums, research platforms, societies and foundations.
- Includes
- Information architecture and content model
- Multilingual (zh, en, ja, ko)
- Exhibition and artist databases
- Calendars and event listings
- Registration and membership
- Audio guide pages
- Embedded video and maps
- Editor training
- Delivery
- Usually four to eight weeks from final key visual to launch, with live adjustments during the run.
- 02
Interactive and immersive visuals
Three.js, shaders and scroll-driven narrative turn the key visual into a space you can enter. Visitors start seeing the show in their first minute on the site.
- For
- Exhibitions with a key visual that should move on the web.
- Includes
- Three.js scenes
- Shader animation
- Scroll-triggered narrative
- Mask transitions
- Data-driven visualisation
- Game-like browsing structures
- Delivery
- Every effect is built with mobile performance and reduced-motion accessibility in mind.
- 03
Long-term maintenance and security
Hosting, vulnerability scanning and fixes, Cloudflare protection, performance tuning, newsletters and membership. Monthly retainers with regular meetings. Launch is where the work begins.
- For
- Institutions whose sites run for years, or that have been asked for a security audit report.
- Includes
- Hosting (DigitalOcean, AWS)
- Vulnerability scanning and remediation
- Cloudflare WAF configuration
- CSP and cookie security
- Performance and Core Web Vitals
- Newsletter systems
- Monthly meetings and reports
- Delivery
- Monthly retainer including fixed hours and meetings.
How a project runs
- 01Email us the dates, scale and languages.
- 02One online meeting; we reply with a requirements summary and a quote.
- 03While the key visual is in progress, we build the back end and content model.
- 04Once the key visual is final, we build the front end and interactions.
- 05Security scan before launch; maintenance after.
Our stack
Nuxt in front, WordPress behind. Editors keep the back end they know; visitors get fast static pages. A pure WordPress build is also possible, and we quote both options side by side.