===== BEGIN SITE BUILDER SUBCOMMITTEE SYNC MEETING!!! =======
Drupal Community Zoom is inviting you to a scheduled Zoom meeting.
Topic: Project Browser SBS Meeting - Detail Page Brainstorm
Time: Aug 2, 2022 04:00 PM Eastern Time (US and Canada)
Join Zoom Meeting:
https://drupalassoc.zoom.us/j/83949754494
Meeting ID: 839 4975 4494
Dial by your location
+1 646 931 3860 US
Find your local number: https://drupalassoc.zoom.us/u/kdtCgIxNy7
Today we'll be discussing the Figma designs for the "detail" page. Right now when you click through a card, you end up on Drupal.org; we'd like to keep you in Project Browser! What information would you like to see in the "detail" page for a module, and what's most useful for newcomers??
Taking notes here.
..1️⃣ People have said a number of things about the quality of the content, which we acknowledge is an issue, but AmyJune's template for body fields helps a lot.
| bsnodgrass (he/him) | For reference, what is the link to the template? |
| bsnodgrass (he/him) | I do like the idea to somehow see more or less information on the detail page. Everyone will want to be able to tailor that for their use at that particular moment. Collapsed/Expanding detail was mentioned as was an outline style navigation. |
| rkoller | https://docs.google.com/document/d/1Ujee_QVa6W96Qv-2e2uBQGyktJVv2j12L01M... |
:two: Do we allow someone to choose v3 vs v4 of the package/module? Could use a dropbutton so the default is the recommended release, and there are additional options.
3️⃣ one of the most challenging pieces we heard from Leslie, is the body field. So what can we do with the data we have today vs. pie in the sky best future?
| chrisfromredfin | @fjgarlin suggesting rendering READMEs; this solves the problem of having "version 7" version "for Drupal 8 & 9" -- rendered markdown? |
| hestenet (he/him) | i.e: maybe a project-browser.md per branch |
| chrisfromredfin | drumm says: But d.o IS a project browser also, so we don't necessarily to diverge them, so would we do the same for d.o? What about 1.0 vs. 2.0 that are both compatible? |
4️⃣ items of possibility: link to issues, report an issue link, link to d.o, maintainers (useful for experienced folks), documentation link, link to source code (drupalcode) --> list others below!
| hestenet (he/him) | Link to the module's slack channel, patreon, etc...(May not be able to do this way since this kind of data is not structured, but could become optional parts of AmyJune's body template.) (edited) |
| chrisfromredfin | need a link to d.o page! |
:five: If we have a list of clickable maintainers, then we can click through the maintainers headshot AND THEN SEE other modules that maintainer is involved with. This has the benefit of showing "wow, had a good experience with this maintainer" or "oh well they maintain a lot of things, they're big in this community"
6️⃣ option of configurable layouts for project browser / detail pages, etc.
| chrisfromredfin | @shaal dovetailed off this to make it user-selectable "see advanced mode" and get more metrics or not |
| fjgarlin | config page could offer the fields available and perhaps checkboxes to show/hide them |
| chrisfromredfin | @hestenet (he/him) mentions the idea that we can make some of the larger fields collapsible, or encourage use of elements that can be collapsed ! This could even work with current body field 🙂 |
| bsnodgrass (he/him) | As I mentioned configuration options for the site project browser is installed on. I didn't mean multiple versions of things (body field), but rather on off for certain project information available for the detail.FWIW, I don't see that in this phase, but maybe for a future version. (edited) |
:seven: divya mentions the idea of an "outline" hovering on one side so you can click through the headings of the body
:eight: scrap related modules, as we don't have that data on d.o now
Participants:
bsnodgrass, rkoller, chrisfromredfin, hestenet, fjgarlin
Comments
Comment #7
leslieg commented