Wording use across Polaris 1.2.0 site...
- Dominant language
- Java
- Stars
- 2.1k
- Forks
- 522
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 137
Description
### Is your feature request related to a problem? Please describe.
Can I suggest... use less reference to "Iceberg" and use more generic wording, putting the strategic direction down as a catalog for multiple Open Table formats
polaris.apache.org
[Overview](https://polaris.apache.org/releases/1.2.0/)
Powerful, extensible, and feature-packed frontend toolkit. Build and customize with Sass, utilize prebuilt grid system and components, and bring projects to life with powerful JavaScript plugins.
G
### Describe the solution you'd like
_No response_
### Describe alternatives you've considered
_No response_
### Additional context
_No response_
Contributor guide
Research direction
Start by reviewing the linked Polaris 1.2.0 Overview page on polaris.apache.org and identify wording that refers specifically to Iceberg. Done means the site presents Polaris as a catalog for multiple open table formats, but the issue does not name files or provide replacement text.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100