A Pinned Dashboard Widget slot with configurable size (expandable to full available width)
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
How to use GitHub
- Please use the 👍 reaction to show that you are interested into the same feature.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Is your feature request related to a problem? Please describe.
I want to support custom workflows starting with the dashboard. The size of the dashboard widgets is limited to 320px by 480px, which is small. Users can also "lose" the site-specific dashboard widgets by removing or moving the widget. This leads to support requests to "get the widget(s) back".
Complex custom code is required to initialize a new account with role-based dashboard widgets (i.e. admin, funder, funding candidate), if configured with the following:
occ config:app:set dashboard layout --value="site_widget_1,site_widget_2,site_widget_n,recommendations,spreed,mail,calendar"
Describe the solution you'd like
Having a slot for pinned dashboard components of any size.
Describe alternatives you've considered
While it's possible to mitigate by using multiple dashboard widgets and/or opening modal dialogs, being able to utilize the full width of the dashboard UI would be a better user experience.
- Multiple Dashboard widgets to split up site-specific dashboard workflow UI
- Buttons/Links that open a Modal Dialog, providing more screen real estate
For role-based dashboard widgets, auth branching logic can be added to each site-specific dashboard widget. If we use multiple dashboard widgets, we could have SiteDashboardWidget1, SiteDashboardWidget2...SiteDashboardWidgetN all have an auth if/else statement to present different views for the different user roles.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the dashboard layout configured through occ config:app:set dashboard layout and how dashboard widgets are placed and sized. Define the pinned slot behavior, configurable sizing, and full-width expansion before identifying the affected dashboard entry points and a way to verify role-based layouts and widget persistence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- design, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100