Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions src/_includes/system-override.njk
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,9 @@
<button onclick="triggerSecretUnlock('matrix')" class="override-btn py-1.5 bg-green-500/5 hover:bg-green-500/20 text-green-500 text-[8px] border border-green-500/20 rounded transition-all">
MATRIX
</button>
<button onclick="triggerSecretUnlock('pulse')" class="override-btn py-1.5 bg-orange-500/5 hover:bg-orange-500/20 text-orange-400 text-[8px] border border-orange-500/20 rounded transition-all">
PULSE
</button>
Comment on lines +20 to +22

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

The PR description states that the orange styling is added to match the pulse easter egg. However, the pulse easter egg color in .xp-pulse is set to #f59e0b (Tailwind's amber-500), while this button uses orange classes (bg-orange-500/5, border-orange-500/20) and its text color is overridden to #fbbf24 (Tailwind's amber-400).

To ensure visual consistency and avoid mixing orange and amber, we should use Tailwind's amber color palette consistently for the PULSE button. Additionally, we can use Tailwind's ! modifier (e.g., !text-amber-500) to override the default #dev-tools button text color directly in the HTML, allowing us to remove the custom CSS overrides in style.css entirely.

        <button onclick="triggerSecretUnlock('pulse')" class="override-btn py-1.5 bg-amber-500/5 hover:bg-amber-500/20 !text-amber-500 text-[8px] border border-amber-500/20 rounded transition-all">
            PULSE
        </button>
References
  1. When suggesting style changes, adhere to the project's existing CSS framework (e.g., Tailwind CSS) and its conventions, rather than introducing separate, traditional CSS files.

<button onclick="triggerForceSurge()"
class="relative overflow-hidden py-2 px-6 bg-blue-600/20 text-blue-300 border-2 border-blue-400 rounded-lg font-bold tracking-[0.2em] transition-all hover:bg-blue-500/40 hover:shadow-[0_0_30px_rgba(59,130,246,0.6)] animate-pulse uppercase">
<span class="relative z-10">Force Surge</span>
Expand Down
8 changes: 7 additions & 1 deletion src/assets/css/style.css
Original file line number Diff line number Diff line change
Expand Up @@ -279,6 +279,12 @@ html body #dev-tools[data-lock="true"] {
#dev-tools button[onclick*="badge_click"] {
color: #bc13fe !important;
}
#dev-tools button[onclick*="pulse"] {
color: #fbbf24 !important;
}
#dev-tools button[onclick*="triggerForceSurge"] {
color: #60a5fa !important;
}
Comment on lines +282 to +287

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

Instead of adding custom CSS rules with !important to override button text colors, we should leverage Tailwind CSS's built-in ! (important) modifier directly in the HTML templates. This keeps the styling utility-first, avoids cluttering the stylesheet, and aligns with the project's Tailwind conventions.

We can remove these rules entirely and apply the colors directly in the template using !text-amber-500 (for the PULSE button) and !text-blue-400 (for the Force Surge button).

References
  1. When suggesting style changes, adhere to the project's existing CSS framework (e.g., Tailwind CSS) and its conventions, rather than introducing separate, traditional CSS files.


/**
* 5. SELF DESTRUCT & REPAIR
Expand Down Expand Up @@ -496,7 +502,7 @@ body[data-level="6"]::after {
/* Added via JS when XP increases */
.xp-pulse {
transform: scale(1.3);
color: white !important;
color: #f59e0b !important;
}
#jump-lvl {
font-family: "Courier New", monospace;
Expand Down
Loading