New Bitloops (Frontend Copilot) documentation.

[SergioBitloops]

Proposed changes

This pull request updates the documentation for the Bitloops front‑end co‑pilot by improving both content and structure to better align with the product and our SEO goals.

Changes include:

Updated existing documentation pages for the Bitloops front‑end co‑pilot, replacing the previous “designed to code” slug with front‑end co‑pilot, which is more accurate and better reflects the current product positioning.

Created new documentation pages that are directly relevant to Bitloops users, focusing on how the front‑end co‑pilot can be used in practice.

Added two new in‑depth sections:

Best practices and patterns – a reference‑style section that outlines recommended approaches, patterns, and common use cases for the front‑end co‑pilot.

UI systems and performance – a deeper dive into how the co‑pilot integrates with UI systems and how it can help optimize front‑end performance.

These sections are written with reference‑oriented content in mind, which will also support our SEO strategy by targeting relevant long‑tail keywords and use‑case queries.

Types of changes

What types of changes does your code introduce to Bitloops Language?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ x] Documentation Update (if none of the other choices apply)