[META] Drupal CMS work tracks [#3454529]

Collection of Starshot work track meta issues.

#3454525: [META] Track 1: Update Drupal.org for Drupal Starshot Assigned to: hestenet
#3454526: [META] Track 2: Starshot product marketing section Assigned to: pixelite
#3454527: [META] Track 3: Drupal Starshot documentation Assigned to: lenny moskalyk
#3454528: [META] Track 4: Recommend official recipes in the installation process Assigned to: tim.plunkett
#3479360: [META] Track: Create "Contact form" recipe Assigned to: artinruins
#3454546: [META] Track 6: Create "Blog" recipe Assigned to: l_vandamme
#3454547: [META] Track 7: Create "Events" recipe Assigned to: mandclu
#3454549: [META] Track 8: Create "Data privacy / compliance (GDPR, CCPA, cookie consent)" recipe Assigned to: jurgenhaas
#3461524: [META] Track 9: Trial experience for Starshot
#3461527: [META] Track 10: Create 'base' recipe with contrib modules and basic features Assigned to: pameeela
#3461528: [META] Track 11: Dashboard page for post installation and login Assigned to: mtift
#3461529: [META] Track 12: Proposal for Sitewide SEO recipe Assigned to: thejimbirch
#3461530: [META] Track 13: Content publishing workflows Assigned to: mohammed j. razem
#3461532: [META] Track 14: Proposal for advanced search Assigned to: baddysonja
#3461533: [META] Track 15: Proposal for media management Assigned to: tonypaulbarker
#3461535: [META] Track 16: Proposal for accessibility tools Assigned to: the_g_bomb
#3461541: [META] Track 17: Proposal for multilingual content recipe Assigned to: pavlosdan
#3461542: [META] Track 18: Proposal for analytics Assigned to: dharizza
#3461544: [META] Track 19: Proposal for concurrent editing
#3467680: [META] Track 20: AI Assigned to: yautja_cetanu
#3473313: Track: Navigation for admin UI Assigned to: m4olivei
#3473310: Track: Gin admin theme Assigned to: saschaeggi

Meta issues for projects within the larger starshot scope

#3454620: Starshot Automatic Updates Webinar follow-up Assigned to: tedbow

Issue fork drupal_cms-3454529

Show commands

Start within a Git clone of the project using the version control instructions.

Add & fetch this issue fork’s repository

Or, if you do not have SSH keys set up on git.drupalcode.org:

Add & fetch this issue fork’s repository

About issue forks

Comments

Comment #1

14 June 2024 at 00:09

pameeela created an issue. See original summary.

Comment #2

pameeela CreditAttribution: pameeela commented 14 June 2024 at 00:11

Issue summary:

View changes

Comment #3

pameeela CreditAttribution: pameeela commented 14 June 2024 at 00:13

Comment #4

pameeela CreditAttribution: pameeela commented 14 June 2024 at 02:09

Issue summary:

View changes

Comment #5

hestenet

He/Him

Portland, OR 🇺🇸

CreditAttribution: hestenet at Drupal Association commented 25 June 2024 at 17:33

Issue summary:

View changes

Comment #6

mandclu CreditAttribution: mandclu as a volunteer and at Acquia commented 27 June 2024 at 17:41

Should there be a track for accessibility testing? Since Starshot is intended to bring in functionality from contrib modules, accessibility compliance isn't necessarily guaranteed.

Comment #7

kristen pol

she/her

English

Santa Cruz, CA, USA

CreditAttribution: kristen pol at Salsa Digital commented 28 June 2024 at 15:35

Thanks. I had raised the question about accessibility testing/review in a few different places. Although it can’t be guaranteed, maybe there are people who’d still want to focus on this both for the marketing designs and for the user interfaces for each piece (XB, PB, AU, etc). There’s been discussion about usability testing so it seems like a natural fit to have some basic accessibility testing too. Even if things aren’t addressed for the MVP, there can be issues raised for future work.