Smoke Testing

Breadcrumb navigation is a secondary navigation pattern that shows the user's current location within a site hierarchy as a trail of links (e.g., Home > Products > Shoes). It helps users understand where they are and quickly navigate back to parent pages without relying on the browser's back button. Proper implementation uses an ordered list within a `<nav>` element with `aria-label="Breadcrumb"` for accessibility.

Headless UI refers to component libraries that provide behavior, state management, and accessibility logic without any predefined styling or markup. Libraries like Radix Primitives, Headless UI by Tailwind Labs, and React Aria give developers full control over visual presentation while handling complex patterns like focus management, keyboard navigation, and ARIA attributes. This approach decouples functionality from design, making it ideal for custom design systems.

Hydration is the process where a client-side JavaScript framework attaches event listeners and interactivity to server-rendered HTML markup. After the server sends pre-rendered HTML for fast initial display, the framework "hydrates" it by reconciling its virtual representation with the existing DOM and making it interactive. Hydration can be expensive on complex pages, which has led to innovations like partial hydration, progressive hydration, and React's selective hydration with Suspense.

Git hooks are scripts that Git executes automatically before or after events like commits, pushes, and merges. Common examples include pre-commit hooks that run linters and formatters, commit-msg hooks that enforce message conventions, and pre-push hooks that run tests. Tools like Husky and lint-staged make it easy to manage hooks across a team, catching issues before they reach the remote repository.

Shadow DOM is a browser API that allows you to attach a hidden, encapsulated DOM tree to an element, isolating its styles and markup from the rest of the page. This means CSS defined inside a Shadow DOM won't leak out, and external styles won't bleed in. It's the core technology behind Web Components and is used by frameworks to achieve true style encapsulation without CSS naming conventions or tooling.

React's Context API provides a way to pass data through the component tree without manually threading props through every intermediate level. You create a context with `createContext`, wrap a subtree with a `Provider`, and consume the value anywhere below with `useContext`. It's ideal for global concerns like themes, authentication state, or locale, but should be used judiciously since any change to context value re-renders all consuming components.