Frequently Asked Questions

website.co.jp is a free training site that teaches people how to build websites with ChatGPT in a clear, repeatable sequence. It is designed for beginners, practical builders, small business owners, and anyone who wants more direct control over their site.

It is mainly for people who want to build or organize websites without getting lost in unnecessary chaos. That includes beginners, founders, writers, side-project builders, domain owners, and small organizations.

No. Beginners can follow the sequence directly, but more advanced builders can also use the workflow as a discipline. The site is useful for anyone who wants a cleaner production method.

No. It helps to become familiar with HTML, CSS, and JavaScript over time, but you do not need to begin as a coder. The site is built around structured use of ChatGPT plus clear file and workflow habits.

Because sequence reduces confusion. If you define the site first, decide filenames next, organize images, save files locally, and only then move toward upload and publishing, the entire project becomes easier to manage.

Local-first building lets you work calmly before the site is public. You can save files, check links, inspect layouts, correct mistakes, and understand your structure before upload. It is safer and clearer.

Yes. Many static HTML websites can be opened locally in a browser. That is one reason local-first practice is so useful for training and early development. It lets you learn the site as files, not only as a remote service.

Because filenames create structure. Once you know the exact pages you intend to build, the project stops floating. ChatGPT also performs better when you can say exactly which file you want created.

Because section index pages should guide readers to real pages, not just promise future content. If detail pages already exist, the section index becomes stronger and more natural.

A homepage is strongest when it introduces real content that already exists. If you make it too early, it tends to become a polished promise with weak destinations behind it.

Because once the site is structurally complete, you can evaluate it as a whole. Grading at the end helps you find weak points, improve priorities, and move the site from “finished enough” to genuinely strong.

Because images affect structure, page strength, consistency, and later HTML generation. When images are named, organized, uploaded, and tracked properly, they become stable production assets rather than loose clutter.

Because saved image URLs let you instruct ChatGPT precisely later. Instead of saying “use some image,” you can say “use this exact image,” which makes future page generation much more reliable.

Usually no. It is better to upload images once they are named, organized, and actually ready to be used. That keeps your server cleaner and your workflow more stable.

For many projects, yes. A single main images folder makes management easier, especially in smaller and medium-sized static sites. It also makes URLs easier to track.

A common CSS file keeps the site visually consistent. It also makes future changes easier. If your buttons, cards, headings, spacing, and layout rules live in one place, you can improve the whole site more efficiently.

A shared JavaScript file keeps common behavior in one place. Menu toggles, checklist counters, reveal effects, and other light interactions stay organized instead of being repeated page by page.

Not by default. Page-specific code should be added only when necessary. The default goal is to keep as much as possible in common files so the site stays clean and unified.

Because they represent practical control. PuTTY helps with command-line access, WinSCP helps with file transfer, and vi helps with direct editing. Together, they support a more independent website workflow.

No. They are useful examples and historically important tools, but the larger lesson is about capability: you should understand how files move, where they live, and how to maintain control over them.

Yes. One of the strengths of local-first practice is that you can build and learn before paying for live hosting. That makes the process less expensive and less stressful at the beginning.

Upload when the structure is clear, the files are organized, the images are ready, and you have already checked the pages locally. The upload stage should feel like a controlled step, not a desperate rush.

It means you should not let your site become something only other people can access, understand, or update. Keep track of your files, domains, hosting access, and structure. Dependency becomes dangerous when it becomes unclear.

No. The point is not that you must personally perform every technical task forever. The point is that your business should not become helpless if one person disappears, refuses, delays, or withholds essential materials.

Because file access is practical power. If you know where the files are, how they are organized, and how they connect, you are in a much stronger position to maintain, improve, or transfer the site when needed.

Not really. It is more about building a stable production system. Good prompts matter, but they work best when paired with a clear file tree, image list, common CSS, defined purpose, and step-by-step structure.

The best way is to be specific. State the exact filename, language, purpose of the page, audience, relevant image URLs, and the requirement to use common site.css and site.js. Specific structure produces stronger results.

Usually no. Build your detail pages and section indexes first. Then, when real content exists, ask ChatGPT to build a homepage that introduces the actual site rather than an unfinished promise.

Yes. In fact, it should. Ask for an honest review of structure, readability, mobile quality, trust, visual consistency, and top improvement priorities. Grading is part of the workflow here.

Webbie is the robot guide of website.co.jp. He is part mascot, part teacher, part reviewer, and part symbol of the site’s method: organize first, build second, publish last.

Because website building can feel intimidating. Webbie helps make the site feel human and memorable while still supporting real structure and discipline. He is not decoration for its own sake.

Professor Webbie is a more formal version of Webbie used when the site wants to signal authority, instruction, or deeper explanation.

Do not build in panic. Organize first. A clear sequence is more valuable than random speed.

Then start by documenting it. Define what the site is supposed to be, list the files you actually need, gather your images, stabilize your common CSS and JS, and rebuild order step by step.

That is one reason the site emphasizes local-first practice. Work locally, save copies, move carefully, and keep your structure understandable. Confidence grows from visibility and repetition.

Start the training sequence. Begin at step 1 and follow the order. That is the fastest path to building a site that feels real, stable, and under your control.