adding webstorm ide, clearning out defaults and setting up base fonts

[leouofa]

Summary by CodeRabbit

• Chores
  • Added IDE-specific configuration files for project setup.
  • Configured Git version control settings.
  • Set up ESLint inspection profiles.
  • Updated project module configurations.
  • Introduced new font family configurations in Tailwind CSS.
• New Features
  • Simplified structure for the Home component, focusing on text headings.

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
gridbeat	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 29, 2024 8:15pm

[coderabbitai]

Walkthrough

The pull request introduces several configuration files in the .idea directory, which are typically used by IntelliJ IDEA for project-specific settings. These files include .gitignore, gridbeat.iml, inspectionProfiles/Project_Default.xml, modules.xml, and vcs.xml. The changes primarily involve setting up IDE-specific configurations, including version control mappings, module definitions, and ESLint inspection settings, along with modifications to the Tailwind CSS configuration in tailwind.config.ts to include new font families.

Changes

File	Change Summary
.idea/.gitignore	Added ignore rules for /shelf/, workspace.xml, /httpRequests/, /dataSources/, and dataSources.local.xml
.idea/gridbeat.iml	New web module configuration with content URL and excluded folders
.idea/inspectionProfiles/Project_Default.xml	Added ESLint inspection tool with WARNING severity
.idea/modules.xml	New project module configuration referencing gridbeat.iml
.idea/vcs.xml	Added Git version control mapping for the root directory
tailwind.config.ts	Added new font family configurations for sans and mono

Poem

🐰 A rabbit's IDE delight,
Configs dancing left and right,
Gitignore shields, modules align,
ESLint watches with a sign,
Fonts now frolic, bold and bright! 🎉

Tip

CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request. We would love to hear your feedback on Discord.

---

🪧 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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

app/page.tsx (1)

3-6: Keep the headings descriptive and relevant.

Currently, the headings both say "Initial Setup..". Perhaps consider using more descriptive text to help users know what to expect from this page. If “Initial Setup..” is just a placeholder, it’s perfectly fine, but be mindful to replace it as the app grows in functionality.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6822456 and b4a9c04.

⛔ Files ignored due to path filters (5)

• public/file.svg is excluded by !**/*.svg
• public/globe.svg is excluded by !**/*.svg
• public/next.svg is excluded by !**/*.svg
• public/vercel.svg is excluded by !**/*.svg
• public/window.svg is excluded by !**/*.svg

📒 Files selected for processing (2)

• app/page.tsx (1 hunks)
• tailwind.config.ts (1 hunks)

🔇 Additional comments (1)

tailwind.config.ts (1)

15-18: Great addition of custom font families!

This configuration effectively ties your variables to fallback fonts. If you need more extensive language coverage or prefer additional fallback fonts, consider adding them to your sans and mono definitions. Otherwise, this looks good to go.