davidzollo opened a new issue, #10289:
URL: https://github.com/apache/seatunnel/issues/10289

   ### Description
   
   The blog section in 
[seatunnel-website](https://github.com/apache/seatunnel-website/tree/main/blog) 
currently lacks internationalization (i18n) capability. While the documentation 
and other sections of the website support multiple languages (English and 
Chinese), the blog plugin configuration does not have i18n features enabled.
   
   ### Current Situation
   
   - The blog configuration in `docusaurus.config.js` does not include 
i18n-related configurations
   - The `/blog` directory contains English blog posts
   - The `/i18n/zh-CN/docusaurus-plugin-content-blog` directory exists but 
lacks proper i18n support configuration
   
   ### Proposed Solution
   
   Add i18n capability to the blog plugin configuration in 
`docusaurus.config.js`:
   
   ```javascript
   blog: {
     showReadingTime: true,
     editLocalizedFiles: true,  // Add this
     editUrl: ({ locale, versionDocsDirPath, docPath }) => {  // Update this
       if (locale !== "en") {
         return 
`https://github.com/apache/seatunnel-website/edit/main/i18n/${locale}/docusaurus-plugin-content-blog/${docPath}`;
       }
       return 
`https://github.com/apache/seatunnel-website/edit/main/blog/${docPath}`;
     },
   },
   ```
   
   This configuration will:
   1. Enable proper i18n support for blog posts
   2. Allow localized blog content to be managed in the 
`/i18n/{locale}/docusaurus-plugin-content-blog` directory
   3. Provide correct edit URLs for both English and localized blog posts
   
   ### References
   
   - Docusaurus Blog i18n: https://docusaurus.io/docs/blog#i18n
   - Current blog config: 
https://github.com/apache/seatunnel-website/blob/main/docusaurus.config.js
   


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