A Website Starts as an Ordinary Folder

A website can begin as an ordinary folder on your computer. Inside it are files that a browser can read, along with the pictures and words the pages need. You already understand the main organizing idea from the VS Code course: the folder is the project, the files are its parts, and the assistant helps you work with those parts. You do not have to type the code yourself to understand what belongs together.

Our fictional example is Cedar Lane Repair, a small local service business. Its visitors want to know what the business repairs, where it works, and how to ask a question. That is a useful starting point because it gives the website a job. Asking for a beautiful website without describing its job leaves too much for the assistant to guess. A clear purpose helps you judge whether the result is useful.

Open the prepared website folder when you want optional practice. It contains index.html for the example home page, services.html for the service information, contact.html for the contact explanation, and sitemap.html for a readable page list. Each page includes its own style and small interactive behavior so it opens directly in a browser. Other projects may share separate style or script files; the underlying roles are the same.

The extra planning notes stay beside the pages. project-brief.md explains the audience and limits. sitemap.md lists the intended pages and what each page must do. These notes are helpful context for your agent, but they are not automatically public website pages. Keeping a planning file in the project does not mean visitors should receive it. Later we will identify exactly which files are intended for publishing.

For this first look, do not worry about hosting, domains, passwords, payments or search rankings. A local page lets you see an idea before making it available to other people. The public website will eventually need a hosting arrangement, but a preview is already enough to discuss layout and wording. That separation gives you time to make sensible choices while the work is still easy to change.

In the activity, choose the folder whose files answer one small business purpose. Then notice how a short brief gives the assistant something concrete to build toward. A useful request might be: explain what each prepared page does before changing anything. You are beginning by understanding the workspace. That is productive progress even when you have not added a feature or published a single page.