stac-extensions / stac-extensions/stac-extensions.github.io
Reorganize the extensions table
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 26
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
The initial list a visitor sees at the https://stac-extensions.github.io/ page is rather daunting, at 57 extensions all in a variety of states.
Later in the page is a useful listing of the extensions by maturity level, but it's just a list without the descriptive info, meaning you have to cross reference back to the alphabetical listing to learn about what they do.
I think it would be better to have the initial listing be the full tables but grouped by maturity level so that a visitor can digest what's available by the most common and mature extensions first. An alphabetical listing could be added at the end as a simple list.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the current listing on https://stac-extensions.github.io/ and compare the initial alphabetical table with the later maturity-level listing. Reorganize the visitor-facing full tables by maturity level, retain the descriptive information, and add an alphabetical list at the end. Done means visitors can browse mature extensions first without losing the alphabetical overview.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100