S/01
Web platforms
Client sites that editors can actually run: custom post types, structured fields, sane templates, consent and analytics wired up correctly instead of bolted on afterwards.
Open to interesting problems · RemoteBased in Europe · Working worldwide
engineer, occasional automator
BISHALI build software that survives contact with reality.
I ship client platforms, internal tooling and agent-driven automation — the kind of work that has to keep running on a Tuesday morning when nobody is watching it.
01 — About
The short version
A working note on what I do, how I got here, and what I'm useful for.
I'm a full-stack engineer who spends most of his time in the unglamorous middle of things — the integration that has to reconcile two systems that disagree, the CMS that has to stay editable by non-engineers, the automation that runs at 10:30 every morning whether or not anyone remembers it exists.
Most of my work has been agency-side: client web platforms built on WordPress and custom fields, product interfaces in Next.js and Supabase, and a growing pile of n8n and MCP-based automation that quietly removes manual steps from other people's days.
Lately I've been deep in agentic systems — self-hosted orchestration, local models, tool-calling that actually behaves. Less demo, more uptime.
the part I actually enjoy: making a complicated
thing feel obvious to the person using it.
- Systems integration
- Automation design
- CMS architecture
- Agentic AI
- Technical writing
- Team lead
02 — Services
What I take on
Four things I do properly, rather than twenty I do adequately.
S/02
Product engineering
Dashboards, portals and internal tools built end to end — schema through interface — with the auth, state and edge cases handled before they become support tickets.
S/03
Workflow automation
Recurring manual work turned into a reliable pipeline: scheduled sweeps, reconciliation between systems that disagree, feature-flagged rollouts and replayable runs when something goes wrong.
S/04
AI & MCP integration
Model Context Protocol servers, agent workflows and retrieval-ready documentation — built so a model has the right context and the right tools, not a bigger prompt.
03 — Selected work
Things I shipped
Four builds that earned their place — client platforms, internal automation, and one full product.
PROJECT 01FULL-STACK
ShelfSync
Organisation inventory automation · Next.js + Django
Office stock-keeping without the spreadsheet. Staff photograph a shelf or just say what they took; the system resolves it against the catalog, moves the stock and predicts what's about to run out.
- One photo or phrase resolves to several products at once — "potatoes and rice" is two items, not one guess
- Anything the catalog doesn't stock comes back as a tap-to-add chip instead of failing silently
- Stock history is reconstructed from real purchase receipts, so it survives a reload — no client-side event log
- EWMA consumption model gives days-to-depletion and a reorder quantity over a two-week horizon
- CSV / Excel import round-trips with the export, so a count can be corrected in a spreadsheet and pushed back
- Every AI path degrades to trigram search rather than erroring — the endpoints never 500
Next.jsDjango + DRFPostgreSQLRedisClaude API
POST /products/identify (shelf.jpg)detected potato, rice, oil, cardamommatched 3 catalog idsunmatched cardamom → tap to add---// consumption model, α = 0.3sugar dtd 3d reorder 12 kgrice dtd 19d reorder —[fallback] no key → trigram search
PROJECT 02MULTI-YEAR
Travel & lifestyle platforms
Sole WordPress engineer · African Tours · Scuba Travel · Hummingbird · Tour Pacific · Waidmann · Intoit
A portfolio of production travel and hospitality sites that I maintained single-handedly — content architecture, consent and tracking, and the long tail of bugs that only appear on live data with real editors behind it.
- 8–10 live sites kept running solo, with near-zero downtime across them
- Carbon Fields and SCF content models editors can run without calling a developer
- A blog index silently returning nothing — a block slug mismatch, not the query everyone assumed
- Untangled a Cookiebot / GTM interaction that broke the consent banner; tracking now waits for consent properly
- Repeater-context bug that was rendering the wrong product data site-wide
- RAG-ready architecture and business-logic docs written per site, so the next person isn't reading my mind
WordPressCarbon FieldsSCF / ACFElementor ProGTMCookiebot
wp estate:status --allafricantours.se upscubatravel.se uphummingbirdmeetings.se uptourpacific.se upwaidmann.se upintoit up---// one maintainer, near-zero downtimeconsent gate → gtm deferred
PROJECT 03INTERNAL
Meal booking sweep
n8n automation · Slack + Sheets + ERP
The office lunch count came from three places that disagreed — a Slack thread, a spreadsheet and the ERP. The kitchen cooked to the highest number, so food went in the bin every day and people who booked sometimes went without. This reconciles all three before the 10:30 cutoff, chases the gaps itself, and hands the kitchen one trustworthy figure.
- Meals cooked now track what's actually eaten — surplus is close to nothing
- Mismatches are DM'd to the person automatically instead of chased by hand each morning
- Cancellations block on a reason, captured behind a feature flag before it reached the ERP
- Replay engine for failed runs, after fixing token-ownership bugs in it
- Timezone bug hunt: sweeps were silently no-op'ing on date boundaries
- Shipped with a handover doc and Mermaid flow diagrams, not just a working canvas
n8nSlack APIGoogle SheetsERP integration
// three sources, one numberwindow 08:00 → 10:30sources slack:#meals · sheettarget erp360.bookings---mismatch → dm sentcancelled → reason requiredover-order → trimmed pre-cutoffresult: cooked ≈ eatenwaste ≈ 0
PROJECT 04INTERNAL
Availability sync
n8n + Slack · Multi-channel status automation
Who's out, who's on leave and who's heads-down was posted in whichever channel someone remembered, so every team held a different version of the truth. One update now propagates everywhere it's relevant.
- A single status change fans out to every channel that needs it — no repeat posting
- Keeps team, project and standup channels consistent instead of drifting apart
- Runs on the same self-hosted n8n instance as the rest of the internal automation
n8nSlack APIWebhooksSelf-hosted
event: status.changedmember @teammatefrom available → on leave---#team-platform synced#proj-northlight synced#daily-standup syncedone update, every channel current
04 — Achievements
Worth mentioning
Competitions, responsibility, and the quiet kind of record that only shows up when nothing breaks.
- Winner · 2024
Summer Hackathon
First place, competing against internal teams on a fixed clock — build, demo, defend.
- 1st runner-up · 2026
Hackathon, again
Back on the podium two years later, with a bigger field and a harder brief.
- Responsibility
Team lead
Led a development team alongside shipping my own work — scoping, review, unblocking, and carrying the handover discipline into how the team documented things.
- 8–10 sites
Near-zero downtime
Maintained an estate of 8 to 10 production websites single-handedly, keeping them online through migrations, plugin churn and client deadlines.
05 — Toolbelt
What I reach for
Next.jsApp Router · TS
SupabaseAuth · Postgres
PostgreSQLSchema · queries
WordPressThemes · plugins
Elementor ProCustom widgets
Carbon Fields / SCFContent models
n8nSelf-hosted flows
MCPServers · tools
DockerCompose · Dokploy
OllamaLocal inference
PHPHooks · WP internals
TypeScriptEnd to end
06 — Process
How the work runs
Same shape whether it's a two-week fix or a quarter-long build.
01
Scope
I ask the annoying questions early — edge cases, who owns the data, what happens when the third-party API is down. Cheaper now than in week six.
02
Build
Small increments you can see running. Feature flags where a change is risky, so nothing ships as an all-or-nothing switch.
03
Prove
Real data, off-hours overrides, replays of the failure paths. If I can't break it deliberately, it's probably ready.
04
Hand over
Documentation your team can actually use — architecture notes, flow diagrams, runbooks. Nothing that only works while I'm around.
07 — Words
What people say
Colleagues and clients, in their own words.
I had the chance to work closely with Redwan almost one year. What stood out most was how he handled the client-facing side of our projects, particularly on African Tours and Hummingbird, from sorting out tricky form and content issues to keeping both client accounts running smoothly day to day. Redwan has a real skill for translating client needs into clear direction for the team, and always made sure we understood not just what to build, but why it mattered to the client. Beyond the client work, he also drove a lot of the automation improvements for the organization that made our day-to-day smoother. The meal booking flow is a great example — it took a process that used to rely on manual back-and-forth and turned it into something automated and dependable that just runs in the background now. He also pushed us forward on the MCP and agent tooling side, which has genuinely changed how we approach problems and think about what's possible with the tools we build. What I appreciated most is that Redwan leads with patience and clarity, even when things get hectic. I learned a lot working alongside him, and I'd gladly work together again.
During my time at Strativ as the sole project manager for website projects, Redwan had been a key player in the PHP team in developing solutions and independently collaborating with some of our longest-running customers. I've seen him learn relentlessly, process feedback with a sound strategic acumen, and augment his processes and performance rapidly over time. His promotion to a team leadership role was well-deserved. Beyond the timeline of my management, I've followed his work that crossed the spheres of Wordpress development onto automations and custom collaboration tracking portal, among other things. He has also consistently been a team player, adding valuable "human element to the development machine" by supporting, mentoring, and uplifting peers from his own team and beyond. Wishing Redwan great success ahead with high confidence!