jiayuasu opened a new pull request, #2792:
URL: https://github.com/apache/sedona/pull/2792

   ## Did you read the Contributor Guide?
   
   - Yes, I have read the [Contributor 
Rules](https://sedona.apache.org/latest/community/rule/) and [Contributor 
Development Guide](https://sedona.apache.org/latest/community/develop/)
   
   ## Is this PR related to a ticket?
   
   - Yes, and the PR name follows the format `[GH-XXX] my subject`. Closes #2791
   
   ## What changes were proposed in this PR?
   
   Search results on the docs site do not differentiate between SedonaSpark, 
SedonaFlink, and SedonaSnow — pages with the same title (e.g., "Geometry 
Functions") are indistinguishable.
   
   This PR adds a colored platform badge next to each search result title:
   - **SedonaSpark** (orange badge) — for pages under `api/sql/`, `setup/`, 
`tutorial/`, etc.
   - **SedonaFlink** (blue badge) — for pages under `api/flink/`, 
`setup/flink/`, `tutorial/flink/`
   - **SedonaSnow** (teal badge) — for pages under `api/snowflake/`, 
`setup/snowflake/`, `tutorial/snowflake/`
   
   Implementation uses a `MutationObserver` on the Material theme's search 
result list to inject badges based on URL path matching.
   
   **Files changed:**
   - `docs-overrides/assets/javascripts/components/search-tags.js` — new 
component with platform detection and DOM tagging logic
   - `docs-overrides/assets/stylesheets/components/_search-tags.scss` — badge 
styles
   - `docs-overrides/assets/javascripts/main.js` — import and initialize the 
new component
   - `docs-overrides/assets/stylesheets/extra.scss` — import the new stylesheet
   
   ## How was this patch tested?
   
   Tested locally with `mkdocs serve` — searched for functions like 
`ST_Contains` and verified that results display the correct platform badge.
   
   ## Did this PR include necessary documentation updates?
   
   - No, this PR does not affect any public API so no need to change the 
documentation.


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