dxlander/dxlander

AI Summary: This issue proposes enhancing the `/health` endpoint to include checks for database connectivity and critical service status. The goal is to provide more comprehensive health information for monitoring and debugging purposes, returning a 200 status for healthy services and 503 for unavailable ones.

AI Summary: This feature request proposes adding `maxLength` attributes to various input components across the application. The goal is to prevent users from entering excessively long values, which could lead to database errors, poor user experience, and other technical issues. The proposed solution includes specific `maxLength` values for different input types like project names, URLs, emails, descriptions, and tokens.

AI Summary: This issue proposes refactoring existing inline date formatting logic into a reusable utility function within a shared package. The goal is to ensure consistent date formatting across the project by extracting a provided `formatDate` function.

AI Summary: This issue proposes replacing the current basic spinner on the homepage with a skeleton loading pattern. This will improve user experience by visually representing the dashboard's structure while content is loading, leading to better perceived performance and a more modern feel. The necessary skeleton component is already available.

AI Summary: This issue proposes adding a custom 404 'Not Found' page to the web application. The goal is to replace the default Next.js 404 page with a branded experience that aligns with the Ocean Design System, including 'Go Home' and 'Go Back' buttons.

AI Summary: This issue proposes to replace the default Next.js favicon and implement comprehensive metadata, Open Graph images, PWA manifest, and SEO assets using the existing DXLander logo. The goal is to improve project branding and search engine optimization by leveraging existing logo assets and following Next.js 15 App Router conventions.

AI Summary: This issue proposes adding a UI feature to allow users to delete projects. It involves wiring up an existing menu item, implementing a confirmation dialog with project name input, and enhancing the backend to clean up associated local files, configurations, deployments, and database records. The goal is to enable users to remove unwanted projects and free up storage.