Verified against current code
Every claim is traced to a file and line in the freshly-pulled repos. When code and the old docs disagreed, the code won.
As-Built · Verified
Orascom Portals — Engineering Documentation
Everything you need to develop and support the platform — verified against the running code.
The Orascom Portals are a real-estate sales platform: four React apps (one per persona) on a single Laravel API, a CRM middleware that reaches three Microsoft Dynamics 365 country orgs, a PDF service, and payments. This site is written so that after reading it you can pick up a ticket and ship it, or take a support case and resolve it — not just understand the shape.
Find what you need by intent
Section titled “Find what you need by intent”Understand a flowHow it works end-to-end, with a real sequence diagram, screenshots, and the exact request lifecycle.
Do a taskHow-to recipes: the exact files to edit to make a change (e.g. add a field end-to-end).
Learn by doingGuided tutorials: clone → run → change → test → PR → verify. Your first day, hands-on.
Look up a factReference: every endpoint field, rule, status code, real JSON, and the Dynamics field map.
Fix a production issueRunbooks: triage a support case by status code and log line, and find the layer at fault.
Explore each app
Section titled “Explore each app”Every app in the platform has a deep-dive — its screens, the exact APIs each one calls, its auth model, and the gotchas — with real screenshots from staging (PII blurred).
The Broker appExternal brokers: the dual-role broker + sales-manager build, the deal→invoice pipeline, EOI workflow, commissions analytics, Oman onboarding, whitelabel.
The Sales-Man appInternal CRM: lead→customer→sale, units, EOI + Taskeen, analytics — Microsoft-SSO only, country-scoped.
The Shopper appCustomer-facing: browse→reserve→pay online, and the post-purchase Pre-Delivery owner area.
The Shopper-Analytics appInternal BI: nine dashboards over shopper-portal data, each with its exact endpoints.
The Voyager admin (CMS)The Laravel back-office: the is_published publish-gate, catalog, personas, commerce, and CMS content.
Complete data modelThe exhaustive catalog: all 85 models by domain and all 125 enums, with CRM-mirror and PII flags.
The system in one paragraph
Section titled “The system in one paragraph”A broker/shopper/sales-man works in their own React SPA, which talks only to the Laravel backend. The backend owns the business logic and reaches each country’s CRM through the crms-middleware service — which, for a lead write, posts to an Azure Logic App that fans out to the right Dynamics 365 org (one per country), and for a read calls that country’s Dynamics OData directly. A separate Node service renders sales-offer PDFs. The reference flow walks one request through all of it.
How this is built to stay trustworthy
Section titled “How this is built to stay trustworthy”Real evidence
Screenshots and API shapes come from the live staging environment, not mock-ups.
No dangling questions
Unknowns are answered from code + staging, or moved to a separate KT tracker — they don’t live in the docs an engineer relies on.
No secrets
Credentials are used to access staging and understand config; no secret value is ever written here.