A film is render(t).

The challenge

Explain an idea, not a feature list.

Shaderera has no timeline and no templates. A film is a function from time to a frame, and the toolkit checks, renders, reviews and delivers it. The site had to make that idea clear to people who write code, show that the films are real, and get a visitor from the first screen to an installed project.

Scroll is t

A hero that works the way the product does.

The SHADER ERA wordmark is drawn from particles. Scrolling moves t: the letters break apart and come back, and scrolling back gives the same frame back, which is the product’s promise shown rather than told. A thin HUD along the top counts t and the frame number.

Below it, one line carries the whole idea: a film is render(t).

Posters on four grounds

Swiss type, four colours, nothing else.

Every section is a poster on one of four grounds: paper, ink, red and cobalt. Headlines are set large and tight in Inter, and every label, code sample and terminal line is in IBM Plex Mono. The palette and type come from the films themselves, so the site and the work read as one brand.

The films and the case for agents

Show the work, then show how it was made.

Three films, MATTER, P(DOOM) and WALLLOOM, each get a poster with a looping cut, the 16:9 and 9:16 versions, the facts and a strip of frames, and open in a branded player. Real source from MATTER sits beside the frame it draws.

Six chapters follow: Brief, Look, Exact, Revise, Scale and Prove. Each one is a short exchange between a person and their agent, shown next to the contact sheet, drafts or review it describes.

From the page to a project

One prompt, any agent.

The site ends where the work starts: copy one install prompt into any agent, or follow the /agents page step by step. A catalog lists the add-ons, each with its own page and preview, and the FAQ answers the plain questions in the same words search and answer engines read.