Post and carousel masters
Layouts that hold one look across six very different photographs, so the grid reads as one company when the profile opens
a set, not a stack of graphics
Social media design · UAE
A feed here is a publishing surface with two scripts on it and rules about what may be claimed. Webzenia builds the masters your own team can fill, in both.
Send us the last month of your feedWhat the system has to hold
A feed is read as one object, published in two scripts, and governed by rules about what may be claimed. A template set has to hold all three or it holds none of them.
Nobody judges a post. They judge the nine tiles visible when the profile opens, and they are checking whether this is a real company, not whether they enjoyed Tuesday.
Every master exists as an English and an Arabic layout, built together. An Arabic caption under an English tile is not an Arabic post, and the difference is visible to the reader it was for.
Promotional publishing here is a permitted act, and what a tile claims is part of it. The claim and the disclosure become design decisions, made in the master rather than argued per post.
What we design
Six masters rather than sixty posts. Each one is a layout your team fills, in either script, without deciding anything we already decided.
Layouts that hold one look across six very different photographs, so the grid reads as one company when the profile opens
a set, not a stack of graphics
Vertical frames with the caption headroom and the safe areas already allowed for, so nothing important sits under a progress bar
formats built for a phone, not cropped to one
One idea in every placement crop, with the disclosure designed in rather than added at the end
a set you can test without redesigning it each round
A batch built against a calendar rather than a Thursday afternoon, so publishing survives the week the person who posts is travelling
a month that already exists
Photo wells, headline zones and logo positions marked as swappable, with the layout itself locked
what a non-designer may change, decided in advance
The commercial seasons this market actually trades on, with the creative produced weeks ahead because the stock and the offer are decided that far out too
a season, not a scramble
How a feed gets made
A JLT commodities trader under DMCC will have tried two of these before the third is even proposed, usually in this order.
| A per-post retainerBought by the count, monthly | The team, in their own toolMade between other jobs | A designed master setBuilt once, filled weekly | |
|---|---|---|---|
| The first post | Good, and produced faster than you could have managed. | Fine, because somebody copied the last one that worked. | Good, and the second one takes twenty minutes. |
| The fiftieth post | A different designer, a different look, the same invoice. | Nine tiles that each belong to a slightly different company. | The same look, because the layout was never the variable. |
| When Arabic is needed | Quoted as an addition, and delivered as a translated caption. | It does not happen, because nobody in the office can set it. | A master already exists, because it was drawn with the English one. |
| When a claim is checked | Whoever wrote the caption that month decided what it said. | Nobody checked, because nobody knew there was anything to check. | The claim rules travel with the kit, so the tile cannot say it. |
| If the supplier changes | The look leaves with them, and the next one starts over. | Nothing changes, because there was never a system to lose. | Nothing changes, because the system is in your own workspace. |
A per-post retainer is a reasonable answer when the volume is low and the brand is settled, and we will say so rather than sell against it. It stops being reasonable at two points: when a second script is genuinely needed, and when somebody has to be accountable for what a tile claims. Neither is a volume problem, which is why buying more posts does not fix either. If what you want is someone to run the account rather than build the system, that is social media marketing, and we will point you there.
The UAE context
Webzenia has worked with Gulf clients since 2018. Four things decide whether a feed does its job here, and none of them is how many posts a month it carries.
The National Media Authority issues an advertiser permit to the individual who publishes, and it covers promotion whether paid or unpaid. What your own brand may promote is scoped by your trade licence. Both land on the creative: what a tile claims stops being a copywriting choice.
The logo moves, the safe area moves, the caption block moves, and the type sits on a different vertical rhythm. Pouring translated text into a layout drawn for Latin gives you a tile that is technically bilingual and visibly an afterthought to the reader it was made for.
They are looking for recency, consistency and evidence that a real company is behind it, in about the time it takes to scroll one screen. A Dubai Marina clinic on a mainland licence is checked this way by a patient and by a supplier, and both are asking the same question.
At an Al Quoz F&B producer on a DET mainland licence that is a marketing executive with three other roles. A kit works when the swappable parts are obvious and everything else cannot be moved. A guideline document does not survive that moment.
What the engagement covers
Six parts, and the last two are the ones a per-post retainer never reaches. The kit is the deliverable, not the posts made along the way.
We settle how the feed reads as a whole before any single tile is designed, because the grid is the thing a visitor actually sees first.
Each master is drawn as an English and an Arabic layout in the same pass, on the same grid, so neither is a retrofit of the other and both ship together.
We produce a real month against the calendar, which is how a master gets tested by actual content rather than by the three examples that suited it.
One idea resized to each format it has to appear in, with the subject and the message surviving a square, a portrait and a vertical without being re-decided.
The Arabic set is read by someone who reads it, and the claims are checked against what you can actually evidence rather than against what reads well.
The locked templates go into the account your team already opens, in your organisation rather than ours, with the source components alongside them.
Our stack
The kit behind a feed a non-designer can fill without breaking it. Select one to see why it earns its place, and what we do with it that most do not.
A feed is one system rendered many times, so the masters have to be components rather than files. Change the logo position once and it should move on every tile that ever used it, including the mirrored ones.
We build the English and the Arabic layouts as one component set, so a change lands on both directions at once. Maintaining them as two libraries is how a brand ends up with two slightly different brands.
How the work runs
The order is set by what your team has to be able to do alone afterwards. Everything before the handover exists to make that moment work.
We settle how the grid reads as a whole, then draw the masters for each format. Whether Arabic is in scope is decided here rather than later, because it changes the number of layouts rather than the finish on them, and retrofitting a direction means redrawing every one.
A full month is produced from the masters rather than three showcase tiles, which is the only way a template gets tested by content that does not suit it. The Arabic set is read by someone who reads it, and anything that only worked in one direction is fixed while it is still one file.
The templates go into your own workspace with the swappable and locked elements already set, and the source components go with them. Alongside the kit you get the claim rules in writing: what a tile may say about the business, and what needs evidence behind it before it is published.
The kit lands in the tool that person already opens, with the claim rules beside it.
Our commitment
Feeds fail at the second script, at the claim, and at the moment the person who posts opens the kit alone. These four are about that.
Nothing ships unread
Every Arabic tile is read by someone who reads Arabic before it leaves us, and the layout is drawn rather than translated into. A set that has never held real Arabic text at real length has not been tested.
Unevidenced claims never ship
If a tile asserts something we cannot trace to a document you hold, it is reworded or cut, and we say which. That is a design check rather than compliance advice, and where a claim needs a lawyer we will say that instead.
Handover happens in your tool
Not the tool we prefer and not as a document. If your feed is filled in a browser by somebody with four other jobs, the templates are locked and delivered there, and we will tell you before the engagement if that changes the scope.
Your workspace holds the kit
Templates and source components sit in your own account, in your organisation. A kit hosted in an agency workspace is a kit you lose on the day you change agency, which is exactly the day you most need it.
Common questions
Keep exploring
Marks, a bilingual system, and the files your team can run.
A position your licence supports and a buyer can verify.
A mark drawn in both scripts, and made to be fabricated.
A deck built for the pocket of capital reading it.
The document a vendor registration checks before anyone reads it.
One master that sets decks in both directions.
Written twice, because a committee watches it twice.
One permitted shoot, cut for every place it sells.
Shot to two marketplace specs, against the sellable pack.
Next step
Send the profiles and a month of posts. We will come back with what to standardise, what to pair in Arabic, and what to stop publishing.
Tell us what you need.