Netlify

What Netlify is used for

Netlify connects website builds, deployments and content delivery in one platform. A project can begin from a repository or prebuilt files, and the platform supports modern frontend frameworks. Its capabilities extend beyond static files to serverless functions, edge functions and data services.

A documentation team could publish from a repository, while a marketing team could connect a content system to the same deployment workflow. In both cases, decide which event triggers publication and how an editor confirms that a change has reached the public site.

Build output and dynamic requests

Prebuilt content can be delivered without running the application for every visit. Functions handle routes that need code execution, while preview URLs provide a place to inspect in-progress work. Netlify also exposes caching controls and image transformation features.

For example, a public landing page could be generated during a build, while a form submission is handled dynamically. A successful build validates the published output, but the form’s credentials and external service still need a separate test.

Functions, edge logic and integrated data

Netlify Functions runs backend handlers, while Edge Functions lets applications act in the edge request path. Netlify Blobs stores unstructured data, and Netlify Database supplies a relational data option. These expand a site from generated files into an application with persistence; they have different data access and execution models.

Forms, images and application workflows

Netlify Forms handles website form submissions, and Image CDN supplies image transformations and delivery. Deploy Previews give changes a review URL before production publication. The platform also documents Async Workloads for background processing and AI Gateway for connecting applications to AI services. A content site can use selected features without adopting the entire platform.

Keeping publishing and caching predictable

Write down whether content changes need a rebuild, a cache invalidation or an immediate API response. These are different publication models. A CMS update can be saved correctly while an older build remains visible to visitors.

Use a preview to check redirects, missing pages, environment variables and important integrations. If a project needs a particular framework runtime feature, verify its support and deployment configuration before assuming that every hosting platform behaves identically.