-
Notifications
You must be signed in to change notification settings - Fork 6
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
Public page layout component #146
Conversation
Not even going to think about touching SignUpPage
Deploy preview for hkn-ucsd-portal-dev ready! Built with commit 6da8ad2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm. Just had a question out of curiosity.
<Grid | ||
className={classes.root} | ||
container | ||
direction='row' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just curious as to why you picked direction row here. Is it so that the whole screen is utilized, at least horizontally, if there are multiple children? Or does it just make sense from a design standpoint?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
great question
idk
it looks fine and will be encapsulated anyways :)
alignItems='center' | ||
> | ||
<Grid item className={classes.children}> | ||
{children} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, is this grid item going to hold all of children, even when children can have multiple components? I thought grid item is usually used for only one component.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it'll just be one thing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good to me : )
* Make document body fill viewport. * Add PublicPageLayout component with story. * Update pages to use public page layout. Not even going to think about touching SignUpPage * Add spacing so content is not squished on mobile.
Create reusable layout component for all public facing pages (event rsvp+signin, signin, signup, future scheduling forms.)