🧠 Widget catalog replacement brainstorm

Open
#11,986 5 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
dart, flutter
Domain
documentation

Research direction

Start by reviewing the current widget catalog and the role previously served by the Flutter Gallery. Compare proposals against the stated requirements: discoverability, filtering, API documentation reuse, stable-channel updates, and widget examples or visualizations. Done means a concrete, agreed direction rather than an implementation patch.

Written by the indexing model from the issue text.

Description

act.question p2-medium t.widgets

Now that the Flutter Gallery is no longer maintained, the widget catalog is the only way to quickly browse Flutter's core widgets to get a rough idea of what is available and what each looks like.

However, the current widget catalog is out of date, isn't easy to maintain, isn't super visually interesting or interactive, and isn't easy to dive in to.

We need a low-maintainence solution that:

  • Helps Flutter developers discover widgets relevant to their needs.
  • Doesn't include non-key/otherwise distracting widgets or allows hiding them.
  • Doesn't duplicate content from API docs, use from there if needed.
  • (Mostly) Automatically updated, at least for the stable channel.
  • (Preferably) Allows developers to view an example of the widget or a visualization of it.

Please respond with any thoughts or proposals, both big or small. Web-based, Flutter-based, or mixed options are all possibilities.

Dominant language
Dart
Stars
3.1k
Forks
3.5k
Avg merge
1d 11h
Merged PRs (30d)
76

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from flutter/website

All issues in flutter/website

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.