Quick reference guide to common web development and HeyBoss-specific terms. Bookmark this page for easy reference while building.

Chat Mode: Discussion mode where AI helps plan and debug without modifying code. Perfect for questions and strategy.

Code Mode: Implementation mode where AI actively builds and modifies your code. Use after planning in Chat Mode.

Credits: HeyBoss currency used for AI operations. More complex operations use more credits.

Remix: Create a copy of an existing project to use as a starting point. Like forking on GitHub.

Meta Title: The title that appears in search results and browser tabs. Should be 50-60 characters.

Meta Description: Short summary (150-160 chars) shown in search results. Influences click-through rate.

URL Slug: The readable part of a URL (e.g., /about-us). Should be short, descriptive, lowercase.

Canonical URL: The preferred URL when multiple pages have similar content. Prevents duplicate content SEO issues.

Sitemap: XML file listing all pages on your site. Helps search engines find and index your content.

Alt Text: Description of an image for accessibility and SEO. Screen readers use this for visually impaired users.

Component: Reusable piece of UI (like a button, card, or form). Building blocks of modern websites.

Responsive Design: Website adapts to different screen sizes (desktop, tablet, mobile).

API: Application Programming Interface. How your website talks to external services.

CTA (Call To Action): Button or link encouraging users to take action ('Sign Up', 'Buy Now', etc.)

Hero Section: Large banner area at the top of a page, typically with headline and CTA.

Frontend: What users see and interact with (the visual website).

Backend: Server-side code handling data, authentication, and business logic.

Database: Where your data is stored (users, products, blog posts, etc.)

Deployment: Publishing your site so it's live on the internet.

CDN: Content Delivery Network. Serves your site from servers close to users for faster loading.

Each term is explained in context throughout our documentation. Start with Best Practices for practical usage examples.

See also: Best Practices | All Documentation

Need help? Contact Support