Skip to main content

Web Unit Studio / Layout Q & A

Work to have done:

  • Nearly all of the Interneting is Hard tutorial, most recently on Web Typography and Semantic HTML.
  • Push a second preview of your site-in-progress, now with a first pass at layout

Plan for the day:

  1. Schedule update and inquiry
  2. CSS layout example: grid areas
    • And some FAQs on Grid and Flex
  3. Studio: toward a full working draft
    • Set Goals
    • Go forth!
    • Exit note
  4. HW: Post a draft for Tuesday’s workshop

1. Schedule update and inquiry

In light of various positive indicators around COVID rates, I am tentatively planning to travel for Passover, which would require me to teach class remotely on Thursday, April 14th: a studio day during the final consolidation/integration unit, and our third-to-last class overall.

I want to check in: is going online that day going to cause any major problems that you can think of?

Meanwhile, our next class – the web-unit workshop – was originally scheduled to be fully asynchronous, though I was planning to extend online office hours to include our usual class meeting time.

I can hold to that async arrangement if you’ve planned around it, or I can be available to support an in-person workshop if you feel like that would compensate for the new remote day. Can I get a sense of the room?

2. CSS layout example: Grid Areas

In the EXT readings on CSS Grid, from over the weekend, I’d mentioned Grid By Example, but I suspect not many people made it that far. I’d like to play around with one of the CodePens from that site (by web developer Rachel Andrew), as a way of giving you some examples of what Grid offers in terms of layout.

I’ll be in her Grid by Example 11: Defining Grid Areas, which is a CodePen.

FAQ on layout

When to use Grid, and when Flexbox?

Generally speaking, if you only have one dimension (one row, or one column), Flexbox is your friend. To put that another way: use Grid for layout, Flexbox for components. (That link goes to a nice explanation, with examples, of when you'd want to use which.) Some things really are harder with Grid!

And remember that HTML is often about nesting boxes inside boxes: there's no reason you can't have a flexbox inside a gridbox.

Do we have to use Grid or Flexbox?

Not at all! You can lay out your page using real widths and heights, and if you express them as responsive units (em or %), you'll even get scaling effects as the viewport changes size. To get a horizontal centering effect, you can use margin: 0 auto; on any block element with a declared width, or text-align: center; on any inline element, and you should be good to go.

That said, for dynamically adjusting space between elements, and especially for centering things vertically, these new layout tools are definitely your friends.

Can I learn Flexbox in a more bloodthirsty way?

Try Flexbox Zombies, an interactive course that's currently free. In it, you imagine the flex layout as aiming a crossbow at undead monsters: you have to position the targets using CSS rules to survive. It's kind of slow-paced, but that's because it's filled with challenges for you to solve, with the idea being that typing out the rules many times will make them second-nature by the end.

3. Studio: toward a full working draft

Keep working on your projects and/or tutorials, knowing that you have a draft due by Tuesday morning. See if you can get up to baseline! (In general, use the gdoc as your source for the most up-to-date baseline, since it also has clarifying commentary.)

I’m hoping by now you’re starting to get a feel for how to use the browser’s inspector to see what’s being rendered, and how!

And now you know that includes layout like grid and flex containers, too!

Set Goals

What do you need to do to level up on HTML and CSS in the direction of your specific project? As usual, please write down some goals in the shared google doc, set a goal for today: what do you need to do to level up on HTML, CSS, and resource gathering to move toward your specific project?

Also for my sake and yours, please be as specific as possible: e.g. rather than “working on my site,” you might say, “choosing images for photo gallery” or “building grid for layout with top menu and featured image” etc etc.

Not sure where to start?

Already feeling done? Ask yourself:

  • Are you repeating the same CSS rule in multiple places? Instead, see if you can reuse CSS classes in multiple places, extending them where you need to.
  • Does that div need to be there? If it’s not for layout or semantic grouping, it might not be necessary. See that screencast above for an example.
  • Do you have style or presentation directly in the HTML? See if you can extract it out to the stylesheet.
  • Want more relative values for things like color? See css-tricks.com/a-complete-guide-to-custom-properties/.

Go forth! And Don’t forget to document your process

Don't forget to save periodically as you go:
  • as a project file
  • as a screenshot, showing your process
  • as a git commit, saying what you've just achieved

Exit note

Before you leave, just as a way for me to check in, I’d like to hear more about what happened today: Did you decide on your navigation? Block out the html? Make some progress on a stylesheet? Work through a tutorial or two (and which)?

Reply to your note in the google doc.

Homework for next time

  • Work to push a full draft to GitHub by 10:00am Eastern Time on Tuesday: a solid attempt at a complete website, ideally meeting baseline criteria. Rough edges are still welcome.
    • Don’t forget to update your source credits and permissions / license to use them. You can include these right on the website, or link from the website to a file (credits.md, or even README.md) in your repo.
  • If you’re pretty sure by Monday dinnertime that you won’t be ready to turn in a draft, please let me know asap so that I can responsibly rearrange peer-review groups.
    • That said, remember that pretty much any start, however rough, will count here. Even placeholder content with navigation lets us see the parts you’re thinking about, and maybe we can help you move forward from there.

To double-check that your partners will see the files as you intended, please download a .zip from your GitHub.com repository to a second location on your computer. Does your site open in a browser? Does it look right, or did you forget to push the latest changes?