Feat/554 poc ssg nextjs

[YulikK]

What type of PR is this? (select all that apply)

• 🍕 Feature
• 🐛 Bug Fix
• 🚧 Breaking Change
• 🧑‍💻 Code Refactor
• 📝 Documentation Update

Description

Migrating to Next.js framework

Transition issues:

• Removing react-router, change navigation hooks
• Importing images now gives an object as a result. Added src field to all image variable
• Removed useSizeWindo hook
• Removed useTitle hook, moving title setting logic to route files
• Removed hooks for data request, I pass data directly from the route file.
• Problem with naming folders by fsd. Renamed pages folder to views folder. Renamed app folder to core folder
• Disable eslint rule for default export
• Removed ScrollRestoration
• Dayjs.isBetween same problem as when switching to remix, import changed a bit
• Deleted all test files

Related Tickets & Documents

• Related Issue POC: Move the Website to Static Site Generation (SSG) using Next.js or Remix #554
• Closes POC: Move the Website to Static Site Generation (SSG) using Next.js or Remix #554
• Related Issue Investigate flaky test problem #114
• Closes Investigate flaky test problem #114
• Closes Remove unused Concurrently dependency #592
• Closes DOM nesting issue #530
• Closes Investigate: Correct srcset and sizes when no optimized images #421

Screenshots, Recordings

Please replace this line with any relevant images for UI changes.

Added/updated tests?

• 👌 Yes
• 🙅‍♂️ No, because they aren't needed
• 🙋‍♂️ No, because I need help

[optional] Are there any post deployment tasks we need to perform?

[optional] What gif best describes this PR or how it makes you feel?

[SpaNb4]

Problems I've noticed so far:

2. bluh
   

[github-actions]

Lighthouse Report:

• Performance: 73 / 100
• Accessibility: 100 / 100
• Best Practices: 100 / 100
• SEO: 100 / 100

View detailed report

[apalchys]

@YulikK @Quiddlee I updated PR with the latest changes from the main and it fixed feature branch deployed. It doesn't work if any conflicts exist