chihsuan commented on code in PR #351:
URL: https://github.com/apache/ozone-site/pull/351#discussion_r3161588181


##########
docusaurus.config.js:
##########
@@ -344,7 +344,7 @@ const config = {
             ],
           },
           {
-            to: 'download',
+            to: 'downloads',

Review Comment:
   This renaming creates new broken external links for anything that's 
bookmarked or indexed, pointing to the old paths.
   
   `/release-notes/*` renaming will also likely 404 after the rename. Was a 
redirect considered (e.g. via `@docusaurus/plugin-client-redirects`)?
   
   
   



##########
src/pages/release/index.md:
##########
@@ -0,0 +1,6 @@
+---
+title: Release Notes
+sidebar_label: Release Notes
+---
+
+This page contains the release notes for Apache Ozone. Please navigate to the 
specific version to view its release notes.

Review Comment:
   I've noticed that when visiting this page, we aren't able to navigate 
directly to a specific version. Was this an intentional design choice?
   
   Perhaps we should add a version list (for example: - [Apache Ozone 
2.1.0](/release/2.1.0) — 2025-12-31...). Alternatively, linking prominently to 
the /downloads page might be helpful. Since the Downloads table already lists 
each version with its corresponding release notes link, this page wouldn't need 
to repeat that information or require updates with each new release. Just share 
a few thoughts.
   
   <img width="2556" height="1376" alt="Image" 
src="https://github.com/user-attachments/assets/f7dd598e-48e8-4dda-a550-9385ac1658bb";
 />
   
   
   



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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to