Thomasroest/basic layout component

[ThomasRoest]

• I have read Chapter's contributing guidelines.
• My pull request has a descriptive title (not a vague title like Update README.md).
• My pull request targets the master branch of Chapter.

Adding some structure with a basic layout component, header and footer

[xarielx]

We need to keep a flexible grid that ensures consistency across layouts, containing details about how content reflows on different screens and providing ease of how an app can scale from small to extra-large screens. At this moment, after reviewing the UI that we have designed thus far, the simplicity that they have, which is the vision that we have, to keep simple, it is better to use the Material UI since it constraints styling to their existing guidelines. For example:
Inline-style:


Here is some helpful documentation: Grid

[xarielx]

I just finished my review, based on today's meeting and since our view is to keep the UI/UX as simple as possible, I believe that we should continue using Material UI moving forward since this provides an easy way for us to provide a uniform experience.

[ThomasRoest]

I would rather see some suggestions on improving the code, instead of some vague statements about grids and pointing to docs. You don't need a grid for a simple single column layout. If you do need it later on ( for larger screen sizes) you can add it to the main component for example.

[Sonicrida]

At the very least, we should let @ThomasRoest refactor to use grid if we think it needs to be in right now. I would prefer to have more actionable advice in code reviews vs closing a PR when at least in this case, it's not too much of a change to refactor if it is necessary.

I don't feel like the screenshots that have been posted demonstrate the need for a Grid component at this time.

[xarielx]

If we could include the Material UI layout in this pull request I can merge it. Thank you

[QuincyLarson]

During our Nov 30 meeting, we determined we want to use Materialize UI for the sake of shipping our MVP sooner. This way, we will not have to spend as much time creating custom Flexbox code.