All solutions

Hi there!

1. I created a list of buttons for the implied filtering system. See-- .topic-tags-list, .topic-tag, and .topic-tag-btn. I thought that if tags can be added and subtracted, a list would be preferable here. I also used buttons for in-page filtering, but I suppose anchors could be used if the filtering system is not in-page. I would like to know if this is semantically correct, and if my reasoning is sound?

2. I had added a "line-height: 150%" to the body style, thinking it would apply to all text. This property did not affect the headings or button. I had to go back and include this property in their classes as well. Why is this?

Thank you!!

I notice throughout my solutions that there are very slight differences in typography (such as letter spacing) as well as margin/padding differences. I tried to tinker with these numbers in my code despite the Figma design, but I still struggled to find a solution. I do not want to overuse absolute positioning. I'd prefer to stick with flexbox/grid whenever possible.

If anybody can help me with this or let me know what I'm doing wrong to not achieve pixel perfect, I'd super appreciate it!

I was fumbly with Github and the deployment of my solution. It's clear that I need to work on learning Git, hah. I have a few resources that I plan to delve into, but any suggestions on specific content would be great.

I'm always interested in feedback regarding accessibility best practices-- If you happen to take a look, and you spot a potential issue or something that can be cleaned up, I'd love to hear your insight.

Any other feedback is appreciated. I'm here to learn by doing, and I've got a lot of work to do. Thank you so much!!

Update: I added the lang and dir attributes to the HTML tag. This was to fix the accessibility error caught by the solution report.