Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updated CTA card bg and link styles #22207

Merged
merged 1 commit into from
Feb 17, 2025
Merged

Updated CTA card bg and link styles #22207

merged 1 commit into from
Feb 17, 2025

Conversation

sanne-san
Copy link
Member

Ref https://linear.app/ghost/issue/PLG-355/improve-cta-card-settings-panel

  • Added pink and purple as background colors to the CTA card.
  • Changed CTA card link styles to currentColor instead of accent color – both for the label and the body text.

Ref https://linear.app/ghost/issue/PLG-355/improve-cta-card-settings-panel
- Added pink and purple as background colors to the CTA card.
- Changed CTA card link styles to currentColor instead of accent color – both for the label and the body text.
Copy link
Contributor

coderabbitai bot commented Feb 17, 2025

Walkthrough

The pull request adds new CSS styling options by introducing two background classes, .kg-cta-bg-pink and .kg-cta-bg-purple, with specified colors in RGBA format in one location and hex values in another. It further defines new style rules for link elements, specifically setting .kg-cta-sponsor-label a to use a black color and .kg-cta-text a to inherit the current text color. These changes affect both the call-to-action cards in the frontend and the email templates, expanding the available styling variations for enhanced visual presentation.

Possibly Related PRs


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 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.

@sanne-san sanne-san enabled auto-merge (squash) February 17, 2025 14:52
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (2)
ghost/email-service/lib/email-templates/partials/styles.hbs (1)

944-946: Consider using RGBA colors for consistency.

The background colors are defined in hex format (#FCEEF8, #F2EDFC) while the frontend CSS uses RGBA. Consider using RGBA for consistency or document the reason for using different formats.

.kg-cta-bg-pink {
-    background: #FCEEF8;
+    background: rgba(225, 71, 174, 0.11);
}

.kg-cta-bg-purple {
-    background: #F2EDFC;
+    background: rgba(135, 85, 236, 0.12);
}

Also applies to: 948-950

ghost/core/core/frontend/src/cards/css/cta.css (1)

1-154: Consider adding hover states for sponsor label links.

The CTA button has a hover state, but sponsor label links don't. Consider adding hover styles for consistency.

.kg-cta-sponsor-label a {
    color: rgba(0, 0, 0);
+    transition: opacity 0.2s ease-in-out;
}

+.kg-cta-sponsor-label a:hover {
+    opacity: 0.85;
+}
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between aee0d3c and 3c8bd66.

📒 Files selected for processing (2)
  • ghost/core/core/frontend/src/cards/css/cta.css (3 hunks)
  • ghost/email-service/lib/email-templates/partials/styles.hbs (3 hunks)
🔇 Additional comments (5)
ghost/email-service/lib/email-templates/partials/styles.hbs (2)

966-968: LGTM! Clear and consistent link styling.

The sponsor label link color is appropriately set to solid black, matching the design intent.


1001-1003: LGTM! Proper use of currentColor.

Using currentColor for CTA text links ensures they inherit the text color, improving visibility and maintaining consistency with the text.

ghost/core/core/frontend/src/cards/css/cta.css (3)

37-43: LGTM! Well-structured background color definitions.

The new background colors follow the existing pattern and use consistent alpha values (0.11-0.12) matching other background variations.


60-62: LGTM! Clear sponsor label link styling.

The solid black color for sponsor label links ensures good visibility and readability.


120-122: LGTM! Proper use of currentColor for links.

Using currentColor for CTA text links is a good practice as it:

  1. Maintains consistency with the text color
  2. Adapts to different color schemes automatically
  3. Improves maintainability

@sanne-san sanne-san merged commit 794a8f0 into main Feb 17, 2025
22 checks passed
@sanne-san sanne-san deleted the cta-bg-and-links branch February 17, 2025 14:59
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.

1 participant