@wojtekbrejnak
Posted
Hello, @xStephx! Let me share some helpful suggestions with you. Here are some key points to keep in mind:
I. HTML Structure: Remember to properly structure your HTML documents using tags like <main>
, <article>
, <section>
, <header>
, <footer>
, and <nav>
. These elements enhance accessibility and maintainability.
II. Heading Order: As @abdellah-abadou mentioned, maintaining the correct order of headings (from <h1>
to <h6>
) is crucial. It ensures semantic clarity and assists screen readers.
III. Avoid Nesting <p>
Inside <li>
: Nesting <p>
tags within <li>
tags can lead to unexpected behavior. It’s unnecessary and can cause issues down the line.
IV. Simplify CSS Selectors: Whenever possible, use element selectors to avoid overcomplicating your code. For instance, if you’re targeting a <th>
element with the class “custom-th,” consider using th {}
directly.
V. Custom Properties (Variables): Use custom properties (CSS variables) wisely. If a variable isn’t needed, like in the case of --font-wght-700: 700
, opt for a direct value, such as font-size: 700
.
VI. Bootstrap Usage: While learning and using Bootstrap is valuable, focus on mastering the basics first. Bootstrap can come into play as you advance in your learning journey.
VII. GitHub Documentation (README.md): Invest time in creating clear and informative README files for your projects. Following the Frontend Mentor blueprint is a great approach. Good documentation makes you a better developer and helps others understand your work.
VIII. Meaningful Commit Titles: When committing changes, provide descriptive titles. Instead of generic titles like “Update style.css,” opt for specifics like “Style nutrition table.” Clear commit messages benefit both you and your future collaborators.
Remember, feedback and networking is essential for our growth. Keep up the excellent work, and I wish you all the best on your coding journey!
Marked as helpful
@xStephx
Posted
@wojtekbrejnak thanks for the feedback! I have read all the points where you have explained them precisely and clearly. I will use these suggestions in future projects. Thanks for taking the time to make these suggestions. if you have anything else to write, feel free to write to me, I'm open to new experiences!