Move a Netflex site to Aurora

A Netflex website is a Laravel app whose content lives in Netflex's API: its pages and their blocks, its structures, its files and its labels. It moves to Aurora as a new Aurora site that reads all of that from the API, with the old project beside it as the reference for every template and component. An AI coding assistant can do most of the work: Aurora comes with a skill that knows the way.

1. Make the new site

You need PHP 8.4, Aurora 1.3.6 or later, and the Netflex project checked out. Make the new site next to it:

Say no when it offers to run the starter's seeders: the homepage comes from Netflex. Then give the new site the old one's API keys, from the Netflex project's .env. The import only reads with them; it never changes anything on the Netflex site.

2. Ask your AI coding assistant

The starter app comes with Aurora's skills for Claude Code, Cursor and the other coding assistants. In the new site, ask:

The aurora-netflex skill takes it from there, step by step, and asks where the website needs a decision of yours:

• Page templates and layouts become Aurora layouts, in the Blade they were.
• Builder components become blocks. Netflex keeps no list of a component's fields, so the skill works them out from its editor buttons and inline areas.
• Pages come across with their tree, their addresses and each block's content, read from the API.
• Structures, such as news, events or staff, become models of the site's own with a screen in the admin and blocks that pick or list them.
• Global content becomes a settings tab, labels the site's translation files, and the page tree's navigation menus.
• Files go into the media library with their alt text, and Netflex's redirects and the addresses that change become redirects.
• Languages: Netflex keeps a page tree for each, without linking a page to its translation. The skill suggests which pages pair up, and once you've confirmed them, they become each page's translations.

Commerce, newsletters, customer logins and Netflex admin extensions have nothing to move into in Aurora: the skill lists what the site uses of them and asks what each should become.

3. Check it in the visual editor

The content comes across with an artisan command of the site's own, which updates what it made the last time instead of adding doubles. Run it as often as you need, open the pages under /admin and compare them with the Netflex site until they look the same.

4. Switch over

Run the import one last time, after the editors' last change in Netflex. Check the old addresses (on Netflex they end with a slash; a changed one gets a redirect), the forms, the menus and the labels in each language, then point the domain at the new site. Keep the Netflex site until nobody needs to compare, then take its keys out of .env.

Without an AI assistant

The steps are the same by hand. The skill, vendor/shipaurora/cms/resources/boost/skills/aurora-netflex/SKILL.md, has the map from each part of Netflex to Aurora, the API calls that read it and where each kind of field keeps its value.