fix: navbar Components button redirect to buttons section

[anurag5603]

Pull Request Description

Fixed a broken navbar link — the Components button in the top navigation bar was not redirecting anywhere because it pointed to #components, a section ID that does not exist in the documentation. Changed the href to #buttons which is the first components section on the page.

---

Type of Change

• ✨ New animation / hover effect
• 🧩 New component
• 📝 Documentation improvement
• 🐛 Bug fix in an existing submission
• Other (describe below)

---

Submission Checklist

⚠️ PRs that fail this checklist will be closed without review.

• All changes are inside submissions/examples/your-feature-name/
• Includes demo.html — self-contained, opens in browser with no server
• Includes style.css — raw CSS for the proposed feature
• Includes README.md — what it does, how to use it, why it fits EaseMotion CSS
• No changes to core/
• No changes to components/
• One feature per PR (no bundled unrelated changes)

---

Feature Description

What does this add?
Fixes the broken Components navbar link in the documentation site.

How does a developer use it?

<!-- Navbar Components button now correctly scrolls to the buttons section -->
<li><a href="#buttons">Components</a></li>

Why does it fit EaseMotion CSS?
This is a documentation bug fix. The navbar Components link was pointing to a non-existent #components anchor, making it completely non-functional. This fix improves navigation UX for all users of the docs site.

---

Demo

• Demo added (demo.html works by opening directly in a browser)

---

Browser Testing

• Chrome
• Firefox
• Edge
• Safari (optional but appreciated)

---

Notes for Maintainer

This is a one-line fix in docs/index.html. The Components navbar link was using href="#components" but no section with id="components" exists in the page. Changed it to href="#buttons" which is the first components-related section. Feel free to adjust the anchor target if a dedicated #components section is added in the future.

---

Reminder: Only the repository maintainer may merge pull requests.
Do not self-merge, even if you have write access.
Maximum 2 active assigned issues per contributor — unassign extras before opening a PR.