Keep the calendar full, on brand.
Ship every aspect ratio from one idea, batch a month of on-brand content in a pass, and react while the moment is still live.
The calendar is a production problem. Treat it like one.
Every ratio from one idea
Feed, story, reel, thumbnail. The layout is computed, not pinned to a canvas size, so the composition recomposes for each placement instead of being dragged into shape nine times.
Batch weeks of content in one run
Put the month in a table — the product, the line, the date, the offer — and generate against it. A quarter of posts is a run, not a rota. What used to be a fortnight of assembly becomes a set you review.
React fast without going off-brand
When something is live and the window is hours wide, you don't have time to build from scratch and you can't afford to skip approval. Change the input, run the graph, ship the set — the brand rules came along with it.
The brand system is enforced by the graph, not by review
Type, colour, spacing, logo clearance and safe areas are operators, not a PDF someone is meant to have read. Off-brand output isn't caught later — it isn't a thing the setup can produce.
Save the format as a Recipe and re-run it each drop
When a format works — the weekly product post, the drop announcement, the recap carousel — it becomes a Recipe. Next month starts from the thing that already performed instead of from a blank canvas.
Same calendar, two shapes.
Today
One idea becomes a manual re-cut for every platform. The 9:16 is trimmed by hand, the square loses the headline, the thumbnail is exported at the wrong size. By the time the set clears review, the moment it was made for has passed.
With nooodles
The format is authored once with the variable parts exposed. One change — a new product, a new line, a new date — and the whole set regenerates in every ratio, on brand, ready to post.
The same graph can build the thing the post links to.
A content drop is a workflow — it hands your team files to schedule and place. But the link in the bio doesn't have to lead to a flat page someone else built: the same graph, the same brand system and the same table of drops can ship a scene your audience opens and plays with.
A page personalised per recipient, a piece people interact with, a live thing that reacts — built from the source that made the posts, so the two can't drift apart.
The content set
Every ratio, cut and caption card — files your team schedules across platforms.
- Mode
- Workflow
- Who opens it
- You and your team
The thing they tap through to
An interactive piece or a personalised page — the audience opens it and does something.
- Mode
- Scene
- Who opens it
- Your audience
Start from something that already works.
These ship with the beta — open them, run them, or take them apart.
Social Cutdowns
WorkflowCut one hero into every duration and platform.
by Jacques ParysAspect Fan-out
WorkflowReframe one master into every ratio and placement.
by Jacques ParysLookbook Grid
WorkflowLay a product set into styled grid layouts.
by Jacques ParysPersonalised Page
SceneGenerate one page per recipient from a table.
by Jacques ParysWhat social teams ask first.
Does the social team need to learn the node graph?
No. One person sets the format up — no code needed — everyone else gets the handful of controls that author chose — pick a product, type the line, set the date, generate. They work in a form, not a graph.
Won't batching make everything look identical?
Only if you build it that way. What's fixed is the brand system; what varies is up to you — layout variants, motion behaviour, colour, generated texture and backdrop passes can all be part of the run. The point is that the sameness is deliberate where you want consistency, and parameterised where you don't.
Is this video too, or only stills?
Both. It's a procedural engine with real motion, 3D and physics, so cutdowns across durations, animated type, loops and turntables come from the same setup as the stills. A video variant is another output, not another project.
Does it post to the platforms for us?
nooodles produces the content — every ratio, every duration, named and sized for where it's going. Scheduling stays in whatever you already use; the files drop into that pipeline. The work it removes is the assembly, not the calendar tool you're happy with.
How fast can we actually react to something?
Fast, because the reaction is an input rather than a build. If the format already exists as a Recipe, responding is changing the copy or the product and running it — and the whole set comes out in every placement at once, already inside the brand rules, so approval isn't the bottleneck either.
Build the format once.
Free to start, nothing to install. Or tell us about your content calendar and we'll walk you through it with your own work.
Working with a team?
Tell us where to reach you and we'll set up a walkthrough.
No spam. A real reply from a human.