weiqingy opened a new pull request, #1018:
URL: https://github.com/apache/flink-agents/pull/1018

   Linked issue: #1017
   
   ### Purpose of change
   
   The documentation index splits into two columns through the `columns` 
shortcode. The left "Try Flink Agents" column held a single sentence, while the 
right "Get Help with Flink Agents" column carries the Slack and Community Sync 
sections. The shortcode renders both as flex items, so they stretch to the 
height of the taller one and the closing "developed under the umbrella of 
Apache Flink" paragraph sits below both. The left column ended about 260px 
above that paragraph, leaving a large blank area in the middle of the landing 
page.
   
   This adds two short link lists to the left column, one for the three 
quickstart agents and one for the main development and operations pages. The 
columns now end within about 15px of each other, and the docs root offers real 
navigation instead of a single link. This follows the Apache Flink 
documentation index, which lists its tutorials as a bulleted list with a one 
line description each.
   
   ### Tests
   
   Built the site with Hugo 0.110.0 extended, the version pinned in 
`docs/setup_hugo.sh`, and rendered the index locally.
   
   - No errors or warnings in the build output.
   - All nine new links resolve and return 200.
   - Confirmed against a render of the unmodified page that the blank area is 
gone.
   
   ### API
   
   No public API change. Documentation only.
   
   ### Documentation
   
   - [ ] `doc-needed`
   - [ ] `doc-not-needed`
   - [X] `doc-included`
   
   ### Was this patch authored or co-authored using generative AI tooling?
   
   - [X] Yes
   - [ ] No
   
   Generated-by: Claude Code 2.1.233 (Claude Opus 5)
   


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