feat(docs): add Valaxy blog site

[yufeng201]

Description

Add a standalone Valaxy blog site under blog/ for the planned blog.openviking.dev domain. The blog is separated from the VitePress docs site, keeps the OpenViking visual language, supports image-based post cards and post detail covers, and includes a dedicated GitHub Actions workflow for publishing the generated static site to a TOS bucket.

Related Issue

N/A

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactoring (no functional changes)
• Performance improvement
• Test update

Changes Made

• Added blog/ as a standalone Valaxy + valaxy-theme-press site with OpenViking branding, navigation, RSS output, favicon/logo assets, and sample posts.
• Added a custom blog index with image cards, tags, categories, excerpts, and cover support.
• Added a custom post layout with VitePress-style typography, centered content, right-side outline, copy-page action, detail-page cover image, last-updated text, and previous/next post navigation.
• Added .github/workflows/blog-tos.yml to build the blog and upload blog/dist to a TOS bucket using GitHub Actions secrets.
• Added blog/README.md documenting local development, build commands, content authoring, and required deployment secrets.

Testing

• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have tested this on the following platforms:
  • Linux
  • macOS
  • Windows

Validation performed:

• npm ci in blog/
• npm run build in blog/
• Parsed .github/workflows/blog-tos.yml with js-yaml
• Opened the local preview at http://127.0.0.1:4173/ and checked the blog list and post detail routes

Checklist

• My code follows the project's coding style
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• Any dependent changes have been merged and published

Screenshots (if applicable)

Local preview was used to verify:

• Blog list cards with cover images
• Post detail layout with cover image, copy-page action, right-side outline, and previous/next navigation

Additional Notes

The workflow expects a separate blog bucket. Required secrets are:

• BLOG_TOS_BUCKET
• TOS_ACCESS_KEY
• TOS_SECRET_KEY

Optional blog-specific overrides:

• BLOG_TOS_REGION
• BLOG_TOS_ENDPOINT

[github-actions]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🏅 Score: 95

🧪 No relevant tests

🔒 No security concerns identified

✅ No TODO sections

🔀 No multiple PR themes

⚡ No major issues detected

[github-actions]

PR Code Suggestions ✨

No code suggestions found for the PR.