Skip to content
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

Merged
merged 4 commits into from
Sep 3, 2020
Merged

Public page layout component #146

merged 4 commits into from
Sep 3, 2020

Conversation

godwinpang
Copy link
Collaborator

Create reusable layout component for all public facing pages (event rsvp+signin, signin, signup, future scheduling forms.)

@godwinpang godwinpang requested a review from a team September 3, 2020 04:08
@netlify
Copy link

netlify bot commented Sep 3, 2020

Deploy preview for hkn-ucsd-portal-dev ready!

Built with commit 6da8ad2

https://deploy-preview-146--hkn-ucsd-portal-dev.netlify.app

Copy link
Collaborator

@thai-truong thai-truong left a 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'
Copy link
Collaborator

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?

Copy link
Collaborator Author

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}
Copy link
Collaborator

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.

Copy link
Collaborator Author

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

Copy link
Collaborator

Choose a reason for hiding this comment

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

Sounds good to me : )

@godwinpang godwinpang merged commit 4d50b6c into dev Sep 3, 2020
@godwinpang godwinpang deleted the public_page_layout branch September 5, 2020 21:45
godwinpang added a commit that referenced this pull request Sep 20, 2020
* 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.
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