

Suspendisse ornare gravida mi, et placerat tellus tempor vitae. Proin nunc lacus, semper sit amet elit sit amet, aliquet pulvinar erat. Praesent nulla mi, rutrum ut feugiat at, vestibulum ut neque? Cras tincidunt enim vel aliquet facilisis. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Curabitur vitae tortor id eros euismod ultrices. Mauris interdum fringilla augue vitae tincidunt. It also keeps my Sass organised, therefore it avoids too much nesting and keeps things readable. This approach can have its drawbacks, yet I’ve found it to be sustainable on larger projects because it makes me think about how many elements I’m nesting and if it’s necessary. accordion-section inside it, which is then followed by an. That’s because I follow a basic principle which uses nested-naming. Some of you will notice it’s not actual BEM.

When coding up components I like to follow the BEM structure. You might also like: Creating Tabs with HTML, CSS & jQuery Table of Contents If you could simply scroll the titles and have the content hidden, it would allow you to scan much faster, therefore giving a better experience. Imagine browsing an FAQ and you had to scroll all the way down through loads of sections to find the answer, it would be a painful.

That’s a good argument as they show a simple outline of the content. If printed to the page, FAQs could stop users from finding the answers they’re after due to all the text they’re presented with. An accordion is usually associated with FAQ areas.
