Migrate off storyblok

[mattip]

This is the first part of a migration task to remove the integration with storyblock and use astro to render the blocks. I used claude to help me download all the data we currently have in storyblok. The details are in the storyblok-migration-download.md document, and the scripts are part of the PR. The bulk of the data is the 106 team members, and then there are 7 pages, and the header and footer for the site.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
labs	Ready	Preview, Comment	Jun 22, 2026 2:42pm

[mattip]

Status: Finished the page generation part of the astro migration (point 2.5, step 6 in the migration-plan.md). Vercel deployment is failing.

[mattip]

Locally I can view the pages

DOCKER_API_VERSION=1.42 docker run --rm -v "$PWD":/app \
    -w /app/apps/labs node:22-alpine sh -c "npm run build"
DOCKER_API_VERSION=1.42 docker run --rm -v "$PWD":/app \
    -w /app/apps/labs node:22-alpine sh -c "npm run preview -- --host 0.0.0.0"

[mattip]

I visually looked at some blog posts, the team page, the home page. They all seem very close to the current production ones. Anything else to do? More documentation?

[rgommers]

Anything else to do? More documentation?

The "Maintenance Going Forward" in migration-plan.md would be useful to work out indeed.

[mattip]

Is there something in particular you would like to see in the "Maintenance going forward section"?

[rgommers]

Is there something in particular you would like to see in the "Maintenance going forward section"?

It has "TODO: detailed workflow" for sections that would be good to fill in (add a person, add a page, editing header/footer). In addition, linking to the existing "add a blog post" instructions would be useful (I assume those won't change). And then a few pointers about how to add/edit something other than content, say if the page needs to have a visual component to it that doesn't yet exist.

[mattip]

In ad420a4 I updated the documentation and marked the migration-plan.md completed. Should I delete it or leave it as a historical document?

[mattip]

Should I take this out of draft status or is there more to do?

[pavithraes]

Thank you for working on this Matti, thank you also for your patience here. Yes, I think we can take this out of draft. :)

Ralf and I also got a chance to discuss this in our marketing sync yesterday, and the next step is a full review (potentially AI-assisted). We’re leaning towards merging this soon.

First, about the rendered site, I think all the pages visually look good overall. I did a manual screen-reader test for a11y on several pages, and everything looks good there too. I did notice 1-2 missing alt-texts and a link rendering issue, but we can fix that during full review.
Also, looks like since everything was ported over from Storyblok, that includes some artifacts we no longer need (like some project logos, because we no longer have the projects page). We can clean that up during the full review too, but it's also fine to leave it in.

Some thoughts on our specific workflow/implementation, i.e., the YAML-based content (non-blog) authoring with the Storyblok-like blocks for styling. I was going back and forth on this because I wasn’t sure if this will be maintainable/sustainable long term, but I think it works just fine for the intermediate term. We can consider re-working this during the full website redesign, to be more aligned with how Astro-sites are typically themed/styled.

As for migrating over the Quansight.com pages & blogs, we discussed tackling that after merging this PR. And, we most likely don’t need to migrate all the styling over from that site (because it might even clash with the design of the current Labs site), we can try to move over the content alone, and style it using the blocks we have in this PR (or, add minimal new ones as needed). Does this make sense, and sound alright?

Should I delete it or leave it as a historical document?

Re migration-plan.md, I have no strong preferences as we will have a record of it in this PR's commit history.

[mattip]

Does this make sense, and sound alright?

Yup

[mattip]

As for migrating over the Quansight.com pages & blogs, we discussed tackling that after merging this PR.

Is there anything blocking that merge?