Re-evaluate template-derived feature gaps before implementation
@cixzhang is already working on this.
Since Aug 28, 2026.
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 1.1k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 669
Description
## Why this needs an owner decision
Several feature gaps were filed from template grading evidence and then turned into large component or API implementations before maintainers rechecked whether the capabilities still belong in the current system:
- #2625 — whole-shell width and centering for `Layout`
- #4094 — a first-party `Image` component with loading, fallback, and preview behavior
The template workarounds are useful evidence, but template score alone does not approve a new public API or component.
## Decision needed
For each capability, decide whether it is still necessary in the current product and component direction, and if so, settle its ownership and public shape before implementation resumes.
Until that decision is made, this issue is not ready for contributor implementation. The original issues are consolidated here so contributors are not asked to maintain speculative branches.
Contributor guide
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.
Assessment
This issue has not been assessed yet.