working changed File Folder Structure Migrate to Next.js 13 #659

[crocmons]

working changed File Folder Structure.. Migrate to Next.js 13 #659

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
informatician	❌ Failed (Inspect)			Jul 2, 2023 7:12am

[github-actions]

Hello crocmons, thanks for rising a Pull request, your contribution is valuable to us. The maintainers will review this Pull Request and provide feedback as soon as possible. Keep the great work up!

[s2sharpit]

LGTM!

[s2sharpit]

LGTM
But the branch has too much and complex conflicts.

[crocmons]

I also see it .. I don't know how can I fix it because my resolve conflict option is disabled..@s2sharpit

[s2sharpit]

The branch seems to have numerous and intricate conflicts that need to be resolved. To address this effectively, let's adopt an incremental approach rather than migrating the entire codebase at once. Instead, we'll create a completely new codebase or project and add parts of the codebase, or the code for each page, one by one as individual steps. This method allows us to better manage conflicts, review changes more efficiently, and ensure a smoother transition. As a first step, Let me create the starting files required for Next.js and tailwindcss on the new branch. As we progress, I kindly request you to create a pull request after completing each step or when a page is fully developed. This way, we can maintain an organized workflow, provide focused feedback, and keep track of the changes more effectively. Let's break it down into manageable parts and create pull requests accordingly. Thank you for your understanding and collaboration!

[crocmons]

Actually, that's a great idea but now the merge conflict is resolved...so we can work on this branch.