🐛💄 Homepage - sizing between components #2766
Open
+16
−3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As per #2765 - the primary issue is that on large screens the
FeatureItemsALL hadlg:min-h-[70vh]set. I played around with a few options to conditionally render the padding, gaps and margins based off of the user input in the/admineditor. However none of these fit the use case for the Feature block.Instead, I have added a boolean
isFullScreento eachfeatureItem, set to true it would enablelg:min-h-[70vh](like for our landing featureItem), set to false it would just render the gaps as normalTest passed by @bettybondoc