How to Build a Collaborative Website with AI? | AI for Work Essentials 05

Building a Multi-User Collaborative Website in Five Steps

QwenWork User Guide

The age-old problems of team collaboration: chasing project updates in group chats, files scattered across everyone's personal computers, and having to nag each person for their weekly reports. Want to build a unified website? Hiring a vendor means custom development starting at 50,000 RMB, with a three-week lead time just to change requirements; building it in-house means lacking the manpower and time.

In this issue, we build it ourselves using QwenWork: from a single-sentence prompt to a fully functional, login-enabled, collaborative online website that collects weekly reports, all in just five steps: ① Describe Requirements → ② Break Down Requirements → ③ Design the Solution → ④ Build the Website → ⑤ Publish and Go Live.

01 Describe Requirements

Explain it clearly, and attach a document for better results

No need to write a PRD. Just type "Help me generate a department weekly report workflow website" and send it your existing "Department Weekly Report Workflow" document as a reference: one sentence plus one document, and your requirements are clearly stated.

Here is the prompt—just copy and paste it directly

Replace the department name and pain points with your own (the example uses the department weekly report workflow):

Prompt · Ready to Copy

Help me generate a multi-user collaborative online website for the "Product Design Department," using the uploaded "Department Weekly Report Workflow" document as a requirement reference. Background context: This is for a real department, not a demo. Among the four pain points (task progress tracking, scattered assets, lack of retrospectives, and unrecorded handovers), the first version should prioritize task progress tracking. Roles are divided into two tiers: Person-in-Charge + Regular Members. Management granularity: Project → Task (two levels). Assets are mainly small files (design images/PDFs); large files should be stored as links. The Person-in-Charge dashboard needs two summary views: "Overview + Weekly Report." First, provide a design proposal (give me 2-3 style/theme options, layout planning, interaction logic, account system, and permission rules). I will confirm before you start building. After going live, it must support setting an access password.

The prompt is quite long; scroll up or down to read the full text

02 Break Down Requirements

The AI asks follow-up questions; you just make the decisions

The AI will clarify your requirements in two rounds of questions.

The first round sets the framework: What is the website's core purpose? Which of the four pain points should be solved first? How are roles divided? How granular should task and project management be? Real department application, task progress tracking prioritized, two role tiers (Person-in-Charge + Members), and two management levels (Project → Task)—all four questions answered in four seconds.

The second round sets the boundaries: Which modules go into the first version (how to prioritize the asset library, project retrospectives, and handover records)? What format for assets (store small files directly, or use links for large files)? What summaries does the Person-in-Charge need (Kanban overview, Overview + Weekly Report, or just the Kanban)?

Every item is a multiple-choice question; just click to select: you make the decision, and it remembers. After these two rounds, it understands your department better than a new intern.

03 Design the Solution

Choose from three styles; the proposal is documented

It first generates three theme style drafts: Deep Red for steady business, Blue-White-Gold for reporting, and Dark Green for fresh collaboration. The Kanban structure remains the same; just pick the vibe you like.

Once selected, it provides a complete design proposal: 1. Style and Theme; 2. Layout Planning (the Person-in-Charge sees the project Kanban and asset library on the first screen, while regular members only see their own tasks); 3. Interaction Logic (how to submit weekly reports, how task statuses flow); 4. Account System and Permission Rules.

If you're not satisfied, just say so; it will keep revising until you approve.

04 Build the Website

Watch it build the page brick by brick

Once the proposal is confirmed, the construction begins. The entire build is completed within the chat: it attaches the four design images and processes them one by one. Every step involves "executing commands and modifying files": adding a calendar, creating project switching, building a member selection panel. Which files were changed and what commands were run are fully visible throughout. After building, it automatically runs a full-function verification; only after it passes and test data is cleaned up is it delivered.

What does the final product look like? The Person-in-Charge opens the first screen: 12 tasks to be advanced this week, 2 overdue. The team's recent status is clear at a glance: 187 tasks completed this week (weekly goal 180, achieved), 2,940 mutual assists, average response time 1 hour 24 minutes; delivery completion rate 86% (on time 68%, potentially delayed 22%, overdue 10%); progress of 4 ongoing projects is clear at a glance; the team calendar on the right shows today's three meetings.

Multi-user collaboration is truly collaborative: Account A and Account B are online simultaneously, each viewing their own project perspective with real-time data synchronization. A new member opens the login page and one-click fills in six demo accounts: Person-in-Charge, Visual Designer, Front-End Engineer, Product Manager, Interaction Designer, and Data Analyst, each entering their own homepage.

05 Publish and Go Live

Go live with one click, and you can even add a password

Click "Publish as My Webpage" to get an official URL with the domain qwenwork.host, ready to use by simply opening it in a browser.

Manage everything uniformly in "My Webpages": published status, version number, and dynamic/static type are all clear at a glance. You can also right-click to set an access password: after saving, visitors must enter the password to access the page, making it secure for internal department use.

Newly launched teams don't need training: the website comes with a built-in 7-step onboarding guide. Follow it for 30 seconds, and you'll know how to use the search command panel, team calendar, and create new projects.

Finally, Two Advanced Tips

Tip 1: All Data is in Your Hands

The website features built-in data tracking: page views, completed tasks, searches—who is using it and how much is all visible at a glance on the backend, with a one-click export to Excel (CSV). Digging deeper, every table in the "Database" (tasks, member accounts, comments, milestones, etc.) can be queried directly using SQL, with support for Excel import and export. It's not just a webpage; it's your department's data asset.

Tip 2: Add to Your Phone's Home Screen and Use it Like an App

Open the website URL in Safari on your phone, tap Share → Add to Home Screen, and an icon will appear on your desktop. Tap it to open the full-screen website, indistinguishable from a native app.

That's all for the 5th issue of the AI Office Essential Course. In the next issue, we will continue to unlock the next efficiency scenario with QwenWork.

Follow the "QwenWork" official account to get the latest updates as soon as they are released.

We dedicated to serving clients with professional DingTalk solutions. If you'd like to learn more about DingTalk platform applications, feel free to contact our online customer service or email at This email address is being protected from spambots. You need JavaScript enabled to view it.. With a skilled development and operations team and extensive market experience, we’re ready to deliver expert DingTalk services and solutions tailored to your needs!