Full-Stack Developer Needed: Next.js Website, Visual CMS & Admin Dashboard with PHP API Integration

PRD: https://docs.google.com/document/d/1tTOSwAqNa6Ddrlslo-ISlbJw0wtdHjZM5nM3-GZ-xWE/edit?usp=sharing We are looking for an experienced full-stack developer or small development team to rebuild the website for Shuyi (数易赋能, numforlife.com), a spiritual wellness and personal guidance platform offering numerology calculations, tarot readings, personalized insights, and membership services. This is not a WordPress or Elementor website project. The existing website will be rebuilt as a modern, responsive, API-driven web platform using Next.js, React, TypeScript, and Tailwind CSS. The project also includes a visual content management system and a secure website administration dashboard. The Shuyi mobile app remains the main product experience. The website will provide a lighter experience focused on brand awareness, SEO, simplified tarot and calculation previews, membership conversion, and directing users to download or open the mobile app. Project Objectives The developer will be responsible for: * Rebuilding the existing Shuyi website using Next.js, React, TypeScript, and Tailwind CSS * Creating a clean, premium, mystical, and mobile-first user interface * Supporting both light mode and dark mode * Integrating the website with our existing PHP backend through secure APIs * Rebuilding selected Flutter tarot flows for the web using React/Next.js * Developing simplified tarot and numerology preview experiences * Creating a lightweight user dashboard * Building a secure website admin dashboard with role-based access * Implementing a drag-and-drop or block-based CMS for non-technical content editors * Migrating relevant content and URLs from the current WordPress/Elementor website * Implementing SEO, analytics, performance optimization, and conversion tracking Recommended Technology Stack Frontend: * Next.js * React * TypeScript * Tailwind CSS * Reusable component and design-token system * Responsive, mobile-first architecture * Light and dark themes Backend: * Existing PHP backend will remain in use * The frontend must communicate with the backend through secure APIs * The frontend must never connect directly to the production database * Existing MySQL/database infrastructure will remain the source of data CMS and Admin: We are open to a suitable recommendation based on cost, maintainability, and ownership. Possible approaches include: * Builder.io or Plasmic for selected visual editing areas * Custom block-based CMS * React Admin, Refine, or Ant Design Pro for the admin dashboard * PHP-based admin dashboard if appropriate * Directus or another suitable structured-content solution The successful developer should recommend the most practical architecture before implementation. We prefer avoiding unnecessary recurring platform fees and vendor lock-in. Public Website Scope The website is expected to include: * Homepage * About and brand story pages * Numerology/calculation landing pages * Simple calculation input and preview result pages * Tarot Lite experience * Membership comparison and marketing page * Lightweight user profile/dashboard * Limited website-generated calculation history * FAQ and SEO landing pages * Privacy Policy, Terms of Use, and disclaimer pages * App download and open-app calls to action * Shareable preview result pages where applicable * Responsive navigation and footer * Redirects from relevant existing WordPress URLs Tarot Lite Web Experience The developer will receive access to the existing Flutter tarot application as a functional and visual reference. The web version should be rebuilt natively in React/Next.js and may include: * Question input * Topic selection * Tarot card selection * Card-drawing animations * Simplified card interpretations * Preview-only results * Optional saving of preview records * Sharing functionality * Calls to action directing users to the Shuyi mobile app The developer must identify which logic should remain on the backend and which animations should be simplified for good web performance. Embedding the existing Flutter Web application is not preferred unless specifically approved. Visual CMS Requirements Non-technical administrators should be able to manage selected marketing and content sections without editing code. Editable areas may include: * Homepage banners and hero sections * Text and image sections * Feature grids * Calls to action * FAQ sections * SEO landing pages * About and brand content * Membership marketing content * App download sections * Announcement bars * Campaign pages * Product recommendation sections * Footer content CMS features should include: * Reusable content blocks * Drag-and-drop or structured block editing * Draft and published states * Preview before publishing * Desktop and mobile preview * Light and dark mode preview * Scheduled publishing * Version history and rollback * SEO metadata * Media library * Page duplication and archiving * Approval workflow where practical Important Boundary The CMS is only for content and presentation. It must not control or modify: * Numerology calculation algorithms * Tarot generation logic * Authentication * Membership entitlement * Energy-point or credit rules * Payment processing * User records * Database operations * Other security-sensitive business logic Admin Dashboard Scope The website admin dashboard should include: * Website performance overview * Page and content management * Drag-and-drop CMS * SEO management * Redirect management * Banner and announcement management * Campaign management * Media library * Tarot and calculation preview configuration * Website-generated preview record lookup * App download link and deep-link management * User support lookup * Analytics and conversion reporting * Website feature flags * Integration health monitoring * Error and webhook monitoring * Admin role and permission management * Audit logs Admin roles may include: * Super Admin * Content Editor * Marketing Admin * Support Admin * Developer Admin * Read-Only Admin All sensitive permissions must be validated by the backend, not only hidden in the frontend. Existing System Boundaries The developer must follow these ownership rules: 1. KCC ID KCC ID is responsible for: * User identity * Login and authentication * Passwords * Email and phone verification * SSO sessions * KCC user IDs The Shuyi website admin must not manage user passwords or authentication credentials. 2. Shuyi App Admin The existing Shuyi App Admin remains responsible for: * Membership tiers and expiry * Membership entitlement * Energy points and credits * Monthly credit allocation * Credit deduction and top-up * Payment entitlement * App-level membership packages The website admin may display this information through APIs for customer-support purposes, but it must remain read-only. 3. PlenorHub PlenorHub remains responsible for: * Marketplace products * SKUs * Prices * Inventory * Sellers * Orders and fulfillment The Shuyi website admin may choose which PlenorHub products are displayed and where they appear, but it must not directly edit the source product data. 4. Shuyi Website Admin The new website admin will manage: * Website content * Page layout * SEO * Banners and campaigns * App download links * Website preview configuration * Website analytics * Product display placement * Support lookup * Website configuration * Integrations and audit logs API Integrations The project may require integration with APIs for: * KCC ID authentication and SSO * User profile * Membership status * Payment and entitlement status * Energy-point balance * Numerology calculations * Tarot Lite results * Preview result storage * Website record history * Deep-link generation * PlenorHub product display * Analytics and conversion events * Admin roles and permissions * Integration health monitoring No sensitive business logic should exist only in the frontend. Design Direction The website should feel: * Premium * Mystical but professional * Clean and modern * Trustworthy * Mobile-first * Consistent with the existing Shuyi mobile app The developer should create reusable components for: * Buttons and forms * Tarot cards * Calculation cards * Result summaries * Membership plans * Dashboard cards * Admin tables * Alerts and notifications * Loading, error, and empty states * App download banners Dark mode must be intentionally designed rather than created through simple color inversion. SEO and Performance Requirements The website should support: * Server-side rendering or static generation where appropriate * Clean, SEO-friendly URLs * Page titles and meta descriptions * Open Graph metadata * Canonical URLs * Sitemap and robots.txt * Schema markup where applicable * Proper heading structure * Image alt text * Image optimization * Core Web Vitals optimization * Fast mobile loading * Migration redirects from old WordPress URLs Analytics The implementation should support: * GA4 * Meta Pixel where required * TikTok Pixel where required * App download tracking * Open-app tracking * Tarot preview starts and completions * Calculation starts and completions * Result views * Membership CTA clicks * Product clicks * Campaign and UTM tracking * Relevant backend events Expected Deliverables * Architecture and implementation proposal * Complete responsive Next.js website * Reusable frontend component system * Light and dark themes * Tarot Lite web experience * Calculation preview flows * Lightweight user dashboard * Visual or block-based CMS * Secure role-based admin dashboard * Existing PHP backend API integration * KCC ID integration * Shuyi App Admin read-only integration * PlenorHub display integration * SEO configuration and URL migration * Analytics and conversion tracking * Testing and bug fixing * Deployment configuration * Source code and repository handover * API and architecture documentation * Admin user guide * Deployment and maintenance documentation Developer Requirements Please apply only if you have strong experience with: * Next.js and React * TypeScript * Tailwind CSS * PHP API integration * Authentication and SSO * Role-based access control * Headless or visual CMS architecture * Admin dashboard development * SEO migration * Responsive UI implementation * Web animation and performance optimization * Secure API-driven architecture * Git-based development workflows Experience with Flutter code review, multilingual websites, membership platforms, tarot or interactive card experiences, and app deep linking would be an advantage. The website should support Chinese content. Please explain your experience handling Chinese or multilingual interfaces. Application Questions Please answer the following questions in your proposal: 1. Please share two or three relevant Next.js projects you personally developed. 2. Have you built a visual, drag-and-drop, or block-based CMS before? Which technology did you use? 3. What CMS and admin architecture would you recommend for this project, and why? 4. How would you integrate a Next.js frontend with an existing PHP backend? 5. Have you implemented SSO and role-based admin permissions before? 6. Have you migrated an existing WordPress website to Next.js while preserving SEO and URLs? 7. How would you rebuild a Flutter tarot experience for the web while maintaining good performance? 8. Would you handle this project personally or through a team? Please identify the people who would work on it. 9. Please provide an estimated development timeline. 10. Please state which items, information, designs, and API documentation you would require from us before starting. Please begin your proposal with the words “SHUYI NEXTJS” so we know you have read the complete job description. We will provide the detailed PRD, current website reference, Flutter app reference, branding materials, and available backend documentation to shortlisted applicants. This is expected to be a milestone-based project. Final milestones will include testing, production deployment, source-code handover, documentation, and resolution of agreed defects.