Wix Landing Page to Full Stack NextJS Conversion

1. Project Objectives

The objective of this project is to achieve the following:

• Seamlessly migrate the current single landing page of www.isolde.app from Wix to a Next.js.

• Maintain design consistency and functionality.

• Leverage modern toolkits and development best practices for scalability, maintainability, and performance.

• Deliver a robust, maintainable, and flexible landing page integrated with Payload CMS and other provided toolkits.

2. Project Scope

2.1. Migration Requirements

1. Landing Page Content

   • Migrate general structure, content, and functionality of the single landing page at https://www.isolde.app.

   • Recommend optimisations and design updates while ensuring the migrated page structure, animations, responsiveness, and interactivity  are still as relevant as the current Wix page.

2. Development Frameworks and Tools

   • Framework: Next.js 15 (App Router) — Nextjs 15 is not a dead requirement but just a preference.

   • Language: Typescript

   • Styling: Tailwind CSS.

   • Animations: Motion.dev or Framermotion (alternative suggestions or preference by the developer are welcome)

   • CMS: Payload CMS configured with Postgress and Uploadthing.

   • Component Library and Documentation: Storybook.

3. In-house Toolkits & reusable Components suggested and available:

   • TWBlocks.

   • Optional Access: TailwindUI & Pro Access, NextUI & Pro Access, and Flowbite & Pro Access (use at the service provider’s discretion).

4. Environment Context

   • Version Control: The service provider will use our in-house GitHub repository.

   • CI/CD: The project will integrate with our in-house CI/CD pipeline.

   • Code Quality: All code must adhere to linting standards, we recommend using Ultracite for Typescript.

2.2. Deliverables

1. Fully functional, migrated single landing page. (*)

2. Integration with Payload CMS for dynamic content management.

3. Tailwind CSS and motion.dev for styling and animations.

4. Documentation and component previews using Storybook.

5. Deployment-ready code integrated with the in-house GitHub repository and CI/CD pipeline.

6. Comprehensive documentation covering:

   • Installation and deployment instructions.

   • CMS configuration and usage.

   • Component descriptions and usage guidelines (via Storybook).

(*) As Next.js enables export as static site or Single-Page Application (SPA),  we welcome optimisation recommendations to keep the footprint of the site as minimal as possible.

3. Eligibility Criteria

Service providers should preferably demonstrate:

1. Proven expertise in developing Next.js projects.

2. Experience with Tailwind CSS, Payload CMS, and animations.

3. Familiarity with Postgres database configuration and Uploadthing.

4. Experience with GitHub version control and CI/CD pipelines.

5. Knowledge of Storybook for component documentation and previews.

6. Compliance with code quality standards and best practices.

4. Submission Requirements

We recommend service providers to submit a short answer with:

1.  Proposal

   • Approach and methodology for migration.

   • Suggested Project timeline and milestones.

2. Experience and/or Portfolio

   • Examples of previous projects (relevant portfolio).

5.  Suggested Project Timeline

The migration project is expected to be completed within 4 weeks of contract award. Below is an indicative timeline:

1. Week 1: Kickoff meeting, requirement gathering, and initial setup.

2. Week 2: Development and integration.

3. Week 3: Testing, revisions, and component documentation.

4. Week 4: Final delivery, deployment, and handover.