Skip to content

Conversation

@carlosabadia
Copy link
Collaborator

No description provided.

@linear
Copy link

linear bot commented Jan 14, 2026

@greptile-apps
Copy link
Contributor

greptile-apps bot commented Jan 14, 2026

Greptile Summary

Added a new consulting use case landing page at /use-cases/consulting with dedicated sections for hero, social proof, features, stats, FAQ, and CTA. The page follows the same structure as existing finance and healthcare use case pages.

Key changes:

  • Created consulting page with 10 view components (hero, social proof, 4 text sections, 2 feature sections, stats, FAQ, final section)
  • Added 7 consulting firm logos (Blue Yonder, Deloitte, DNV, EY, LTIMindtree, PwC, TCS)
  • Updated navbar to link "Consulting" menu item to new dedicated page
  • Enhanced common feature_card component to support optional bullet lists and custom styling
  • Registered new route in pages __init__.py

Issues found:

  • text_section_2.py was created but never imported or used in the page layout, likely left over from copying the template from finance/healthcare pages

Confidence Score: 4/5

  • This PR is safe to merge with one minor issue that should be addressed
  • The implementation follows established patterns from finance and healthcare pages, reuses common components appropriately, and adds straightforward content. The only issue is the unused text_section_2.py file which creates dead code but doesn't break functionality
  • Pay attention to pcweb/pages/use_cases/consulting/__init__.py to decide whether to import and use text_section_2 or remove the file entirely

Important Files Changed

Filename Overview
pcweb/pages/use_cases/consulting/init.py Main consulting page component; missing import for text_section_2
pcweb/pages/use_cases/consulting/views/text_section_2.py Unused text section component; never imported or rendered
pcweb/pages/init.py Added consulting_use_case_page import to routes
pcweb/components/docpage/navbar/navbar.py Updated consulting navigation link to point to dedicated page
pcweb/pages/use_cases/common/features_2.py Extended feature_card to support optional items list and custom class_name

Sequence Diagram

sequenceDiagram
    participant User
    participant Browser
    participant MainPage
    participant ConsultingPage
    participant ViewComponents
    participant CommonComponents

    User->>Browser: Navigate to /use-cases/consulting
    Browser->>MainPage: Request page route
    MainPage->>ConsultingPage: Call consulting_use_case_page()
    ConsultingPage->>ViewComponents: Render hero()
    ViewComponents->>CommonComponents: Use left_content() & right_content()
    CommonComponents-->>ViewComponents: Return hero components
    ViewComponents-->>ConsultingPage: Return hero section
    ConsultingPage->>ViewComponents: Render social_proof()
    ViewComponents->>CommonComponents: Use logos_carousel()
    CommonComponents-->>ViewComponents: Return logo components
    ViewComponents-->>ConsultingPage: Return social proof section
    ConsultingPage->>ViewComponents: Render text sections (1, 3, 4)
    ViewComponents->>CommonComponents: Use text_section()
    CommonComponents-->>ViewComponents: Return text components
    ViewComponents-->>ConsultingPage: Return text sections
    ConsultingPage->>ViewComponents: Render features (1, 2)
    ViewComponents->>CommonComponents: Use feature_card()
    CommonComponents-->>ViewComponents: Return feature cards
    ViewComponents-->>ConsultingPage: Return feature sections
    ConsultingPage->>ViewComponents: Render stats()
    ViewComponents->>CommonComponents: Use stat_card()
    CommonComponents-->>ViewComponents: Return stat cards
    ViewComponents-->>ConsultingPage: Return stats section
    ConsultingPage->>ViewComponents: Render faq()
    ViewComponents->>CommonComponents: Use faq_section()
    CommonComponents-->>ViewComponents: Return FAQ component
    ViewComponents-->>ConsultingPage: Return FAQ section
    ConsultingPage->>ViewComponents: Render final_section()
    ViewComponents->>CommonComponents: Use left_content() & right_content()
    CommonComponents-->>ViewComponents: Return final components
    ViewComponents-->>ConsultingPage: Return final section
    ConsultingPage-->>MainPage: Return complete page
    MainPage-->>Browser: Render consulting page
    Browser-->>User: Display consulting use case page
Loading

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

15 files reviewed, 1 comment

Edit Code Review Agent Settings | Greptile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants