KH
Open navigation menu
Back to work
Abstract orbit of audio, content, analytics, and operational modules

Multilingual operations · Content platform

Quran Orb Admin

The internal administration platform for a Quran audio and content service spanning publishing, users, engagement, support, and configuration.

Visit product

Role

Sole frontend engineer who developed the administration application from its initial setup.

Scope

Analytics, reels, users, reciters, administrators, and operational support · Audio uploads, metadata, previews, duration extraction, playlists, and content associations · Permission-aware navigation, actions, fields, and content blocks · Arabic/English forms, validation, reusable tables, filters, uploads, and API/query hooks

Team

One frontend engineer, one backend engineer, one QA engineer, and a project manager.

Challenge

Turning complexity into legible state.

Challenge

Many modules had different data shapes and multi-step API flows, yet the operational dashboard needed one consistent multilingual interaction model.

Approach

I created shared REST and React Query hooks, form and validation patterns, reusable data tables and filters, permission gates, translation-aware fields, uploads, and explicit query invalidation after related mutations.

Outcome

Nontechnical operations staff could manage content, audio, playlists, users, publishing, analytics, and support through one consistent Arabic/English dashboard.

Selected contributions

  1. 01Built cross-module multilingual and RTL architecture from the application’s initial setup.
  2. 02Implemented audio upload, preview, automatic duration, metadata, cover, and status workflows.
  3. 03Built support tickets and replies, contact requests, suggestions, and settings content.
  4. 04Converted backend role permissions into reusable UI gates while preserving backend authorization responsibility.

Stack

ReactTypeScriptViteMUIReact QueryAxiosReact Hook FormYupi18nextApexCharts

Repository snapshot

81 of 84 commits in the inspected repository history were attributed to my identified Git identity.

The public consumer site is linked for product context; I did not build its landing page.

Continue exploring