Premium Headless WordPress & Next.js Platform – Advanced Search, Dashboard and Approval Workflows

About the project

PROJECT OVERVIEW We are seeking an exceptional, established digital-product development company to design and build a premium, fully custom headless WordPress platform. This is not a standard WordPress website, Elementor project, theme customization or basic directory. WordPress will serve as the structured CMS and application backend. The complete public frontend and registered-user dashboard must be custom-designed and developed using Next.js, TypeScript and a suitable API architecture. The platform will contain approximately 650 pre-existing organization profiles together with connected services, programs, events, locations, campaigns and editorial content. The client identity, location, final language and exact sector are confidential. Additional materials will only be provided to shortlisted companies after NDA acceptance. CORE FUNCTIONALITY The platform must include: - structured and relational content architecture; - organization, service, event, location and campaign entities; - secure frontend registration and authentication; - email verification and password reset; - custom organization dashboard; - profile creation and editing; - claiming of existing profiles; - ownership-evidence submission; - manual claim approval, rejection and correction requests; - verified-profile status; - multiple users managing one organization; - one user managing multiple organizations where authorized; - role-based permissions; - draft, pending, approved, rejected, returned and published states; - preview before submission; - editorial approval workflow; - reviewer comments and revision history; - advanced API-driven search; - multiple simultaneous filters; - mobile-friendly filtering; - automatically generated detail pages; - related-content displays; - Excel/CSV migration of approximately 650 records; - data normalization and duplicate detection; - technical SEO; - accessibility; - GDPR-conscious implementation; - strong security; - excellent performance and Core Web Vitals; - documented API architecture; - testing, deployment, training and long-term support. DESIGN QUALITY — HIGHEST PRIORITY Visual and interaction design quality is the most important selection criterion. The final product must not resemble: - a WordPress theme; - a directory template; - a marketplace script; - a generic Bootstrap dashboard; - an Elementor kit; - a purchased UI kit with changed colors. All important screens must be designed and approved in Figma before frontend development. The design phase must include: - product discovery; - information architecture; - user journeys; - wireframes; - two genuinely different visual directions; - high-fidelity desktop and mobile designs; - responsive behavior; - interactive prototype; - complete design system; - reusable component library; - navigation, search and filter components; - dashboard components; - forms and validation; - loading, empty, error and success states; - accessible focus and interaction states; - developer handoff; - design QA during implementation. The proposed senior designer must have verifiable experience designing complex digital products, not only marketing websites or e-commerce stores. TECHNICAL EXPECTATIONS The architecture must be production-grade, scalable, maintainable and SEO-compatible. Applicants must be experienced with: - Next.js; - TypeScript; - React; - headless WordPress; - PHP and custom WordPress plugins; - REST API, GraphQL or justified custom API architecture; - relational data modeling; - secure authentication; - role and ownership authorization; - SSR, SSG and ISR; - caching and cache invalidation; - technical SEO; - Core Web Vitals; - automated and manual testing; - Git-based development; - development, staging and production environments; - documented deployment and rollback processes. Business-critical functionality must be separated from presentation and implemented in documented custom plugins or services. No WordPress core modifications, nulled software, undocumented production changes or direct untracked development on the live system will be accepted. REQUIRED COMPANY PROFILE We require a real, established multidisciplinary company or stable internal team. The proposed team must include: - senior product/UI designer; - UX specialist; - senior Next.js/TypeScript developer; - senior WordPress/PHP developer; - API or solution architect; - QA engineer; - project manager; - post-launch support contact. All subcontracting must be disclosed. The actual proposed designer, architect and lead developers must attend the selection interviews. A sales representative alone is not sufficient. MANDATORY PORTFOLIO Portfolio submission is mandatory. Every applicant must provide exactly three directly relevant live projects: 1. One project demonstrating exceptional original UI/UX. 2. One production headless platform using Next.js, React or an equivalent modern framework. 3. One platform with frontend accounts, dashboards, profile ownership, content submission, directory functionality or approval workflows. For each project, provide: - live URL; - launch date; - technology stack; - your company’s exact responsibilities; - team members or roles involved; - your contribution to design, frontend and backend; - performance results where available; - whether you still maintain the project; - a verifiable client reference where permitted. Generic portfolio pages, screenshots without live URLs and unrelated company websites are not sufficient. Applications without three relevant and verifiable projects will not be reviewed. MANDATORY APPLICATION INFORMATION Begin your proposal with this exact sentence: “We have reviewed the complete brief and will provide three verifiable relevant projects.” Then provide: 1. Legal company name. 2. Official company website. 3. Country and year of registration. 4. Number of permanent employees. 5. LinkedIn company page. 6. Named proposed project team. 7. Exactly three relevant projects. 8. Recommended technical architecture. 9. Explanation of profile claiming and ownership security. 10. Explanation of permissions and cross-organization data protection. 11. Explanation of the editorial approval and revision workflow. 12. Search and filtering recommendation. 13. Migration and duplicate-detection approach. 14. Performance and Core Web Vitals strategy. 15. Testing and QA approach. 16. Project phases and timeline. 17. Fixed-price breakdown by phase. 18. Third-party and recurring costs. 19. Warranty and long-term support. 20. Two client references. 21. Confirmation of complete source-code, Git, Figma and documentation handover. AUTOMATIC REJECTION We will reject: - generic or copy-and-paste proposals; - proposals without relevant live examples; - template-based or conventional theme solutions; - one-paragraph bids; - applicants without a named senior designer; - undisclosed one-person or subcontracted teams; - unverifiable portfolio claims; - unrealistically low placeholder bids; - proposals requiring full payment in advance; - refusal to provide source code or Figma files; - inability to provide documentation and long-term support; - applicants who cannot make the actual proposed team available for interviews. SELECTION PROCESS The selection process will include: 1. Written proposal review. 2. Company and portfolio verification. 3. Design interview with the proposed senior designer. 4. Technical interview with the proposed architect and developers. 5. Live walkthrough of a relevant platform. 6. Client-reference checks. 7. Paid discovery or architecture/design assignment for selected finalists. 8. Final scope and milestone agreement. We are not selecting based on the lowest price. We are looking for a highly reliable long-term technology and design partner capable of delivering exceptional visual quality and senior-level engineering. Please review the attached detailed project brief before applying.

Skills required