Fix(frontend)/remove unwanted elements

[alcercu]

Summary by CodeRabbit

• Refactor
  • Streamlined page layouts across builders, lawyers, and home views by removing non-essential sections and interactive elements.
  • Reordered content and updated component interfaces to offer a simpler, more focused user experience.
• Style
  • Adjusted spacing, padding, and background themes for improved visual clarity and consistency.
• Chore
  • Standardized internal resource references and module paths for cleaner organization.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request revises several React components and query definitions by removing unused components and fields, updating import paths, and adjusting class names and spacing for styling consistency. Notable changes include removing the IntegrateSection, TokenStats, and KlerosEscrowSection components, modifying GraphQL queries to eliminate token statistics, and introducing an optional listMode prop to conditionally adjust the layout in some components.

Changes

Files	Change Summary
frontend/src/app/for-builders/page.tsx, .../home/components/Hero.tsx, .../home/components/TokenStats.tsx, .../for-lawyers/components/KlerosDisputeResolutionSection/index.tsx	Removed unused components and their JSX usage: the IntegrateSection, TokenStats (and its file deletion), and KlerosEscrowSection.
.../for-lawyers/components/Hero.tsx, .../home/components/CaseStudies.tsx, .../home/components/LearnPosts.tsx, .../home/components/UseCases.tsx	Adjusted layout and styling by updating padding values and changing background class names.
.../for-lawyers/components/KlerosMediationSection/index.tsx, .../components/Flowchart.tsx, .../components/KlerosEscrowSection.tsx, .../queries/kleros-escrow-section.ts	Updated import paths from relative to absolute and rearranged import orders.
.../components/IntegrateSection/index.tsx, .../components/Navbar/AppsDropdownContent/index.tsx, .../home/page.tsx	Modified component interfaces to add an optional listMode prop, updating component signatures and conditional rendering logic accordingly.
.../home/queries/hero.tsx	Removed the tokenStats field from the GraphQL query and its corresponding type definition.

Sequence Diagram(s)

sequenceDiagram
    participant Parent as Parent Component
    participant ADC as AppsDropdownContent
    Parent->>ADC: Render with optional listMode prop
    alt listMode is true
        ADC-->>Parent: Renders without grid layout classes
    else listMode is false
        ADC-->>Parent: Renders with grid layout classes
    end

Loading

Possibly related PRs

• feat: for builders page #23: Introduced a new IntegrateSection component for the builders page, establishing a direct connection with its removal in this PR.
• Feat(frontend): home page #60: Modified the usage and import of IntegrateSection, aligning closely with the changes made in this pull request.
• fix(cms): token-stat-type #72: Removed the tokenStats field from the GraphQL schema, which corresponds to the query and type modifications here.

Suggested reviewers

• Harman-singh-waraich

Poem

I'm a nimble rabbit, hopping through the code,
Trimming extra branches off this pixelated road.
With clean paths and spacing perfectly tight,
I celebrate changes that make the UI light.
Hop along with me, enjoy the refactor delight!
🐰💻 Hop, hop—code’s never been so bright!

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between c107b2e and 68bcee2.

📒 Files selected for processing (16)

• frontend/src/app/for-builders/page.tsx (0 hunks)
• frontend/src/app/for-lawyers/components/Hero.tsx (1 hunks)
• frontend/src/app/for-lawyers/components/KlerosDisputeResolutionSection/index.tsx (0 hunks)
• frontend/src/app/for-lawyers/components/KlerosMediationSection/index.tsx (1 hunks)
• frontend/src/app/home/components/CaseStudies.tsx (1 hunks)
• frontend/src/app/home/components/Hero.tsx (1 hunks)
• frontend/src/app/home/components/LearnPosts.tsx (1 hunks)
• frontend/src/app/home/components/TokenStats.tsx (0 hunks)
• frontend/src/app/home/components/UseCases.tsx (1 hunks)
• frontend/src/app/home/page.tsx (1 hunks)
• frontend/src/app/home/queries/hero.tsx (0 hunks)
• frontend/src/components/Flowchart.tsx (1 hunks)
• frontend/src/components/IntegrateSection/index.tsx (2 hunks)
• frontend/src/components/KlerosEscrowSection.tsx (1 hunks)
• frontend/src/components/Navbar/AppsDropdownContent/index.tsx (1 hunks)
• frontend/src/queries/kleros-escrow-section.ts (1 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

---

🪧 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.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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 or @coderabbitai title 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.