wuchong opened a new pull request, #2232:
URL: https://github.com/apache/fluss/pull/2232

   <!--
   *Thank you very much for contributing to Fluss - we are happy that you want 
to help us improve Fluss. To help the community review your contribution in the 
best possible way, please go through the checklist below, which will get the 
contribution into a shape in which it can be best reviewed.*
   
   ## Contribution Checklist
   
     - Make sure that the pull request corresponds to a [GitHub 
issue](https://github.com/apache/fluss/issues). Exceptions are made for typos 
in JavaDoc or documentation files, which need no issue.
   
     - Name the pull request in the format "[component] Title of the pull 
request", where *[component]* should be replaced by the name of the component 
being changed. Typically, this corresponds to the component label assigned to 
the issue (e.g., [kv], [log], [client], [flink]). Skip *[component]* if you are 
unsure about which is the best component.
   
     - Fill out the template below to describe the changes contributed by the 
pull request. That will give reviewers the context they need to do the review.
   
     - Make sure that the change passes the automated tests, i.e., `mvn clean 
verify` passes.
   
     - Each pull request should address only one issue, not mix up code from 
multiple issues.
   
   
   **(The sections below can be removed for hotfixes or typos)**
   -->
   
   ### Purpose
   
   This PR updates the primary font family of the Apache Fluss website to 
**Inter**. The goal is to improve the readability of technical documentation 
and blogs across all devices (Desktop & Mobile) and to provide a more modern, 
clean visual aesthetic.
   
   **Motivation & Rationale**
   After evaluating several options for technical documentation sites, we chose 
**Inter** for the following reasons:
   
   1. **Superior Legibility:** Inter is specifically designed for computer 
screens. It features a tall x-height, which makes text highly readable at small 
sizes and on mobile displays.
   2. **Neutral & Professional:** As a data infrastructure project, our website 
should look rigorous and clean. Inter offers a "neutral" personality that 
doesn't distract the reader, similar to the design language used by Vercel, 
Tailwind CSS, and VitePress.
   3. **Modern Standard:** It has become a de-facto standard in the open-source 
community for its clarity and extensive character support.
   
   ### Brief change log
   
   <!-- Please describe the changes made in this pull request and explain how 
they address the issue -->
   
   * Updated the global CSS `font-family` stack.
   * Added **Inter** as the primary sans-serif font.
   * Implemented a "System-First" fallback strategy to ensure fast loading and 
native rendering if web fonts fail to load (e.g., falling back to 
`-apple-system`, `Segoe UI`, etc.).
   <!-- What is the purpose of the change -->
   
   <!-- List UT and IT cases to verify this change -->
   
   #### Screenshots (Before vs. After)**
   *(Please attach screenshots here to show the comparison, e.g., a page of 
documentation and the landing page)*
   
   * **Docs Before:** 
   <img width="3840" height="1876" alt="image" 
src="https://github.com/user-attachments/assets/d8f4400a-39f6-40e3-86e2-87089efdef44";
 />
   
   * **Docs After:** 
   <img width="3840" height="1884" alt="image" 
src="https://github.com/user-attachments/assets/766bb3e4-738f-49f5-afde-f4502ac03165";
 />
   
   * **Blog Before:** 
   <img width="3840" height="1880" alt="image" 
src="https://github.com/user-attachments/assets/d081719c-e156-4f1f-98e6-24d37a501eec";
 />
   
   * **Blog After:** 
   <img width="3840" height="1872" alt="image" 
src="https://github.com/user-attachments/assets/bbbcb341-62c0-4a83-8eba-2103ab926b60";
 />
   
   
   ### API and Format
   
   <!-- Does this change affect API or storage format -->
   
   ### Documentation
   
   <!-- Does this change introduce a new feature -->
   


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