The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
One segment got the wrong product recommendation block.
A tagging mismatch sent one segment content meant for another. Caught it fast, fixed the mapping logic between segment tags and content blocks to be far stricter.
→ More personalization means more places a small mapping error can hide.
The mapping problem compounds as segmentation gets more granular. At 50 segments and 200 content blocks, no one's manually reviewing every combination. The approach that scales: treat segment-content assignments as a typed contract. Define what each content block expects —...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Two cuts of the same opener for Pletor 2.0. Same copy, same timing, different composition.
In the first one the words sit at opposite corners and the product cards drift in loose. In the second the cards arrive as tight stacks and the words swap corners.
I keep going back and forth on which one reads faster.
Vote in the comments, 1 or 2.
35 voted
65%
19 voted
35%
54 votes
Closed
2 for me. The tight stacks give the eye one clear place to land, so the message reads quicker. The loose drift in 1 looks beautiful but I found myself chasing the cards a bit
AetherOS is a web desktop for AI agents. The entire project sits inside a single HTML file. It starts with a boot screen. Then it opens into a dark workspace. The background has black animated particles. Everything runs on plain CSS and vanilla JavaScript. The site loads zero external dependencies and zero sound files.
The bottom dock holds seven apps. These tools manage four AI agents: Atlas, Sage, Bolt, and Vega. The Agents app shows them chatting and passing tasks. Files lets you browse a drive. Memory shows a live graph of what the system knows. Users can also modify a history timeline. Studio lets you test prompts. Flows builds node pipelines, and Cost tracks token usage.
Every window can be moved, resized, minimized, or maximized. The top menu bar has a model switcher. It routes tasks to Claude Opus 4.7, GPT-5.2, Gemini 3 Pro, DeepSeek V4, or Llama 4. The OS also has Spotlight search, sound toggles, and local API key inputs. The interface uses dark glass panels with blue highlights.
Building the node graphs in one single HTML5 file was tough. At first, the physics nodes pushed apart too hard. They floated right off the screen. Dragging extra lines while getting zoomed in also threw off the precise positions. I fixed the center gravity math. Then I divided mouse positions by the zoom factor. That stopped the unnecessary movement and kept the OS stable.😊
Rope Street Tattoo, Brașov (fictional)
Problem solved: a solo tattoo artist loses tourist leads to midnight DM replies and a day's pay to every no-show. Now any message becomes a priced, deposit-paid booking in under a minute, and confirmations, reschedules and waitlist refills run on their own.
The client: Mara, one chair, around the corner from Strada Sforii. Gloves on 7 hours a day, so DMs wait until midnight. Every quote needs size, placement and colour: about 7 messages per booking. Tourists leave before she replies, and 1 client in 7 doesn't show up.
What I built in Lovable:
→ Front door: describe the idea in English, German or Romanian. AI reads it, but Mara's own rules set duration, price and deposit. Only times that fit the job and the customer's days in town. Stripe deposit, booked. Cover-ups and hands go to Mara instead.
→ Autopilot: confirm or move at 72 h, a second nudge at 48 h, unconfirmed slots released 24 h ahead and offered to the waitlist, prep reminders, online consent forms, aftercare and touch-ups.
→ Owner area: Today, Week, Needs you with drafted replies, paste-a-DM replies, and the numbers: in four weeks of demo data, 304 messages not written and 38 h 53 min saved.
→ A demo clock to fast-forward and watch it work.
Try it: https://rope-street-tattoo.lovable.app
Owner view: footer → Studio → Try the owner view → Demo clock
Case study: https://rope-street-tattoo.lovable.app/story
A tourist who books two days ahead lands inside the 72-hour confirmation step. Does that booking skip the confirm-or-move message, or does it get the 48-hour nudge straight away?