Skip to content

Button styling changes - #9

Merged
yasminosten13 merged 3 commits into
mainfrom
feature/development-changes
Mar 6, 2026
Merged

Button styling changes#9
yasminosten13 merged 3 commits into
mainfrom
feature/development-changes

Conversation

@yasminosten13

@yasminosten13 yasminosten13 commented Mar 6, 2026

Copy link
Copy Markdown
Collaborator

Summary by Sourcery

Adjust button styling for outline button hover state and refine read-more button typography.

Enhancements:

  • Ensure outline-style buttons use white text on hover for improved contrast.
  • Set a consistent font weight for read-more buttons to align with design guidelines.

@sourcery-ai

sourcery-ai Bot commented Mar 6, 2026

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

Reviewer's Guide

Adjusts button-related styles by adding a hover color override for a specific outline button variant and normalizing the font weight for "Read more" buttons.

File-Level Changes

Change Details Files
Added a specific hover text color rule for the outline variant of WordPress buttons.
  • Introduced a :root-scoped selector targeting .wp-block-button.is-style-outline--2 .wp-block-button__link:hover.
  • Forces hover text color to the white preset using !important to ensure it overrides existing styles.
wp-content/themes/indigotree-theme-2025/assets/sass/main.css
Tweaked the visual styling of the "Read more" button variant.
  • Set font-weight to 400 for .wp-block-read-more to normalize text weight with surrounding typography.
  • Kept existing background, border, and color overrides intact.
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 :root :where(.wp-block-button.is-style-outline--2 .wp-block-button__link:hover) selector may be more specific than necessary; consider dropping :root if you don't need the extra specificity so that future overrides remain easier to manage.
  • If you're changing the hover color for .is-style-outline--2 buttons, consider adding matching :focus/:focus-visible states for keyboard users so the interaction remains consistent and accessible.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- The new `:root :where(.wp-block-button.is-style-outline--2 .wp-block-button__link:hover)` selector may be more specific than necessary; consider dropping `:root` if you don't need the extra specificity so that future overrides remain easier to manage.
- If you're changing the hover color for `.is-style-outline--2` buttons, consider adding matching `:focus`/`:focus-visible` states for keyboard users so the interaction remains consistent and accessible.

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.

LukeGohegan
LukeGohegan previously approved these changes Mar 6, 2026
@yasminosten13
yasminosten13 merged commit 4451cf7 into main Mar 6, 2026
4 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