28 Nov 20 21:14 - dvicj/Horiseon-Accessibility GitHub Wiki

Update:

So, I messed up the content HTML! Luckily I was able to fix it. Explanation:

I applied all of the changes to the “.content” class, which I think took away the display:inline-block style, so all of the content was running into each other and didn’t look good. I didn’t realize that there was already a “content” class at the top of the css document (probably why you’re supposed to group related classes together) so when I applied the changes, they overrode the original inline-block display of the content because they were written last (glad we learned about the “cascade”!). Like I said, I didn’t notice this at first, so my first thought was that it had something to do with the “float” property, because the text was no longer beside the images. I applied the “float-right” and “float-left” classes to the <h2>s and the <p>s, but this obviously didn’t help anything. I decided to open the original unedited CSS stylesheet to compare, and that’s when I noticed that first .content class. I ended up moving the original .content class down to be with the rest of the content classes and changed the .content class I made to .content div, which would apply all the changes I needed while still keeping the same styling for the .content class as a whole.

I wouldn’t have even noticed this today, but I decided to open the index.html on my browser one last time before I stopped for the day. Good thing I did. I was already in a coding headspace and might have been more confused had I discovered this tomorrow morning.

Okay, now I’m really done for the day.