One box for everything
The editor pastes from a word processor, the layout breaks, and the developer is asked to fix the spacing.
Services
Content management and publishing
Someone needs to change a price on the site. The request becomes an email, waits for the developer, and ships three days later with a different price still showing in the Arabic version. A content system is not a text box; it is a decision about which fields exist, who may change them, and what has to be true before a page goes public.
Who it is for
- Sites where every text change goes through the person who built the site.
- Businesses publishing the same page in Arabic and French, and drifting apart.
- Teams that cannot say who published the offer still on the home page.
Problems it solves
Published in one language, forgotten in the other
The Arabic page still shows last year's prices, and nothing anywhere flags the two versions as different.
Nobody knows who published it
An old offer stays live for three months: no history, no named author, no way back to the previous version.
Use cases
Structured content types
A service, an article, a project: fixed fields instead of one free-text page. The fields the site needs are the fields the editor fills.
Preview before publish
The real page, at its real URL, with both languages side by side, before anyone outside sees it.
Draft, review, publish
A draft state, one reviewer, and a published version a second person can roll back without a developer.
Bilingual pairing
Every entry knows its counterpart; publishing Arabic without French is blocked or flagged, by a rule you choose rather than one we assume.
What is in scope
Fixed scope. Fixed price.
Agreed in writing before anything is built. You approve before we start.
- A content model: types, fields, required fields and their validation
- Editor screens for the people who will actually type
- Preview, drafts and scheduled publishing
- Roles: author, reviewer, publisher, and what each may change
- Migration of the existing pages into the new structure
- Training, and one written guide per role
How it is delivered
- 01
List what gets published and by whom
Interview the person who sends the price list, the one who adds the photos and the one who approves. That interview decides the roles more than any management meeting.
- 02
Model the content before the form
A field that is optional in the model becomes a paragraph of apology on the page.
- 03
Make the wrong state impossible
Publishing is blocked while a required field is empty, and a language mismatch is visible in the list rather than after publication.
- 04
Train, then watch the first real publish
We sit through the first publishing round, because the first real page finds what the test data did not.
FAQ
Questions about this service.
What owners usually ask before requesting a quote for it.
Can we just use WordPress or an existing system?
Sometimes yes, if the content fits its model and the editing screen is acceptable to the people who will use it. We will say so when a custom admin is not worth its cost.
Can we publish in Arabic only for a while?
You can allow it, but then decide what the other URL shows: a redirect, the other language, or an empty page. The third is the worst, and it is what happens by default.
Who is allowed to publish?
Your decision, not ours. The common arrangement is an author who edits, a reviewer who approves and one publisher who makes it public, with a log naming who did what and when.
Does this remove the developer entirely?
No. A new page template, a layout change, a new field: still code. What it removes is the routine request — a price, a photo, a paragraph — and the queue that comes with it.
Start a project
Want this scoped for your business?
Send the brief. It comes back as a written scope and a fixed quote before anything is built.