Skip to content

Migrate totalcross.com from Gatsby to Astro - #12

Closed
flsobral wants to merge 16 commits into
sitefrom
feat/astro-site-migration
Closed

Migrate totalcross.com from Gatsby to Astro#12
flsobral wants to merge 16 commits into
sitefrom
feat/astro-site-migration

Conversation

@flsobral

Copy link
Copy Markdown
Member

Summary

  • migrate the public site and blog from Gatsby to a static Astro build
  • preserve legacy routes, brand assets, metadata, RSS, sitemap, and rollback refs
  • replace branch-generated publishing with validated GitHub Pages artifacts
  • add isolated, default-off DEV/Medium article distribution

Why

The legacy Gatsby 2/React 16 toolchain depends on an obsolete native Sharp stack and publishes generated output to master. This migration establishes a supported static build and source-only deployment model while retaining the public URL and visual contracts.

Validation

  • Astro check: 0 errors, 0 warnings, 0 hints
  • production build: 18 native pages, 20 prepared HTML documents
  • route/link check: 14 legacy routes, 0 broken local references
  • content/RSS/sitemap/metadata checks: passed
  • license tests: 7/7; cross-post tests: 6/6
  • workflow and release dry-run checks: passed

This draft PR is used to prove the Pages artifact before promoting the source history to main; it must not be merged into legacy site.

@flsobral

Copy link
Copy Markdown
Member Author

Validation completed successfully and produced Pages artifact 9081190501. The source commit was promoted directly to main per the migration plan; this PR must not be merged into legacy site.

@flsobral flsobral closed this Aug 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant