Hi there, @RReiso!
Well, as you may’ve already seen, thought of two semantic blocks,
aside, and just
floated them respectively, one to the
left and the other to the
right. I don’t know if there’s any kind of special magic to it, but it definitively worked out for my layout
As the beginner that I am myself, I’ve realized a few things in my short Code Journey so far:
Precisely, be intentional about your code, rather than playing around with it. This is, use properties as you start understanding them properly — not fully, but at least properly — rather than just throwing a bunch of them to see which one ‘does the trick’ you’re hoping for. It’s exhausting trying to make something work by playing around with properties rather than sitting back to think which ones will actually work in a given context or onto a expected result before you actually write those properties.
Reading somebody else’s code also helps me a lot to figure it out what the heck is goin’ on. Actually, it was the one thing that made me realize that most of times, a few ‘intentional lines’, so to speak, do more for your design than a bunch of lines. I guess this is what the DRY principle speaks directly about.
Cascade (as in 'Cascade StylesSeets") is sorta big deal.
margin: 0 auto;
will work while
margin: 0 auto;
will not to what centering block elements is concerned. So it’s good to have a brain cell just dedicated to analyze the order in which one is setting up every property.
Have a good proper understanding of inline elements vs. block elements will also help you out of more than one frustrating situation, I believe.
Now, one of my main conclusions was that many results to what CSS is concerned is about thinking of all the proper dimensiones of “every box” you’re layin’ out (may that be that CSS Box Model I’ve read about, perhaps?). Thinking of such dimensions (and deciding among them in either absolute or relative terms) feels like quite a big issue… and actually that is what drives me mostly crazy when facing the design initially. This is, all of my insecurities — most of them, at least — come from thoughts as these ones: “OK, so I see this all awesomely in my 13” Mac Book Air screen, but… how about a 15” Mac Book Pro? How about my mom’s 15” Windows-based personal computer? And what about her small 13” Lenovo Yoga? Will relative measures screw up my design? Should I be using absolute measurements instead? As said, it drives me crazy! Because I’ve somehow understood that relative measurements help you somehow with responsive design… not that you don’t need to do your media queries at some point, but the fact that if you use relative measurements properly… it should be easy to see your work adapted in between different devices.
Finally, it is really useful to to me to think — and even draw upon paper — what I want to see reflected on the canvas rather than just imagining it in my head. Mixing what with the ‘be intentional’ principle, I try not to write any code at all whatsoever till I think I’ve got it all figured it out. I mean, I ain’t sayin’ that I don’t miserably fail sometimes and then I go like: “Dude! This should have worked! Why is it not!!
And that’s pretty much it. I don’t know if any of what I just wrote can help you in any way, but I truly hope it does somehow
The Odin Project, mainly, and all the related resources that they provide the user with. Since I am newbie here, I can paste more than 2 links per post, but I solidly recommend and encourage you to create an account there and read everything they tell you to read; there are some amazing resources in there. Actually, I sorta knew FCC before, but it is their ‘Front-End Essentials’ lesson which drove me back here to get familiar with HTML and CSS. I guess that, soon, it will drive me back here to get to know about JS scripting
Don’t hesitate to let me know if I can be of any further help Sharing and teaching is definitively the best way to learn
Thanks for letting me do so!