85 lines
2.4 KiB
Markdown
85 lines
2.4 KiB
Markdown
# Dashboard
|
|
|
|
Workspace reference: [`GSP-WORKSPACE.md`](../../../GSP-WORKSPACE.md)
|
|
|
|
## Purpose
|
|
|
|
Main landing dashboard with widgets and quick server overview.
|
|
|
|
## Current Status
|
|
|
|
- Functional
|
|
- Uses the existing collapsible widget layout for customer-facing quick actions
|
|
|
|
## Dependencies
|
|
|
|
- Panel dashboard widgets
|
|
- user permissions
|
|
|
|
## Database Tables
|
|
|
|
- `widgets`
|
|
- `widgets_users`
|
|
|
|
## Agent Interaction
|
|
|
|
- indirect through monitor widgets and server summaries
|
|
|
|
## User Workflow
|
|
|
|
- view server summary widgets
|
|
- access quick links
|
|
|
|
## Admin Workflow
|
|
|
|
- manage dashboard widgets and layout
|
|
|
|
## Security Concerns
|
|
|
|
- widget visibility should respect permissions
|
|
|
|
## Known Issues
|
|
|
|
- some default widget IDs are legacy and limit how far the collapsible layout can be expanded without a schema change
|
|
|
|
## Missing Functionality
|
|
|
|
- richer status and alert surfaces
|
|
- deeper async server-status embedding without adding remote checks to normal dashboard loads
|
|
|
|
## Suggested Future Improvements
|
|
|
|
- surface lifecycle state, support, billing, and docs more prominently
|
|
|
|
## Recommendation
|
|
|
|
- Keep / Improve
|
|
|
|
## Runlevel Systems Project Request Integration
|
|
|
|
- Dashboard render file: `Panel/modules/dashboard/dashboard.php`
|
|
- Dashboard styles: `Panel/modules/dashboard/dashboard.css`
|
|
- Shared Panel project URL helper: `Panel/includes/functions.php`
|
|
- Shared Discord invite helper: `Panel/includes/functions.php`
|
|
- Shared server-status route helper: `Panel/includes/functions.php`
|
|
|
|
Current project request URL:
|
|
|
|
- `https://runlevelsystems.com/start-project.php`
|
|
|
|
Dashboard behavior:
|
|
|
|
- retained collapsible sections:
|
|
- `Account Overview`
|
|
- `Custom Server Code`
|
|
- `Support`
|
|
- removed duplicate standalone sections:
|
|
- `Custom Server Development`
|
|
- `Support and Troubleshooting`
|
|
- support remains the path for routine troubleshooting, service issues, and existing features
|
|
- the custom-development CTA points users at Runlevel Systems for project work such as custom scripts, mods, integrations, automation, migrations, dashboards, and advanced server tooling
|
|
- the Discord support invite should use:
|
|
- `https://discord.gg/qt9Hnkj6cv`
|
|
- `Custom Server Code` should open the Runlevel project request in a new tab
|
|
- `Support` should keep ticketing and Discord support separate from paid project work
|
|
- `Server Status` stays available from the dashboard, but remote checks are intentionally deferred to the separate status page so normal dashboard loads do not block on agent/network timeouts
|