You can do raw CSS, or you can use an existing library like Bootstrap which will have common CSS defined ready for you to use (and customise if desired).
Personally, I'd just grab Bootstrap or similar for a quick project. But doing it raw would help you learn how it all fits together.
Whichever you choose, I can guide you through it. Though it might not happen tonight.
One thing to keep in mind: there's a near-infinite number of ways to do the same thing with CSS.
The traditional way of doing this kind of thing (correctly) is with HTML <div>s and then CSS display: table, display: table-row and display: table-cells.
It seems to be the general opinion that tables should not be used for layout in HTML.
Why?
I have never (or rarely to be honest) seen good arguments for this. The usual answers are:
It's good to separate content from layoutBut this is a fallacious argument; Cliche Thinking. I guess it's true...
@jokerdino Note that this is a bit historical. The modern way of doing things is by using a flexbox. That replaces the old display: table and also many uses of floating elements.
One thing you need to know is that, until recently, a lot of layouting was basically hacking around HTML, CSS and JS to get things into the right places.
It's only recently that there's been an effort to improve CSS to allow it to stand on its own - to make it more flexible (pun not intended).
@jokerdino Well, a kludge is always fast. It's just gonna be a pain to maintain later, and might not always work and ... .
@jokerdino Summing up before I run off for a bit: <table> is wrong when used purely for layout. display: table works but it can be a bit verbose and is a bit inflexible. flexbox can be a bit hard to wrap your head around, maybe, but it's really neat once you start using it.
Just sounds more complex than it is cause I'm going into all the history here ... would be easier if I provided actual code examples but I'll do that in a bit.
I normally start out with an idea of what I want to achieve, an idea of what css I want to use, then just experiment (w/ google) for a bit. Unless I've done something similar before. At this point the "something similar" list has grown long enough that experimentation is kinda rare.
Uhm... I have this problem with leaving when I should. See also: I'm apparently nocturnal now.
It seems to be the general opinion that tables should not be used for layout in HTML.
Why?
I have never (or rarely to be honest) seen good arguments for this. The usual answers are:
It's good to separate content from layoutBut this is a fallacious argument; Cliche Thinking. I guess it's true...
