feat: add enterprise plan section to api pricing page#1757
Conversation
Deploying beaconchain with
|
| Latest commit: |
3b2e710
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://d05460dd.beaconchain.pages.dev |
| Branch Preview URL: | https://fe-106-api-enterprise-plan-s.beaconchain.pages.dev |
7cd5606 to
975abb2
Compare
api enterprise plan section to api pricing pageenterprise plan section to api pricing page
975abb2 to
00893c1
Compare
00893c1 to
3b2e710
Compare
| borderRadius?: '4xl' | 'xl', | ||
| elevation?: '1' | '2', | ||
| gap?: '5xl' | 'xl', |
There was a problem hiding this comment.
issue: these are too many moving pieces
we should either speak with the design team, if there could be fewer options or we should assume that only the elevation level change this is provided as prop then.
Otherwise having styling options as props on a BaseCard is kinda pointless and we rather slap on classes.
In the end for example we want to have 2 or 3 different versions of a BaseCard.
<BaseCard
elevation="1 | 2 | 3"
...
There was a problem hiding this comment.
Agreed. The thing is, higher elevation also means a card is contained by another card of lower elevation, so it is of a smaller grouping scale and its spacing will likely be smaller too.
We can either only use elevation as a prop like you said, and set gaps with fall-through classes, or let elevation affect both bg color and gap - but I'm not sure that will work.
See: BEDS-106