Skip to main content

Documentation Index

Fetch the complete documentation index at: https://we0-f8eb3f1a.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

In We0.ai, the first step to building a website isn’t drawing wireframes or writing long documents — it’s clearly describing your idea.
The clearer your description, the easier it is for AI to understand your goal and generate a website plan that matches your expectations.
This chapter isn’t about writing “professionally” — it’s about writing “clearly.”

1. Why Clear Requirements Matter

Many users write something like this on their first try:
Help me make a nice-looking website.
This isn’t entirely unusable, but the problem is there’s too little information. The AI can’t accurately determine:
  • Whether your website is for showcase or conversion
  • Who your target audience is
  • What style you want
  • What pages you need
  • Whether you need forms, blogs, CMS, SEO, or other capabilities
So rather than “writing fancy,” what matters more is making the core information clear.

2. What a Clear Requirement Should Include

2.1 Website Goal: Tell the AI what this website is for.

  • For example:
  • Corporate website
  • Brand showcase site
  • Lead generation landing page
  • Portfolio website
  • For example:
  • Campaign page
  • Content hub
  • Interactive quiz site
  • Interactive website

2.2 Target Audience: Tell the AI who this website is for.

For example:
  • Overseas SaaS customers
  • Local service users
  • Job seekers
  • Brand partners
  • Young consumers
  • Entrepreneurs or enterprise clients
The clearer the target audience, the more accurate the website structure, copy direction, and conversion design will be.

2.3 Style & Tone: Tell the AI what feel you want for the website.

For example:
  • Clean, professional, trustworthy
  • Techy, futuristic, modern
  • Youthful, relaxed, fun
  • Premium, minimalist, strong brand presence
  • Warm, natural, lifestyle-oriented
If you have reference websites, you can add a note or use the Intent Recognition feature:
Style reference: [brand website], overall clean with lots of whitespace, emphasizing professionalism.

2.4 Pages & Content Structure: Tell the AI what pages you need, or at least what content you want to showcase.

Common pages include:
  • Homepage
  • About Us
  • Products or Services
  • Case Studies
  • Blog or Content Pages
  • Contact Us
  • Pricing
  • FAQ
If you haven’t decided on pages yet, you can say it differently:
I want to highlight product capabilities, customer case studies, pricing plans, and contact information.

2.5 Features & Conversion Actions: Tell the AI what this website should do beyond displaying content.

For example:
  • Book a demo
  • Lead capture form
  • Contact / consultation
  • Content updates
  • Blog publishing
  • Product showcase
  • Payment or login
  • Result page sharing
This step is crucial because it determines whether the website leans more toward a showcase site, content site, or a product-capable website.
If you’re not sure how to organize your thoughts, use this formula:
I want to build a [website type], targeting [target audience], with a [style keywords] feel. I need [pages or content structure], and I want users to be able to [conversion actions or features].
You can also write it more naturally, for example:
I want to build an AI SaaS website targeting overseas customers, with a clean and professional style. I need a homepage, features page, pricing page, blog, and contact page, highlighting automation capabilities and guiding users to book a demo.

4. Ready-to-Use Requirement Templates

Template 1: Corporate Website

I want to build a corporate website named [ ], targeting [small and medium businesses], with a [clean, professional, trustworthy] style. The site needs [homepage, product introduction, case studies, about us, and contact page], highlighting our core service of [ ], and guiding [users to submit a consultation form].

Template 2: Brand Showcase Site

I want to build a brand showcase site named [ ], targeting [young consumers], with a [trendy, clean, brand-forward] style. The site should showcase [brand philosophy, flagship products, user reviews, and purchase entry points], with [room for future content updates].

Template 3: Personal Portfolio

I want to build a personal portfolio website named [ ], targeting [potential clients and recruiters], with a [clean, premium, design-focused] style. The site needs [homepage, personal intro, work showcase, services, and contact information], highlighting my [design style and past project experience].

Template 4: Content Hub

I want to build a content hub on the topic of [ ], targeting [entrepreneurs and indie developers], with a [clear, professional, tech-oriented] style. The site needs [homepage, topic articles, case studies, and a subscription entry], with the ability to [continuously publish content and build search traffic].

Template 5: Interactive Creative Website

I want to build an interactive creative website on the topic of [ ], targeting [young users], with a [fun, engaging, interactive] style. The site needs [test entry, question pages, result pages, and sharing pages], allowing users to [generate result cards and share with friends] after completing the interaction.

5. If You’re Not Sure Yet, Start Simple

Not everyone can write complete requirements from the start. If you’re still exploring, focus on three key things:
  • What type of website you want to build
  • Who it’s for
  • What you want the website to ultimately achieve
For example:
I want to build a corporate website, mainly for potential clients, that looks professional and trustworthy, and ultimately gets users to leave their contact information.
This is already far more effective than “make me a nice website.” You can always add more details about pages, style, features, and reference sites later.

6. What Not to Write

These types of descriptions usually have too little information for AI to work with:
  • Make me a website
  • Build a fancy corporate site
  • Give me a nice-looking page
  • Make something techy
The problem with these descriptions isn’t that they’re “wrong” — it’s that they lack information. Style without goals, pages without audience, “nice-looking” without functionality — the results will typically be vague.

7. Practical Tips for Writing Requirements

Good requirements aren’t about writing more — they’re about writing the goal, audience, style, pages, and features as clearly as possible.