Roadmap to experimental Project Browser in Drupal Core

Created on 18 October 2022, about 2 years ago
Updated 18 September 2024, 2 months ago

Problem/Motivation

This will serve as the meta issue for adding Project Browser to Drupal Core. At some point this issue will be moved to the Drupal Core queue, but it can stay here for now.

Search (all MVP)

🌠 Starshot Blockers

🅰 Alpha Blockers

🅱 Beta Blockers

🎨 Related to Finalizing the UI

Many of the issues blocking beta really belong to the concept of finalizing the UI. These are UI-related issues which may simply need a decision on, or need some work.

💹 Stable Blockers

🚯 NON-BLOCKING, to be considered after MVP

Done

Beta Blockers:

  • Sanitize project page description HTML (esp. links/images URLs) Closed: won't fix
  • 📌 @todo Add return type when php 7.4 support ends. Needs review
  • 🐛 Do not display Standard profile Closed: cannot reproduce
  • 📌 Error messages should utilize Drupal's messages Needs work
  • 📌 Do not minify Svelte bundles Fixed
  • Beta Blockers, UI:

  • 📌 Move styles out of svelte bundle to traditional Drupal library Fixed and its children
  • 📌 Remove top pager Fixed
  • 🐛 Clearing keyword search with X does not update search results Needs work
  • 🐛 Outline on categories not appearing for check boxes - 508/Accessibility issue Active
  • 🐛 Filter's checkbox labels look broken at smaller viewports Needs review
  • 📌 Change the position of the Browse tab in the local task order Needs review
  • 📌 Improve the readability of module cards in grid view Active
  • 📌 Remove the clear button from the tab order Fixed
  • 📌 Change "Browse" to be the default action tab for "Extend" RTBC
  • 📌 Adjust the chip design to the Drupal Design system Needs work
  • 📌 Reposition the card centric spinner for the Svelte UI for install controllers Needs review
  • Vary number of projects per page Active
  • Improve the readability on individual module pages by limiting the line length Active
  • 📌 Adjust the radio button design to the Drupal Design system Active
  • 🐛 Module categories on Browse tab aren't clickable, don't perform a search RTBC
  • 📌 Improve the categories filter type in context to the rest of the filter component ui Fixed
  • Add a filter type for the release status Postponed: needs info
  • Stable blockers:

  • Ability to clear keyword/search filter with one click Needs work
  • 📌 Update markup classnames Active
  • 🐛 Project list tag has multiple accessibility issues RTBC
  • 📌 Test that we cannot tab to the clear search button Fixed
  • 🐛 Current page not selected in pagination widget Needs review
  • 🐛 Content security policy icon in the filters is not correct Active
  • 🌱 [meta] Improve Project Browser's test coverage Active
  • 📌 Improve help text (hook_help) Needs review
  • 🐛 Security and maintained icons need to communicate correct information Fixed
  • Non-blocking:

  • Convert to GitLab CI Postponed
  • 📌 Project list should be using CSS grid and use gaps instead of margins Fixed
  • Display non compatible modules with current Drupal version Active
  • Relocate Filters Button to the Left of Its Container RTBC
  • 🌱 Plan
    Status

    Active

    Version

    1.0

    Component

    Other

    Created by

    🇺🇸United States tim.plunkett Philadelphia

    Live updates comments and jobs are added and updated live.
    • Needs product manager review

      It is used to alert the product manager core committer(s) that an issue represents a significant new feature, UI change, or change to the "user experience" of Drupal, and their signoff is needed. If an issue significantly affects the usability of Drupal, use Needs usability review instead (see the governance policy draft for more information).

    • Needs frontend framework manager review

      Used to alert the fron-tend framework manager core committer(s) that a front-end focused issue significantly impacts (or has the potential to impact) multiple subsystems or represents a significant change or addition in architecture or public APIs, and their signoff is needed (see the governance policy for more information). If an issue significantly impacts only one subsystem, use Needs subsystem maintainer review instead, and make sure the issue component is set to the correct subsystem.

    • Needs framework manager review

      It is used to alert the framework manager core committer(s) that an issue significantly impacts (or has the potential to impact) multiple subsystems or represents a significant change or addition in architecture or public APIs, and their signoff is needed (see the governance policy draft for more information). If an issue significantly impacts only one subsystem, use Needs subsystem maintainer review instead, and make sure the issue component is set to the correct subsystem.

    • Needs release manager review

      It is used to alert the release manager core committer(s) that an issue significantly affects the overall technical debt or release timeline of Drupal, and their signoff is needed. See the governance policy draft for more information.

    Sign in to follow issues

    Comments & Activities

    Not all content is available!

    It's likely this issue predates Contrib.social: some issue and comment data are missing.

    Production build 0.71.5 2024