Skip to content

Adding gform styling - #2

Merged
yasminosten13 merged 1 commit into
mainfrom
feature/gform-styling-v2
Mar 3, 2026
Merged

Adding gform styling#2
yasminosten13 merged 1 commit into
mainfrom
feature/gform-styling-v2

Conversation

@yasminosten13

@yasminosten13 yasminosten13 commented Mar 3, 2026

Copy link
Copy Markdown
Collaborator

Summary by Sourcery

Align Gravity Forms button styling with the site's primary brand colours.

New Features:

  • Add custom styles for Gravity Forms footer buttons including primary, next, and previous actions.

Enhancements:

  • Define hover states for Gravity Forms footer buttons to match brand styling and improve visual consistency across forms.

@sourcery-ai

sourcery-ai Bot commented Mar 3, 2026

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Adds custom styling for Gravity Forms footer buttons to match theme colors and hover behavior.

State diagram for Gravity Forms footer button styling

stateDiagram-v2
  [*] --> Normal

  Normal: Normal_state
  Normal: background #a9325a
  Normal: text_color #ffffff
  Normal: border 2px_solid_#a9325a
  Normal: border_radius 0

  Normal --> Hover: mouse_over
  Hover --> Normal: mouse_out

  Hover: Hover_state
  Hover: background transparent
  Hover: text_color #a9325a
  Hover: border 2px_solid_#a9325a
  Hover: border_radius 0

  Normal --> [*]: form_unloaded
  Hover --> [*]: form_unloaded
Loading

File-Level Changes

Change Details Files
Style Gravity Forms footer buttons with theme-specific colors and hover state.
  • Define base styles for submit, next, and previous buttons within Gravity Forms footer wrapper, including background color, text color, border, and border-radius
  • Define hover styles for the same buttons, inverting background and text colors while preserving the border color
  • Use !important flags to ensure these styles override default Gravity Forms/button styles
wp-content/themes/indigotree-theme-2025/assets/sass/main.css

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Hey - I've left some high level feedback:

  • The new Gravity Forms button styles rely heavily on !important; consider increasing selector specificity or adjusting the cascade instead so these rules don’t become difficult to override later.
  • These styles apply globally to all .gform_wrapper footers; if the intent is to style only specific forms, consider scoping the selectors to a more specific parent to avoid unintended side effects on other forms.
  • You’ve added hover styles but no explicit focus/active states; consider adding accessible :focus-visible (and possibly :active) styles so keyboard users get a clear focus indication consistent with the new design.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- The new Gravity Forms button styles rely heavily on `!important`; consider increasing selector specificity or adjusting the cascade instead so these rules don’t become difficult to override later.
- These styles apply globally to all `.gform_wrapper` footers; if the intent is to style only specific forms, consider scoping the selectors to a more specific parent to avoid unintended side effects on other forms.
- You’ve added hover styles but no explicit focus/active states; consider adding accessible `:focus-visible` (and possibly `:active`) styles so keyboard users get a clear focus indication consistent with the new design.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@yasminosten13
yasminosten13 merged commit 786baf4 into main Mar 3, 2026
5 checks passed
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