<aside> 💡 Feel free to use this example doc as a starting point for planning and documenting your next migration.
Your Mileage May Vary: A migration document is only useful if it works for you. So feel free to adapt this template to the needs of your project and your team. Larger projects might require more detail, while smaller ones could use a leaner structure.
*Read more about how to use this template:
</aside>
Use this section to briefly describe what this doc is about, the intended audience, and any other information you’d like to be immediately accessible to readers.
Link to any relevant documents as well to give more context about the project, including:
We’ll be working on migrating the frontend layer of Airline.com from its current React + Webpack implementation to Next.js. This migration aims to modernize our tech stack and improve overall performance and developer productivity.
| Date Started | 09/01/2024 |
|---|---|
| Date Last Updated | 09/22/2024 |
| Status | In Review |
| Project Lead(s) | Steve Aoki, Rick Astley |
| … | … |
Explain at a high-level what is the problem that you’re trying to solve with the migration. This includes the outcome you’re hoping to achieve as well as any metrics you’ll use to measure success.
The two primary goals of this migration are to:
By adopting Next.js, we’ll enable developers to implement features end-to-end in a single language and within a single repository. This will allow them to work across the stack with much less friction.
Additionally, the advanced caching and rendering features of Next.js will allow us to improve our application’s loading performance, particularly on mobile devices.