The Publishing Pipeline
An introduction to a verifiable bilingual publishing workflow.
TCV Threat Intelligence Team
On this page
Why publishing stability comes first
content requires more than sound analysis. Its sources, disclosure scope, links, and image availability also need consistent controls. The TCV blog uses repository-managed MDX documents and static assets as its single source of truth.
Publishing flow
- Authors prepare Korean and English documents at the same relative path.
- Automated checks validate frontmatter, translation pairs, images, and links.
- The build prerenders every public route as static HTML.
- Reviewers inspect content and presentation in a Merge Request preview.
This workflow does not automatically deploy executable threat data. It is an editorial and validation process for publishing approved public documents consistently.
Related articles
- [Test] Korean and English navigation
A temporary article for checking translated posts and localized page navigation.
- [Test] Category list navigation
A temporary article for checking category links and the article list.
- [Test] Article list pagination
A temporary article for checking page navigation and newest-first ordering in the blog list.