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

   ## Summary
   - remove the footer divider line and keep the copyright block visually 
centered
   - clip homepage horizontal overflow so the architecture pulse no longer 
leaks outside the section bounds
   - keep the replacement PR scope limited to the still-useful homepage fixes 
from the stale `#468` / `#471` pair
   
   ## Why this respin
   - `#468` is now conflicting with `main`, but its footer and overflow fixes 
are still valid
   - `#471` mixed an unrelated homepage commit that already landed in `#472`, 
and its zh-CN `Scenario Recipes` key is not wired by the current 
`seatunnel-website/main` sidebar structure yet
   - this PR keeps only the changes that are actionable on top of current `main`
   
   ## Validation
   - UI runtime check: `npm run start -- --host 127.0.0.1 --port 3052`
     - verified `http://127.0.0.1:3052/`
     - confirmed `document.documentElement.scrollWidth === 
document.documentElement.clientWidth`
     - confirmed `.st-home` uses `overflow-x: clip`
     - confirmed footer `border-top` is gone and `.footer__copyright` remains 
centered
   - Production build attempt: `npm run build`
     - entered the full static build path, but the local validation environment 
emits pre-existing docs asset warnings for legacy `seatunnel-workflow.svg` 
files and a `docsDir` symlink warning
     - these warnings are outside the 3 touched homepage/footer files, so the 
final acceptance for this respin is based on the real homepage runtime 
verification above
   
   ## Reused local validation artifacts
   - reused local `node_modules` via symlink for preview only
   - reused local `docs`, `sidebars.js`, and `static/image_en` as local preview 
helpers only
   - these helper artifacts are not part of the PR scope
   


-- 
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