Skip to content

[UXIT-2951][filecoin.io V3] Migrate Blog Posts + Assets [skip percy]#2160

Merged
barbaraperic merged 3 commits intomainfrom
bp/migrate-blog-posts
Feb 16, 2026
Merged

[UXIT-2951][filecoin.io V3] Migrate Blog Posts + Assets [skip percy]#2160
barbaraperic merged 3 commits intomainfrom
bp/migrate-blog-posts

Conversation

@barbaraperic
Copy link
Copy Markdown
Contributor

📝 Description

This PR:

  • Migrates filecoin.io images (vintage/images) to the filecoin-site content directory.
  • Updates file paths: slugs containing periods (e.g., 0.3.2) will cause 404 errors due to Next.js interpreting them as file extensions. These files are renamed to use dashes instead (e.g., 0-3-2).

@barbaraperic barbaraperic self-assigned this Feb 10, 2026
@notion-workspace
Copy link
Copy Markdown

@vercel
Copy link
Copy Markdown

vercel Bot commented Feb 10, 2026

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

Project Deployment Actions Updated (UTC)
ffdweb-site Ready Ready Preview, Comment Feb 16, 2026 11:57am
filecoin-foundation-site Ready Ready Preview, Comment Feb 16, 2026 11:57am
filecoin-foundation-uxit Ready Ready Preview, Comment Feb 16, 2026 11:57am
filecoin-site Ready Ready Preview, Comment Feb 16, 2026 11:57am

Request Review

Copy link
Copy Markdown
Collaborator

@CharlyMartin CharlyMartin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking good Barbara!

Is the migration complete after we merge this PR?

A few things I noted:

  1. Some Markdown links are absolute. We should make them relative. For example: https://filecoin.io/blog/filecoin-circulating-supply//blog/filecoin-circulating-supply/
  2. Some image sources also point to filecoin.io instead of using a relative path
  3. Images use a mix of formats and should ideally be optimized/standardized to .webp

These are general considerations, I don't think they apply to this PR. Just thinking out loud / flagging :)

@barbaraperic
Copy link
Copy Markdown
Contributor Author

Looking good Barbara!

Is the migration complete after we merge this PR?

A few things I noted:

  1. Some Markdown links are absolute. We should make them relative. For example: https://filecoin.io/blog/filecoin-circulating-supply//blog/filecoin-circulating-supply/
  2. Some image sources also point to filecoin.io instead of using a relative path
  3. Images use a mix of formats and should ideally be optimized/standardized to .webp

These are general considerations, I don't think they apply to this PR. Just thinking out loud / flagging :)

There are a few things left - ticket here

Yea, I figured we should do absolute links in a separate PR(s) - there's a lot 😵‍💫? Plus we have an issue that aliases don't work in our setup...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants