DanielLeens opened a new pull request, #487:
URL: https://github.com/apache/seatunnel-website/pull/487

   ## What changed
   
   - add an English case study on how Tongcheng Travel consolidated four 
data-transfer paths onto Apache SeaTunnel Zeta
   - add the corresponding Chinese localization
   - include two maintainable Mermaid diagrams for the unified submission and 
dual-run migration flows
   - preserve links to the original Meetup recap, full replay, and speaker 
profile
   
   ## Why
   
   The SeaTunnel community has a recent, detailed Tongcheng Travel Meetup case 
covering large-scale legacy task migration, data consistency validation, 
AI-assisted task authoring, connector reliability, adaptive parallelism, and 
observability. Publishing an independently written bilingual technical summary 
makes that public experience discoverable from the official website blog.
   
   ## Attribution and content scope
   
   The article reports publicly presented technical facts in a new structure. 
It does not reproduce the source article's images or extended passages. The 
speaker is credited separately, and the original recap and replay remain linked 
from both language versions.
   
   ## Validation
   
   - `git diff --cached --check`
   - isolated Docusaurus production build for the new article in `en` and 
`zh-CN`
   - verified the original recap, Meetup replay, and referenced GitHub profile 
return HTTP 200
   - independent QA and Maintainer reviews
   
   The repository-wide `npm run typecheck` and full-site `npm run build` were 
also attempted. They remain blocked by existing `main` issues outside this PR: 
an invalid HTML comment in `docusaurus.config.js`, existing documentation image 
resolution under `src/theme/DocCard`, and legacy Chinese blog links. The 
targeted bilingual production build for the files changed by this PR succeeds.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to