Move blogs to a separate branch

Blogs typically include multiple images, and over time, these assets can significantly bloat the main branch. To keep it lightweight, we could move all blog content to a separate branch, similar to what we did for historical release docs in `versioned-docs`.

They’ll still appear seamlessly on the site, of course. I’m also fine if we decide to store them directly in the existing `versioned-docs` branch instead of creating a new one.

Start by reviewing the existing versioned-docs branch and how its content is made available on the site. Determine where blog content and image assets are currently stored, then define the branch or storage arrangement and site integration needed for blogs to remain visible while keeping the main branch lightweight.

Written by the indexing model from the issue text.