Português
EnglishFive Steps to Build a Multi-User Collaboration Website
QwenWork Usage Guide
The age-old problems of team collaboration: project progress is tracked by constant group message inquiries, materials are scattered across individual computers, and weekly reports must be individually requested. Want to create a unified website? Hiring a vendor for custom development starts at $50,000, with requirement changes requiring three weeks of scheduling; maintaining your own tools lacks both manpower and time.
This issue teaches you how to build one using Qwen Office: from a single sentence describing your needs to a multi-user collaborative online website that can be logged into and used to collect weekly reports—just five steps: ① Describe the requirements → ② Break down the requirements → ③ Design the solution → ④ Build the website → ⑤ Launch it.
01 Describe the Requirements
Verbal explanation, with documents preferred
No need to write a PRD (Product Requirements Document). Simply enter "Help me generate a departmental weekly report workflow website," then send your existing "Departmental Weekly Report Workflow" document as a reference—just one sentence plus one document clarifies the requirements.
Attach task instructions, copy directly
Replace the department name and pain points with your actual situation (using the departmental weekly report workflow as an example):
Instructions · Copy directly
Help me generate a multi-user collaborative online website for the "Product Design Department," using this uploaded "Departmental Weekly Report Workflow" document as a reference. Background note: this is a real-world application, not a demo. Among the four pain points (task progress tracking, scattered materials, lack of post-mortems, no handover records), prioritize solving task progress tracking in the first version. Roles are divided into two tiers: managers and regular members. Management granularity is at two levels: projects and tasks. Materials are mainly small files (design images/PDFs); large files use links. The manager's interface requires two summary views: overview and weekly report. Please provide a design proposal first (2–3 style options, layout planning, interaction logic, account system, and permission rules). I will confirm before proceeding with development. After launch, access passwords should be configurable.
The instruction is lengthy; scroll up and down to view the full text.
02 Break Down the Requirements
AI asks follow-up questions—just make decisions
The AI will clarify the requirements in two rounds.
In the first round, it defines the core: What is the purpose of this website? Which of the four pain points should be solved first? How are roles divided? To what level are tasks and projects managed? Real-world application, prioritize task progress tracking, two role types—managers and members, project-to-task management—four questions answered in just four seconds.
In the second round, it sets boundaries: Which modules should be included in the first version (material library, project post-mortem, handover records)? What form do materials take (small files stored directly, or large files linked)? What summaries does the manager’s interface require (dashboard overview, overview plus weekly report, or just dashboard)?
Each question is multiple choice—just click to decide; the AI records your choices. After these two rounds of questioning, it understands your department better than a newly hired intern.
03 Design Proposal
Choose from three styles; proposal delivered in written form
The system generates three theme style drafts: deep red business style, blue-white gold reporting style, and dark green collaborative style. The dashboard structure is consistent; choose the visual tone you prefer.
Once selected, you receive a complete design proposal: 1) Style theme; 2) Layout planning (managers see the project dashboard and material library on the homepage; regular members only see their personal tasks); 3) Interaction logic (how to submit weekly reports, how task statuses flow); 4) Account system and permission rules.
If unsatisfied, simply request revisions until you approve.
04 Build the Website
Watch as it constructs the pages brick by brick
After confirming the design, construction begins. The entire process unfolds in the chat window: four design diagrams are loaded and processed step by step, each action labeled "execute command, modify file"—add a calendar, set project switching, create a member selection panel. Every file modified and every command run is clearly visible. Once completed, it automatically runs a full-functionality test; after passing verification and cleaning up test data, it is handed over.
What does the finished product look like? Managers open the homepage: 12 items to advance this week, 2 overdue; team status summarized on one screen: 187 tasks completed this week (weekly goal: 180, achieved), 2,940 instances of mutual assistance, average response time 1 hour 24 minutes; delivery completion rate 86% (on-time 68%, possibly delayed 22%, overdue 10%); progress of four ongoing projects clearly visible; on the right, the team calendar lists today's three meetings.
True multi-user collaboration: accounts A and B are online simultaneously, each viewing their exclusive project perspective, with data synchronized in real time. New members open the login page, where six sample accounts are pre-filled: manager, visual designer, front-end engineer, product manager, interaction designer, and data analyst, each entering their dedicated home page.
05 Launch the Website
One-click launch, password protection optional
Click "Publish as My Webpage" to obtain a permanent URL containing qwenwork.host; open it in a browser to use.
Manage everything centrally under "My Webpages": published status, version number, dynamic/static type—all clearly visible. Right-click to set an access password: once saved, users must enter the password to access the site, ensuring secure internal use.
Newly launched teams require no additional training: the site includes a seven-step onboarding guide. Follow the steps for 30 seconds to easily master features such as the command panel, team calendar, and creating new projects.
Finally, Two Advanced Tips
Tip 1: Keep Data at Your Fingertips
The website tracks usage data: page views, tasks completed, search history—who is using it and how much—all visible in the backend dashboard, exportable as an Excel (CSV) file. For deeper insights, each table in the database (tasks, member accounts, comments, milestones, etc.) can be queried directly via SQL, supporting Excel import and export. It's more than a webpage—it's your department's data asset.
Tip 2: Add to Mobile Home Screen—Use Like an App
Open the website URL in Safari on your phone, select Share → Add to Home Screen, and a new icon appears on your desktop. Tapping opens the full-screen website, indistinguishable from a native app.
That concludes Lesson 5 of the AI Office Essentials series. Next time, we'll explore another efficiency scenario with Qwen Office.
Follow the "Qwen Office" official account for the latest updates.
DomTech is DingTalk's officially designated service provider in Macau, specializing in providing DingTalk services to clients. If you'd like to learn more about DingTalk platform applications, contact our online customer service, call +852 95970612, or email [email protected]. We have a skilled development and operations team with extensive market experience, ready to deliver professional DingTalk solutions and services!