Frontend developer

Statement of Work (SOW): Front-End Development Purpose This Statement of Work defines the scope, deliverables, responsibilities, and timelines for the production-ready front-end development of a cultural heritage collection digital platform. The developer will build a highly performant, accessible, and culturally resonant user interface based on the provided designs and a headless CMS architecture. Scope of Work The developer will provide engineering and front-end architecture services across the following areas: 1. Core Architecture & Tech Stack Framework: Build the application using Next.js (App Router) to ensure optimal Server-Side Rendering (SSR) and Static Site Generation (SSG) for SEO and performance. Styling & Components: Utilize Tailwind CSS for styling. The integration of modern component utilities (e.g., shadcn/ui, daisyUI) is permitted to accelerate development while ensuring strict adherence to DBF design tokens. API Integration: Consume data from the headless Strapi CMS (and Nest.js if necessary) via REST or GraphQL APIs. 2. Internationalization & Multilingual Support (English/Arabic) Full Right-to-Left (RTL) layout support for the Arabic interface, including mirrored navigation, grids, and UI components. Implementation of localized UI elements, date/number formatting, and dynamic font pairing optimized for both Arabic and Latin typography. Seamless, state-retaining language switching across all pages. 3. Interactive Features & Exhibition UI Faceted Search & Discovery: Build a highly responsive search interface featuring multi-category filtering, sorting, and dynamic result counts based on the Strapi API payload. Deep-Zoom Image Viewer: Integrate a high-performance tiled image viewer (e.g., OpenSeadragon or a React equivalent) to allow users to inspect high-resolution cultural assets closely. Interactive Exhibition Galleries: Develop immersive, fluid layouts for digital exhibitions, including masonry grids, carousels, and interactive timelines. Multimedia Streaming: Implement accessible HTML5 audio/video streaming players for oral histories, curatorial walkthroughs, and educational media. Deliverables The developer will deliver a fully functioning web application by August 1, 2026: Production-Ready Repository: A clean, well-documented, and optimized Next.js codebase hosted via the GitHub version control platform. Fully Integrated UI: A complete front-end environment seamlessly mapped to the Strapi production/staging API endpoints. Responsive Layouts: A platform fully optimized for desktop, tablet, and mobile breakpoints. Deployment Configuration: Production build configurations and environment variable setups optimized for DBF's Oracle Cloud Infrastructure. Project Timeline To meet the hard deadline of August 1, 2026, the project will follow an accelerated phased approach: Phase Description Targeted Completion Phase 1: Setup & Discovery Repo initialization, design token mapping, architecture alignment with back-end team. June 20, 2026 Phase 2: Core Layouts & i18n Navigation, global components, English/Arabic RTL framework integration. July 5, 2026 Phase 3: Interactive Features Faceted search, deep-zoom implementation, media streaming, and galleries. July 20, 2026 Phase 4: QA & Launch Prep Performance optimization, cross-browser testing, final API tuning, and handover. August 1, 2026 Roles and Responsibilities Developer Responsibilities Deliver clean, modular, and performance-optimized front-end code. Ensure application accessibility (WCAG 2.1 AA compliance standards) and cross-browser compatibility. Collaborate closely with the DBF back-end team to align on API schemas and payloads. Client Responsibilities (Critical Dependencies) Provide finalized Figma files, design tokens, and wireframes prior to the start of Phase 2. Provide fully functional and populated Strapi CMS / Nest.js API endpoints with reliable staging data for integration. Provide all translated localized copy and metadata assets (English and Arabic). Designate a primary technical point of contact for rapid API or design clarifications. Assumptions and Constraints Out of Scope: Back-end server configuration, database administration, Strapi plugin development, and content entry/translation are strictly out of scope. Code Ownership: Upon final payment and project acceptance, all source code and intellectual property developed under this SOW will belong exclusively to the client. Change Control: Any additions to the scope, features, or architectural requirements outlined in this document will require a formal, mutually signed Change Order. Acceptance Criteria Deliverables will be considered accepted when: The website matches the approved Figma designs across mobile and desktop breakpoints. The English and Arabic layouts render correctly without alignment or text-truncation breaks. The codebase passes a mutually agreed-upon suite of functionality tests and builds successfully for production. Written sign-off is received from the client Project Manager.