Epic: Migrate from Gatsby to Astro

[WhiteHoodHacker]

Astro has extremely good MDX support and is just well suited for static sites overall. I have already ported over a good chunk of functionality from the current site. Definitely is a much nicer development experience compared to Gatsby.

Migrated Functionality

• Meetings
  • GFM
  • Katex
• Migrate Events to sigpwny.com #201
• Publications
• Profiles
• Markdown pages
• Meeting-Profile relations
• iCalendar generation
• Redirects
• Client-side routing
• Image optimization
• SEO
• Styling
• Popovers
• Readd tooltips #202
• 404 page
• Home page
• Join page
• Migrate existing content
  • Meetings
  • Events
  • Publications
  • Profiles
    • Admins
    • Helpers
    • Alumni
    • Organizations
  • Redirects
• Epic: Add CMS for new site #203

Fixes

• Epic: Implement reactive animations/transitions #4
• Begins work for CTFd frontend built into sigpwny.com #36
• Portrait-oriented images are squashed into landscape in markdown #98
• Implement meetings index pagination or infinite scroll #121
• Switch meetings/publications to new card_image schema #140
• Handle multi-date meetings #161
• PDF.js increases bundle size significantly #176
• iCalendar location regex matches are too loose #181
• Add pronouns field to member profiles #186
• Make week number field optional #187
• Server-side redirects cause 404 errors in client-side navigation #188

Known Issues

• It is not possible to use a custom key for references between two content types (e.g. you cannot specify an author's name on a meeting Minh Duong, you must use Astro's path ID system member/minh-duong)
  • Workaround: adopt Astro's path ID system. Impact: This adds more friction when creating meetings, but could be improved with a custom CMS widget. This also prevents the easy adding of guest speakers, meaning they need to have a profile created in order for the site to build/pass Zod schema.
  • Solved by manually querying profiles and filtering by name.
• It is not possible to co-locate PDFs and other assets with content markdown files.
  • Workaround: store these assets in public. Impact: This adds more friction when creating meetings, but can be improved using CMS custom assets directory upload.
  • Solved by using vite-plugin-static-copy to copy the entire meetings directory (including assets) into dist.
• Plain markdown files (.md) will not apply custom component replacements (e.g. to use optimized image components or custom table elements). Previously, this was solved by forcing Gatsby to treat all .md files as .mdx files, but this does not seem to be configurable within Astro.
  • Workaround: Only use .mdx files. Impact: minimal.