Skip to content

Conversation

tyrelchambers
Copy link

@tyrelchambers tyrelchambers commented Oct 15, 2025

IMPORTANT: Please do not create a Pull Request without creating an issue first.Any change needs to be discussed before proceeding.

Based off #90 and should be merged after it

Closing issues

closes #91

...

Description

Go to /ccip to see the hero (not mobile-friendly)
Screenshot 2025-10-17 at 3 25 17 PM

Changes

  • High level
  • changes that
  • you made
  • ...

@tyrelchambers tyrelchambers self-assigned this Oct 15, 2025
@tyrelchambers tyrelchambers force-pushed the feat/91-layout-hero branch 2 times, most recently from 004c1fe to 2fd0b7f Compare October 17, 2025 18:53
@tyrelchambers tyrelchambers marked this pull request as ready for review October 17, 2025 19:26
Copy link

@Zelig880 Zelig880 left a comment

Choose a reason for hiding this comment

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

Good PR! Code is simple and clean

Comment on lines 58 to 61
font-weight: 600;
font-size: 14px;
text-align: center;
line-height: 16px;

Choose a reason for hiding this comment

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

SHould this not be coming from the blocks? is it very different?

Copy link
Author

Choose a reason for hiding this comment

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

Actually, it's not used. I missed removing these styles when i switched to the Blocks styling

Comment on lines +26 to +34
<a
href={button.link}
class={buttonVariants({
variant: index === 0 ? "primary" : "tertiary",
size: "sm",
})}
>
{button.label}
</a>

Choose a reason for hiding this comment

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

Should not be using a block button?

Copy link
Author

Choose a reason for hiding this comment

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

The way that they look to be used in the UI is as links. Being semantically correct, should we not use anchors with button styling (for navigating) rather than buttons? I think doing would be inconsequential compared to doing it this way. let me know what you think

Choose a reason for hiding this comment

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

What you said is actually correct, but the solution for that is different.

The "button component" as an "asChild" property, that will allow it to use the Child element: https://blocks.chain.link/?path=/docs/blocks-button--docs

So for example if I do

<BlockButton asChild><a></a></BlockButton>

It will not render the Button but just apply the style to the Anchor tag!

(this is a common practice also in shadCn)

Copy link
Author

Choose a reason for hiding this comment

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

Ok! That results in less code too so I will do it that way

Copy link
Author

Choose a reason for hiding this comment

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

There's a bug with the component where it won't render when using asChild because of returning multiple react children. Tried to briefly troubleshoot, but even their example doesn't work

@Zelig880 Zelig880 merged commit 823224d into dev-3.0 Oct 23, 2025
11 of 13 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