└ Learning SiteGitHub ↗

Legacy migration

Move forward without losing your work.

Migration is designed around one non-negotiable: your content stays yours. A Git recovery point is created before the project is updated.

1

Install Learning Site Editor

Download the current Windows installer and complete the installation.

2

Connect existing repository

Select the local legacy repository or clone it from its remote. Do not copy content into a new project.

3

Legacy project detection

The editor inspects the repository and identifies the legacy Learning Site structure before any upgrade is applied.

4

Safe upgrade

Confirm the upgrade. Your user content is preserved, and the editor creates a Git recovery point before migration so the earlier state remains recoverable.

5

Preview

Open the local preview and check pages, links, media, theme appearance, and language direction.

6

Publish

When the preview is right, commit and push. Your normal GitHub Pages or Cloudflare Pages deployment can publish the upgraded static output.

Keep the recovery point.

Do not delete the migration commit or its history. It is your straightforward route back if you need to compare or restore the legacy state.

Download the editor