Pages & Components Interview Questions

Pages are special components that become routes automatically when placed in pages/ or app/ directory. Components are reusable UI pieces that don't create routes. Pages can use getStaticProps/getServerSideProps while components cannot.

Server Components are rendered on server by default in App Router. Cannot use browser APIs or React hooks. Better performance and bundle size. Support async operations directly.

Client Components use 'use client' directive. Can use browser APIs and React hooks. Enable interactive features. Run on client side after hydration.

Create layout.js file in app directory. Wraps child pages/components. Shares UI across routes. Supports nested layouts. Uses children prop for content injection.

Hydration attaches JavaScript event handlers to server-rendered HTML. Makes static content interactive. Happens automatically after initial load. Preserves server-rendered state.

Use metadata object or generateMetadata function in page files. Set title, description, open graph data. Support dynamic metadata. Handle SEO requirements.

Create error.js files for error boundaries. Handle component errors. Support fallback content. Implement error reporting. Manage error states.

Use [param] syntax for dynamic routes. Access parameters through props. Support multiple segments. Handle parameter validation. Implement dynamic routing.

Use React Context, state management libraries, or lift state up. Handle component communication. Support state updates. Implement state management patterns.

Use dynamic imports, route-based splitting, component-based splitting. Handle lazy loading. Support chunk optimization. Implement loading strategies.

Implement performance optimizations. Use React.memo, useMemo, useCallback. Support component caching. Implement optimization strategies.

Create reusable component patterns. Handle component hierarchy. Support component inheritance. Implement composition strategies.

Use CSS Modules, styled-components, or other styling solutions. Handle dynamic styles. Support theme systems. Implement styling strategies.

Create unit tests, integration tests. Handle component rendering. Support interaction testing. Implement test strategies.

Implement form handling logic. Handle validation. Support form submission. Implement form state management. Handle form errors.

Create reusable component collections. Handle component documentation. Support theming. Implement component versioning.

Implement animation libraries or CSS transitions. Handle animation states. Support transition effects. Implement animation strategies.

Follow ARIA standards. Handle keyboard navigation. Support screen readers. Implement accessibility patterns.

Create compound components, render props, higher-order components. Handle complex patterns. Support pattern composition.

Track render performance. Handle performance metrics. Support profiling tools. Implement monitoring strategies.

Handle XSS prevention, input sanitization. Support content security policies. Implement security measures.

Implement i18n support. Handle translations. Support RTL layouts. Implement localization strategies.

Create error boundary components. Handle error recovery. Support fallback UI. Implement error reporting.

Implement state management solutions. Handle global state. Support state persistence. Implement state patterns.

Create component documentation. Generate API docs. Support example usage. Implement documentation strategies.

Implement semantic versioning. Handle backwards compatibility. Support version migration. Implement versioning strategies.

Design scalable component systems. Handle component organization. Support architecture patterns. Implement design systems.

Implement deployment strategies. Handle build optimization. Support continuous integration. Implement deployment patterns.