Let’s take one interactive feature apart so the markup and behavior make sense separately.
What You Need to Know
A class can be reused on many elements and is useful for styling groups. An id should identify one element in a document and can be a target for links or JavaScript.
In this example: apply a shared card class and a section id.
Try the Example
Take a look at the example. We’ll explain the important lines right below it.
<article class="card" id="first-project">
<h2>Robot project</h2>
</article>
<article class="card" id="second-project">
<h2>Garden project</h2>
</article>Let’s Read the Code
- <h2>: A heading divides the page into understandable parts.
- id: An id uniquely identifies an element on this page.
Read the named elements and attributes together. They explain how the browser connects this feature to the rest of the page.
What Happens in the Browser?
When this example includes JavaScript, it supplies behavior that ordinary HTML does not automatically provide. Always think about a fallback.
Start with native behavior. Details, dialog, and popover each solve a different interface problem. Choose the simplest control that actually matches what a visitor wants to do, then test focus and dismissal as well as appearance.
Your Turn
Run this on a local development server if it loads modules or resources. Change the visible text or trigger and check what still works with scripts disabled.
Common Beginner Mistakes
- Assuming new HTML syntax works in every browser without testing.
- HTML supplies structure; JavaScript is necessary for the scripted behavior in this example. Check keyboard access and focus movement too.
Key Takeaways
- A class can be reused on many elements and is useful for styling groups.
- <h2>: A heading divides the page into understandable parts.
- Test the behavior you expect rather than trusting how the snippet looks in your editor.