Submitted over 2 years ago

Mobile responsive solution using css flexbox

@Osaode

A solution to the Agency landing page challenge

Solution retrospective

Please recommend CSS frameworks that can help me write CSS easily and can compress it so it's not so bulky. My CSS was so difficult to write and it's too bulky.

Code

Please log in to post a comment

Community feedback

K. Karr•90
@kkarrwrites
Posted over 2 years ago
Hi Osaode! I'm K. I want to preface my comment by saying that while I've been studying HTML, CSS, and JavaScript for a while now, I'm still a student. Nevertheless, I wanted to take a stab at your question regarding bulky CSS and CSS frameworks.

When I first started coding CSS, I was immediately overwhelmed by the bulk of it. I asked myself, how can a web developer follow the DRY ("Don't repeat yourself") principle of development in CSS? It seems very difficult! One of the solutions I've found is to research and implement different methods of writing CSS.

Two methods I've found helpful are BEM (https://getbem.com/introduction/) and OOCSS (https://www.hongkiat.com/blog/basics-of-object-oriented-css). I've also started learning and implementing Sass, which is a great way to organize your CSS into more manageable parts.

Regarding frameworks, I would recommend Bootstrap, although my knowledge of it is limited; however, I do think it is good to practice writing CSS and/or SCSS before working with a framework.

Well, I hope this helps!
Marked as helpful
Adriano•42,870
@AdrianoEscarabote
Posted over 2 years ago
Hi Osaode Eghianruwa, how are you?

I really liked the result of your project, but I have some tips that I think you will like:

1- Every page should have one main landmark <main>. So replace the div that wraps the whole content with <main> to improve the accessibility. click here

2- All page content should be contained by landmarks, you can understand better by clicking here: click here

We have to make sure that all content is contained in a reference region, designated with HTML5 reference elements or ARIA reference regions.

Example:

native HTML5 reference elements:
```
<body>
    <header>This is the header</header>
    <nav>This is the nav</nav>
    <main>This is the main</main>
    <footer>This is the footer</footer>
</body>
```
ARIA best practices call for using native HTML5 reference elements instead of ARIA functions whenever possible, but the markup in the following example works:
```
<body>
     <div role="banner">This is the header</div>
     <div role="navigation">This is the nav</div>
     <div role="main">This is the main</div>
     <div role="contentinfo">This is the footer</div>
</body>
```
It is a best practice to contain all content, except skip links, in distinct regions such as header, navigation, main, and footer.

Link to read more about: click here

2- Why it Matters

Navigating the web page is far simpler for screen reader users if all of the content splits between one or more high-level sections. Content outside of these sections is difficult to find, and its purpose may be unclear.

HTML has historically lacked some key semantic markers, such as the ability to designate sections of the page as the header, navigation, main content, and footer. Using both HTML5 elements and ARIA landmarks in the same element is considered a best practice, but the future will favor HTML regions as browser support increases.

Rule Description

It is a best practice to ensure that there is only one main landmark to navigate to the primary content of the page and that if the page contains iframe elements, each should either contain no landmarks, or just a single landmark.

Link to read more about: click here

Prefer to use rem over px to have your page working better across browsers and resizing the elements properly

The rest is great!!

Hope it helps...👍
Marked as helpful

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord