add status page

[SkidGod4444]

Summary by CodeRabbit

Release Notes

• New Features

  • Introduced a user-friendly status page with a clear overview of service statuses.
  • Added a responsive layout with a sticky header and footer for improved navigation.
  • Implemented an accordion interface to display detailed service statuses.
  • Included a customizable theme provider for light and dark mode support.

• Documentation

  • Added a comprehensive README file with setup instructions and deployment guidance.

• Configuration

  • Created configuration files for ESLint, PostCSS, Tailwind CSS, and TypeScript to enhance development practices.

• Styling

  • Established a new CSS structure using Tailwind CSS for consistent theming and responsive design.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
plura-api	🔄 Building (Inspect)	Visit Preview	💬 Add feedback	Nov 16, 2024 8:47am
plura-app	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 16, 2024 8:47am
plura-web	🔄 Building (Inspect)	Visit Preview	💬 Add feedback	Nov 16, 2024 8:47am

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request introduces several foundational files for a new Next.js application named "plura-status." Key additions include ESLint and PostCSS configurations, a README.md file, and a .gitignore file. The project structure is enhanced with various React components for UI elements, including headers, footers, cards, and status indicators, using Tailwind CSS for styling. Additionally, TypeScript configurations and utility functions are established for better code management and styling consistency.

Changes

File Path	Change Summary
apps/status/.eslintrc.json	New ESLint configuration extending next/core-web-vitals and next/typescript.
apps/status/.gitignore	New .gitignore file specifying files and directories to ignore in version control.
apps/status/README.md	New README file providing project setup and usage instructions.
apps/status/app/globals.css	New CSS file defining Tailwind CSS variables for theming, including light and dark modes.
apps/status/app/layout.tsx	New root layout component for the application, managing metadata and theme provider.
apps/status/app/page.tsx	New main page component displaying service status with responsive design.
apps/status/components.json	New JSON configuration file for UI framework settings, including Tailwind CSS paths.
apps/status/components/custom/site/footer.tsx	New Footer component with copyright notice.
apps/status/components/custom/site/header.tsx	New Header component with logo and navigation.
apps/status/components/custom/status.card.tsx	New StatusCard component implementing an accordion for service statuses.
apps/status/components/ui/accordion.tsx	New accordion UI component using Radix UI primitives.
apps/status/components/ui/badge.tsx	New Badge component with variant styling using class-variance-authority.
apps/status/components/ui/button.tsx	New Button component with variant and size options.
apps/status/components/ui/card.tsx	New card UI component with structured subcomponents for content.
apps/status/components/ui/chart.tsx	New chart components using Recharts, including configuration and tooltip handling.
apps/status/components/ui/separator.tsx	New Separator component for rendering horizontal/vertical lines.
apps/status/hooks/themes-provider.tsx	New ThemeProvider component for managing theme context.
apps/status/lib/utils.ts	New utility function cn for merging Tailwind CSS class names.
apps/status/next.config.ts	New Next.js configuration file with placeholder comments for customization.
apps/status/package.json	New package.json defining project metadata, scripts, and dependencies.
apps/status/postcss.config.mjs	New PostCSS configuration for integrating Tailwind CSS.
apps/status/tailwind.config.ts	New Tailwind CSS configuration with theming and animation settings.
apps/status/tsconfig.json	New TypeScript configuration specifying compiler options and file inclusions.

Possibly related PRs

• eslint config #15: The main PR introduces a new ESLint configuration file in the apps/status directory, while this retrieved PR also adds an ESLint configuration file in the apps/api directory, both extending from next/core-web-vitals, indicating a shared focus on linting standards for Next.js applications.

Poem

🐇 In the land of code, where rabbits do play,
New files and components brighten the day.
With headers and footers, and styles that gleam,
Plura Status hops in, fulfilling the dream!
From ESLint to charts, all set up just right,
A project in bloom, oh what a delight! 🌼

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.