Huy Phan• 1,840
@huyphan2210
Posted
Hi, @sofiasmnk
I checked out your solution, and I have some thoughts:
- Regarding your Git issue, there are many Git GUI tools available that you can explore to find the one that suits you best. Personally, I use GitHub Desktop. However, if possible, I recommend sticking with the Git command line interface (CLI). Using the CLI can deepen your understanding of Git’s functionality, as it provides more control over commands and operations. Additionally, it can be more efficient for performing complex tasks and troubleshooting issues, making it a valuable skill in the long run.
- Technically, the
<html>element represents the entire web page, which includes both the content visible within the viewport (the area of the browser window where the page is displayed) and the content outside the viewport that can only be seen by scrolling. While some parts of the HTML, like thebody, will always have sections in the viewport, not all of it is visible at once (for example, thehead, which contains metadata and is not displayed on the page). - I came across a course on HTML & CSS where the instructor explained that HTML elements are like boxes that can be nested inside one another. This analogy is helpful for visualizing the structure of web elements, as each element acts as a container for content or other elements. This concept is foundational in both HTML and CSS. Given this understanding, it’s completely normal to find it challenging to make CSS decisions when working on a single component in isolation. However, CSS can actually guide you in this process. I recommend researching CSS further to improve your decision-making skills.
- It's generally better to choose a semantic element when possible. This enhances accessibility and helps search engines understand the content better. Use generic elements only if the card is more of a visual component without significant meaning on its own.
Hope this helps!
0
