[META] Track 11: Dashboard page for post installation and login

Created on 15 July 2024, 3 months ago
Updated 16 August 2024, 2 months ago

Summary

The Dashboard is the first page users see after logging in or completing the installation process. It replaces the default "/user" page, which is the current default after logging in. A key feature of the Dashboard for Starshot could be a "What should you do next?" feature.

Work to be done for official launch (in scope)

  • We have created initial wireframes for a new dashboard. There was prior work done on having dashboards in core, but with Starshot, the ideas have evolved. We should include the latest ideas into the existing proposal.
  • Define and prioritize the key features and capabilities that should be included in the Dashboard, focusing on the needs of our target audience. What value does the dashboard offer to content creators? What value does the dashboard offer to site builders?
  • When people are installing Drupal Starshot, the experience could focus on guiding them through the setup process and helping them finalize the configuration of their site. However, after the installation, when people are mainly creating and managing content, rather than extending their site, the experience should shift to prioritize common marketing and content management tasks.
  • If a user is being added as a content creator to Drupal Starshot, the dashboard is likely the first thing people see after logging in for the first time. It's where people have their ""first impression"" of Drupal. With that in mind, we need to leave them a first great impression. Things that come to mind: welcoming message, guided onboarding, looking intuitive, etc.
  • We should also benchmark the proposed solution against competitors to ensure we have a superior user experience.
  • Conduct rapid feedback sessions with our target users (e.g. marketers and no-code site builders, not developers) to validate the design, gather insights, and make necessary adjustments based on their input.

Out of scope for official launch

Get Dashboards into core

Target milestone

As soon as possible:

  • Finalize the requirements and user research: warm onboarding, welcoming language, intuitive design, marketer-friendly language, marketing/content tasks, etc.
  • Define a dashboard that meets the goals that came out of the user research.
  • Share the result of user testing so that we have confidence that the dashboard will meet the expectations of our target users.

By DrupalCon Barcelona, we'd like to show a working MVP dashboard in the DriesNote demo.

Skills required

  • UX research
  • Design
  • Content marketer
  • Developer

Blockers / dependencies

TBC

Track owners

Christian López Espínola ( penyaskito ) & Matthew Tift ( mtift ) from Lullabot

📌 Task
Status

Active

Component

Track: Dashboard

Created by

🇦🇺Australia pameeela

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @pameeela
  • 🇨🇦Canada mandclu

    I realize it's very early to be adding feature requests, but based on my initial testing of the Events recipe for Starshot, I see that installing Drupal programmatically in a containerized environment (including DDEV locally or using the WASM in-browser install Matt Glaman is working on) often results in a site that has UTC set as the timezone.

    Having the site timezone as UTC is likely to cause a variety of subtle issues, and in published sites this is very rarely done deliberately. In particular, generating "add-to-calendar" links (recently added to the Events recipe) from a site with a UTC timezone can lead to some unexpected behavior.

    I would like to see on this "post install dashboard" a prompt to change the timezone if it currently set to UTC. Perhaps it could be a message they could dismiss, but since real-world experience suggests that sites are rarely set to use UTC by design, we should make it as easy as possible for the site builder to change the timezone to something that will better suit their needs.

  • Assigned to mtift
  • 🇺🇸United States tim.plunkett Philadelphia

    Assigning to track lead.

  • 🇦🇹Austria Grienauer Vienna

    Hi!
    I/my team would like to contribute here a small peace. A block which was not jet considered (I have not spotted here or in other issues around this initiative.
    We discussed that already multiple times over at our project drupical.com and today at the EOWG Board meeting.

    Idea: On the Dashboard, show a list of near (location based) Drupal Events. Source will be https://www.drupal.org/community/events
    Over at Drupical we did some research in issues and also had some meeting with other cms systems (developers and users from other systems) like Wordpress. It would help to let a Starshot user explore the Drupal community and maybe finde some connections at a possible Drupal event around their place.
    If this is something which is interesting, and could be considered, we would like to take that issue on and develop and provide such a "block".
    I am not sure, this is the right issue to discuss it, but also happy, if we can create an own issue for this, if this is well received and gets some thumbs up.

  • 🇺🇸United States froboy Chicago, IL

    The event organizers have been preparing for this moment for years. 😊

    At various points dating back to DrupalCon New Orleans, 2016, folka have proposed a Wordpress-style "Events and News" item in the dashboard. The "Announcements" block is starting to work in that way, but it would be great to have a more fully-functional method for helping folks discover the "stay for the community" aspect we're so proud of.

    Here is what the Wordpress block currently looks like for me:

    The Drupal Community Events listing can output events as JSON , which could be consumed by a Dashboard widget. We're happy to work with the DA team to supplement the existing event data with anything else that would be useful.

  • 🇦🇺Australia pameeela

    @grienauer @froboy I think this probably makes more sense as a child issue, where it can be discussed on its own?

Production build 0.71.5 2024