Some parts of this page need JavaScript.

Skip to main content

We use cookies for analytics. Privacy

Client delivery · Next.js

Ladie One

An artist portfolio built around the work

Visit live website (opens in a new tab)What we deliveredAll work
Ladie One website
Next.js

In short

A custom artist website bringing murals, studio work, collaborations and press into one visual portfolio, with an inline studio-visit booking panel.

Platform
Next.js
Tools used
Next.js / React / TypeScript / Tailwind CSS / Framer Motion

Inside the project

01 / 04

The homepage.

Ladie One1 / 4

Ladie One homepage on desktop, with the graffiti tag logo and artist intro

The homepage.

The brief

Built around the people using it

A working muralist needed a website that could present large-scale murals alongside graffiti, studio work, collaborations and press. The browsing experience had to carry the artist's visual identity while keeping the artwork easy to explore.

The handoff

Built for the team that runs it

A consistent visual system connects portfolio browsing, the artist biography and studio visits across desktop and mobile.

The delivery

What we delivered

  • Give each mural its own space

    The homepage uses an asymmetric selected-work layout to let large murals, close details and project labels sit together. The design follows the shape and character of the artwork.

  • Browse from overview to detail

    Visitors can move between mural, graffiti and studio categories, then open individual images in a keyboard-accessible lightbox. The same browsing structure adapts to a phone.

  • Connect the work to the artist

    Biography, collaborations and press pages build out the story around the portfolio. An inline Square panel gives visitors a way to arrange a studio visit within that experience.

How we work

How a change reaches production

The same five gates for our own products and for yours. Nothing reaches your customers on the strength of a demo.

  1. 01 · Isolate

    Its own branch and workspace

    Every change starts in a separate copy of the code, so work in progress never touches what is live.

    git worktree add .worktrees/your-change
  2. 02 · Build

    Engineers with AI agents

    Agents write and test code beside us. They hold no passwords: every call they make goes through our gateway, which checks it and logs it.

    agent → gateway → policy · audit · call
  3. 03 · Prove

    Evidence, then review

    Tests, before-and-after screenshots of the running app, then independent reviewers. It does not move on until no serious finding is left.

    review: 0 high · 0 medium → pass
  4. 04 · Ship

    Deployed and checked live

    The pipeline builds and deploys. Then we check the running service itself, not just a green build.

    replicas 1/1 · image sha matches · health 200
  5. 05 · Watch

    Checked every night

    Each integration we run is tested against its provider every night, so a changed API is caught before your team notices.

    nightly: each integration vs its provider

Working on a similar problem?

Start with your existing website, the workflow that needs attention and what your team needs to manage.
Discuss your project (954) 834-3426