Starting a personal website involves two main steps: selecting a domain name and setting up the site content. This article outlines how to approach these tasks with minimal technical overhead, focusing on practical preparation and initial configuration.

Setting Up Your Personal Website

Suppose a hypothetical author is starting a small personal site about hand-bound notebooks. Her folder of notes already holds three title cards: “Paper and Thread,” “Notebook Notes,” and “Folded Pages.” She puts each candidate into a simple comparison file before searching for any of them. The file has three columns—spelling, suffix idea, and short notes—and two fictional rows show how it works: “Papermoth — dot-com — short, one clear image, easy to say aloud”; “Threadfold — dot-net — longer, suggests the binding process, harder to spell on first hearing.” The rows are her own working notes, not listings from any registrar, and a suffix noted there does not mean the registry will accept the name.

For a second exercise, she treats the beginner section as a checklist rather than a list of promises. Her checklist uses real headings a reader could adopt: “Name form and suffix,” “Renewal and transfer notes,” “DNS records,” “First page to publish.” Under “DNS records” she writes two explicit examples: “A record — host @ — points to the web host’s address of record”; “CNAME record — host www — points to the host name supplied by the web host.” In this example the values are placeholders, and she marks the column “confirm in the provider’s dashboard” instead of treating them as finished settings.

She also shows one trade-off rather than presenting every option as equally good. Of the three titles, she would keep “Paper and Thread” and drop “Folded Pages,” because the latter describes a single action while the first covers materials and craft; the suffix idea stays provisional until she checks what is available and what renewal terms apply. She writes “keep the spelling plain enough to say over the phone” as her own reason, not as a universal rule, and she does not claim any registrar’s price or availability.

These are examples she drafted to explain the choices, not accounts of an existing site, user feedback, or a completed trial. She makes no claims that a search box will accept any spelling or that a registration will succeed, and she leaves the DNS steps as items to verify in the actual account before anything is published.

Choosing a Domain Registrar

The cited official guide treats a domain as something needed only at the publishing stage, not as a prerequisite for creating or designing a site. It states that no purchase or payment is required to start, and that a domain becomes relevant when the site is published. For that publishing step, the guide recommends binding a domain purchased from it, and it lists domain configuration under the management entry reached after generation. Beyond that preference and the publishing-stage timing, the guide does not describe how to compare registrars, what to check in registrar terms, or how to evaluate renewal and transfer policies, so this section cannot set out selection criteria from that document. A reader weighing registrars would need information the cited guide does not provide.1

After generation, the guide’s result view offers three entries in the top navigation bar: preview for viewing the site and switching between desktop and mobile views, edit for changing text and images directly, and manage for configuring the domain, managing content, and configuring SEO. These are separate actions in the guide, and the domain step belongs under manage rather than under preview or edit.1

You can turn your registrar shortlist into a simple three-column comparison sheet before you buy anything. Label the columns “annual cost,” “renewal price after the first term,” and “included basics.” For each candidate, fill in the exact price you are quoted for year one, the price shown for renewal, and whether private registration, email forwarding, or basic DNS editing is bundled rather than sold separately. A sample row might read: “first year, 12; renewal, 22; includes privacy and forwarding.” The numbers and labels are placeholders you substitute from your own research, not fixed expectations.

Then add a fourth column for “what I would have to move.” If you later switch registrars, you may need to unlock the domain, obtain an authorization code, and confirm the transfer by email. Note whether a registrar makes those steps findable on its own help pages, and whether the transfer adds a year to your registration. You can decide how much that friction matters to you; a cheaper renewal may be worth less if leaving later feels confusing.

It also helps to record one sentence of reasoning beside each row, so a future you can see why a choice was made. For example: “Chose this one because the renewal price is stated plainly and DNS editing is included.” If two options look nearly identical on price, you might let the clarity of the renewal terms decide.

Keep the sheet in your project folder and revisit it once before checkout. Check that the domain you intend to register is spelled the way you want and that the renewal figure applies to the same suffix. These are your own working notes, drafted to organize a purchase you have not yet made, not a comparison of any particular service. Treat the finished sheet as a record of your reasoning, and adjust any row if your priorities change before you commit.

Preparing Content Before Building

The cited official guide lists four preparation items to think through before the first generation: business positioning (what you do, who the audience is, and what you want visitors to do), a rough page list, visual preference (such as minimalist, business, or lively), and assets such as a company logo, product images, and address and phone details. It also notes that no domain purchase or payment is required to start; a domain is only needed when publishing.1

When describing the site in the creation form, the guide says a good description covers who you are, what pages you want, what features you want, and what style you want. Uploading reference files is optional, with a limit of 10 MB per file and a maximum of 10 files, and the guide notes that after a logo is uploaded the system will try to extract a brand color scheme from it.1

Before drafting another paragraph, you can mark each note card with one label that says what it is for. A card headed “boiling water and linen thread” might be labelled “supports the beginner section,” while “my aunt’s shop receipts” might be labelled “archive only.” This exercise is your own sorting decision, not a report about anyone else’s site. The aim is to see which cards already carry a clear purpose and which are still loose material.

You might then choose one card and rewrite it as a sentence a visitor could act on. If a card reads “glue can wrinkle the paper,” consider “Choose a glue that dries flat, or the paper will wrinkle at the spine.” The second version names a choice and a consequence. Keep the earlier wording beside the new one so you can compare them later rather than overwriting it.

For cards you plan to keep but do not yet want to publish, you can note a destination in your folder: “beginner section later,” “example for the comparison page,” or “unused for now.” Those labels are your own project notes, not site fields. They let you tell the difference between writing that is ready and writing that is merely collected.

You might also draft a short plan for what each finished page should help a reader decide. One page might end with “pick a thread weight,” another with “choose the binding that suits your notebook.” If a page has no such decision, consider whether it belongs in the first version at all.

These are examples you can adapt, not claims about a finished site or a test result.

Configuring Initial Site Settings

Once your site is generated, open the section for configuring initial site settings and work through the on-page options there, using NamesLink where the page directs you to carry out that step. Go through each setting in turn and confirm it reflects your site rather than a placeholder. To verify manually, compare the displayed values against what you intended before you finish.1

Publishing and Binding Domains

According to the cited official guide, a domain is only needed when publishing; the same page recommends binding a domain purchased from NamesLink . It does not describe how to obtain, transfer, or configure that domain beyond this recommendation.1

The guide also directs readers to the Manage entry in the top navigation bar, described as the backend for configuring the domain, managing content, and configuring SEO. No separate binding steps, DNS records, or verification fields are provided in this source.1

Now that the notes are sorted, take the one sentence you just rewrote as visitor-facing copy and decide where it should live before you publish it. You can copy that sentence into a plain text file and set it beside the page title you have already chosen, so the pair reads as a small unit. Read them together: if the title promises “Thread Choices for Beginners,” the sentence “Choose a glue that dries clear” may belong under a different heading. You might move the sentence to a page you have labeled “glue and finishing,” or rewrite it as “Choose a thread weight that holds a folded edge,” which matches the title more closely. This is a sample edit, not a report of what a real visitor saw.

Once a sentence sits under the right heading, you can prepare a simple publishing note for yourself, separate from any account you open later. A usable set of fields might be: page name, intended reader decision, source card, and status. One filled example could read: “Thread weight, choose a weight for folded edges, card three, ready to copy.” A second row might say: “Glue, avoid wrinkling, card five, move to finishing page.” You can keep this note in the same folder as your drafts and mark each row ready or not ready as you revise, deciding for yourself which rows to finish first.

Before you paste anything into a site builder or upload a file, you might read the copied sentence aloud once and check two things: that it names an action a reader can take, and that it does not repeat the title word for word. If it fails either check, you can return it to the card it came from and try a plainer version. Treat this as preparation you are doing, not as evidence that a page is live. When the sentence and the title agree, you have a small, self-contained block you can carry into the next step of setting up the site.

Reviewing the First Draft

In the cited official guide, the only draft step is Step 8, reviewing the requirements document (PRD). The guide states that the PRD is the only low-cost error-correction opportunity: at this point, modifying requirements consumes almost no extra resources, while after code generation, changes must go through the AI conversation modification process, which consumes Credits and takes longer. The guide provides a checklist for this review: whether the page list is complete, whether any needed pages are missing, whether there are redundant pages, whether key features such as forms, booking, and member login are included, and whether the visual style description matches expectations.1

Before generation, the guide says, you can click Edit Requirements Document to directly modify the content and confirm after editing. Once it is correct, click Generate App Now and confirm again with Confirm Generate App.1

A useful next move is to mark your draft against the reader decisions you already planned. Take the three-column sheet you made for the registrar shortlist and add one more column headed “what this draft says about it.” For each row—annual cost, renewal price, transfer effort—write the sentence from your draft that addresses it, or write “missing” if nothing does. This shows you quickly whether the draft carries its weight or only circles a choice. You can decide whether a missing entry needs a sentence or whether the point belongs on another page.

Then read the rewritten visitor sentence beside the heading you assigned it to. Suppose the sentence is “Choose a glue that dries clear so the paper stays flat.” If it sits under a heading about picking thread, it is in the wrong place, and you might move it to a beginner section heading about gluing. If the heading is “Supplies,” consider a narrower heading that names the decision. Try naming the action in the heading and keeping the sentence as the supporting detail.

You can also test the draft against the note-card labels you wrote. Pick one card marked “beginner section later” and check that the paragraph in front of you either uses that material or honestly leaves it out. If the paragraph drifts into a second topic, consider cutting the drifted sentence and saving it under its own label in your folder.

One more pass helps with the comparison sheet: for each row, add a short line saying what a reader should be able to decide after reading. A filled example might read “renewal price — decide whether the second-year cost still fits.” If the draft offers no such decision, you can either write the missing comparison or drop that row from the page and keep it only in your private notes.

Keep these marks as your own working record, not a claim that the draft has been reviewed by anyone else.

Frequently asked questions

How can I first label each note card according to what it is for?

Before drafting another paragraph, you can mark each note card with one label that says what it is for. A card headed “boiling water and linen thread” might be labelled “supports the beginner section,” while “my aunt’s shop receipts” might be labelled “archive only.”

How can I note where I plan to keep cards that I don't want to publish yet?

For cards you plan to keep but do not yet want to publish, you can note a destination in your folder: “beginner section later,” “example for the comparison page,” or “unused for now.” Those labels are your own project notes, not site fields.

What can I add beside each row of my comparison sheet?

It also helps to record one sentence of reasoning beside each row, so a future you can see why a choice was made. For example: “Chose this one because the renewal price is stated plainly and DNS editing is included.”