A static site is one with no server-side processing at all — plain HTML, CSS, and JavaScript files, sent to the browser exactly as they are stored, with no PHP, no database query, and no server-side logic deciding what to send. Hosting for this kind of site is dramatically simpler than everything covered so far, and often free.
A static host does not need to run any code at all — no PHP interpreter, no application server, no database. It just needs to store files and hand them out on request, which is one of the cheapest, most reliable things a server can do. That simplicity is exactly why static hosting is frequently free, and why it scales to enormous traffic with very little effort.
What does not count: anything running PHP on each request, anything querying a database live, and anything needing server-side logic to decide what to send back. WordPress and PHP sites, by their nature, are not static — see the note on `getStaticProps`-style approaches for advanced cases, which are outside the scope of this introductory category.
Static hosting is commonly offered free by cloud platforms (the same ones covered in the previous lesson), by dedicated static-hosting services, and as a basic feature of most CDNs, covered later in this category. Because there is no processing to manage, it is also naturally suited to being served from many locations at once, which is precisely the connection to CDNs made explicit soon.
For a portfolio site — the exact kind of project the Career Skills course tells you to deploy — static hosting is very often the right, and free, choice. It is worth using for any project that genuinely does not need a database or server-side logic, regardless of how it was built.
The moment a project needs to save data submitted by a user, query a database, or run any logic that must happen on a server rather than in the visitor's browser, it is no longer purely static. That doesn't mean starting over — many real projects combine a static frontend with a small separate backend API (exactly the Node.js pattern taught in this site's Node.js course), which is a different and increasingly common architecture, covered briefly in the edge and serverless lesson later in this part.