new.website

What new.website is

new.website generates site layout, style, and copy through dialogue, and it allows the structure and design to be changed the same way, so the positioning is dialogue-driven website generation. The aim is a site you shape by talking, not by learning a builder.

What it does

The product generates layout, style, and copy from a conversation, with the directory noting you can change layout or copy in the same dialogue, which is the distinctive loop: you describe, it builds, you correct in words, and it adjusts. The use cases are generating a site by describing it and editing through conversation, so the iteration stays in language rather than in a visual editor. Because the changes are dialogue-driven, the expectation is a quick site you steer by talking, and the copy is produced as part of the same flow. There is no claim of a polished production system, only a site that arrives and adapts through chat.

Who it is for

People who want a site without learning a builder, and small projects where the speed of a conversational edit beats fine control. It also suits quick sites that will be refined by the owner in conversation rather than by a designer.

What to keep in mind

A site shaped by dialogue is only as good as what the conversation captured, so review the result. Two points to weigh. First, copy generated in a dialogue can read as generic or make claims you did not mean, so read it before publishing, because a sentence the tool wrote is one you are responsible for, and a site that sounds like every other generated site loses its voice. Second, confirm what you can do with the result, because a site you cannot export or host where you choose is a demo, not a base, and the convenience of talking it into being should not leave you unable to leave. Keep new.website for the quick site it promises, but read the copy and own the output, because a dialogue-driven generator is most useful when the words it writes are ones you would stand behind and the result is yours to take.

Two things to pin down before you rely on it. The feature and policy details come from a directory rather than the vendor, so they may be dated or incomplete; check the live product for the current terms. The refund policy noted is strict, with fees treated as non-refundable and access ending with the subscription, which matters more for a managed builder than for software you own. Confirm what you own and where the site is hosted before launching anything publicly.

Treat the first project as a trial of the whole relationship rather than of the builder. Check who owns the domain, what happens to the content if you stop paying, and whether the site can be moved. The strict refund terms raise the cost of a change of mind, so read them before committing a client project. If the answers are acceptable, a chat-driven builder is a quick way to get a presentable site online without assembling a stack.