Build Basics / Standard term
Static versus dynamic site
Static delivery serves prebuilt assets, while dynamic delivery computes some response or data at request time; modern sites often combine both.
A documentation page may be pre-rendered and served from a content-delivery network, then call a dynamic API from the browser. A personalized route may render on a server, at an edge function, or through client-side data fetching. The useful question is which parts require trusted computation or changing data, not which single label applies to the whole project.
Builder example
Static assets can simplify caching and hosting, while dynamic components add runtimes, permissions, data stores, and failure paths. Serverless and edge systems provide request-time computation without one always-on machine, so architecture and traffic determine cost.
Common confusion: Interactivity does not require dynamic page rendering, and a mostly static site can still depend on dynamic services. Authentication and secret-backed actions require a trusted runtime even if the form itself is a static file.