Website & portfolio

Building a Pearl Website in Four Days: An 80% Progress Review

A build-in-progress reflection on a pearl-brand website: page roles, founder-led content, review decisions and the information needed before release.

Huiyang Xie

On this page
    1. Give the homepage and the detail pages different jobs
    2. Turn the founder's point of view into usable content
    3. Make visual feedback specific enough to act on
    4. Keep sample content separate from real product information
    5. What I want the remaining work to prove
  1. FAQ

After four days working on a pearl website for Rachel, I estimated the project was about 80% complete. That is a satisfying point to reach. There is enough of a website to discuss actual pages, wording and interactions instead of asking someone to imagine the finished thing.

I already knew the business through years of brand and marketing work. This article focuses on the new website build: the decisions that made it possible to turn that background into pages we could review.

Give the homepage and the detail pages different jobs

One direction I gave the project was deliberately specific: the homepage could feel more elevated, while the deeper pages should be knowledgeable and approachable, without sounding obscure or constantly trying to sell.

That distinction helped with copy decisions. A homepage line can introduce a visual mood. A series page needs to help someone understand what they are looking at. An About page needs to explain the person and thinking behind the selection.

Without those different jobs, it would be easy to carry the same polished but vague language through every page. A visitor might enjoy the presentation and still leave with basic questions unanswered.

For this build, I kept coming back to the intended reading experience: a strong first impression, followed by useful explanations. That gave me a more practical way to review a headline than asking whether it sounded premium enough.

Turn the founder's point of view into usable content

Rachel's perspective on pearls gave the About page a clear subject. She sees a good piece as something to keep and wear in different parts of life, with different outfits, rather than something that needs to be replaced by another purchase immediately.

I asked for her Chinese and English videos about that idea to sit on the corresponding language versions of the About page. They offer a way to hear the founder explain her approach herself.

The same thinking affects the rest of the site. “Long-term choice” needs supporting content: what the visitor can learn about a piece, how it can fit into everyday wear, and which details need to be confirmed before an enquiry. It cannot do all that work as a slogan.

For price-related content, I chose an explanation of pricing factors and the business model over numerical comparisons with other brands. That keeps the discussion focused on information the business can support, rather than a dramatic claim that would need its own evidence.

These are marketing decisions with consequences for page structure. A build moves more clearly when the content has a purpose before another section is added.

Make visual feedback specific enough to act on

At this stage, feedback can become very detailed: a headline, a video, the order of sections, or where a link should lead. I find that useful. There is a difference between saying “make this feel more refined” and identifying the particular element that is getting in the way.

In this project, the review work included homepage video changes and separate treatment for the brand story and product explanations. Those decisions give the next revision a clear target.

As with my recent personal website review, I have been collecting changes into review rounds. That helps keep the conversation attached to an identifiable version instead of a moving collection of screenshots and remembered requests.

The practical value of a working draft is that it makes these conversations possible. It gives both sides something specific to react to. It still needs judgement: a more polished screen can make an unsupported sentence look convincing, too.

Keep sample content separate from real product information

A product-page mechanism can be tested before every real product is ready. I explicitly asked for a labelled sample product to check the page design and data connection while the real product material was being prepared.

That separation matters. A sample can show whether the structure handles the information. It cannot establish the facts about an item that will actually be offered.

I also asked for a concrete client-materials checklist, including product details, different views of products, real FAQs, terms and gallery material. Those inputs deserve a place in the plan even when the page layouts are already convincing.

I would not use plausible filler to close that gap. The content that makes a product understandable is part of the work, and its source needs to be clear.

What I want the remaining work to prove

The closer a site gets to looking finished, the more useful a separate release checklist becomes. For this project, my review needs to distinguish questions such as:

  • Are the product descriptions and images tied to real, reviewed items?
  • Do the FAQs and terms reflect the business's actual practices?
  • Does an enquiry reach the intended destination, rather than only showing a success screen?
  • Do the Chinese and English experiences preserve the same factual meaning?
  • Have the release settings and visitor-facing links been checked in the version being released?

This is a checklist of what must be established, not a report that every item has already passed. The latest project evidence should decide each answer.

For another small-brand website, the question I would start with is: what do we already know well enough to build, and what still needs the owner's real information or decision? Making that distinction early gives a fast draft somewhere useful to go.

Questions

Frequently asked questions

What does “four days, about 80%” mean?

It is my overall estimate of progress on this build, not a weighted task score or a release-acceptance result. It does not establish how many hours or days remain, or a standard timetable for other projects.

Why give the homepage and product pages different tones?

The homepage can introduce the brand's visual mood. Deeper pages need to explain the products and the person selecting them. I wanted those explanations to be knowledgeable and approachable rather than carrying the same elevated language through every page.

Why use a sample product before the real product details arrive?

A clearly labelled sample can help check whether the page structure and data connection handle the information. It cannot establish the facts of a real item. Actual product descriptions, images and supporting details still need to be supplied and reviewed before release.

What still needs to be checked before calling the website ready?

The release review needs evidence for real product content, business FAQs and terms, enquiry delivery, bilingual consistency and release settings. This article lists those checks; their latest project records determine which have passed.

Share

Found this useful? Share it.

LinkedInXCopy link

Discuss

Want to discuss the idea?

Discuss with me

Author

About the author

Huiyang Xie is a marketing professional based in Greater Vancouver, Canada, working across digital marketing, content, websites, AI-assisted workflows, and cross-cultural marketing. Her work explores how AI can support practical marketing processes while keeping factual review, brand judgment, and human approval in the loop.

Continue reading

Related work and reading

Blog article

What Long-Term Collaboration Adds to Small-Business Marketing

Open

Blog article

My Third Personal Website Visual Upgrade: Making the Work Easier to Read

Open