01 · the collaboration

His work. A shared build.

Ahmed Abokamar needed a film portfolio he could maintain. Wael at WO! Studio led design and handoff; my contribution was the Studio CMS, backend, deployment and production engineering.

L1WO! Studio / WaelDesign direction, client handoff and the client communication relationship.

L2Omar G. NagyCMS, database permissions, content publishing, hosting and engineering improvements.

L3Ahmed AbokamarHis films, images, project details and editorial voice.

02 · the studio

Editing is not deploying code.

The private Studio edits the portfolio content. Saved drafts and published releases stay separate, and the public site is built from a published release.

1. 01EditProjects, films, page copy and press records in one private Studio.
2. 02SaveKeep draft work separate from the public release.
3. 03PublishBuild the static portfolio from a saved content release.

03 · video delivery

Short previews. Full films.

Studio can prepare a short, muted MP4 preview in the browser for review before upload. Full films remain on Vimeo; existing footage still needs original source clips for conversion.

1. 01Prepare locallyCreate a short preview and inspect its playback and actual file size.
2. 02Upload deliberatelyPreparation does not upload or publish footage automatically.
3. 03Keep the filmThe full Vimeo film remains available through the theater player.

04 · delivery status · October 2026

Deployed. Launch still pending.

The portfolio and Studio are deployed. Public indexing remains off pending the separate launch decision, and physical iOS playback verification is still open.

L1DeliveredEditable Studio, content releases, restored publishing and browser preview preparation.

L2RemainingClient source clips, physical iOS checks and the separate public launch decision.

L3Scope of proofEngineering delivery, without a traffic, revenue or conversion claim.