打开豆包工作，说一句“帮我做一份北京红叶旅行手册”，几分钟后，一份排版清爽、带时间轴、带预算表的网页就躺在你的文件夹里。可朋友想看？你得把 HTML 连同图片文件夹一起发过去，朋友们下载、解压、双击打开 —— 手机上还可能错位。想让一群人一起往里填行程、投票、算 AA？更不可能。
问题不在做得好不好，而在做完之后那最后一步：怎么让它被看到、被一起用。
IGA Pages 就是补上这一步的插件——它把豆包工作做出来的页面，一句话变成可以分享、可以共创的在线链接。 下面用一次真实的北京红叶行程，看两个 Demo 分别怎么落地。
个人旅行手册 Demo
这是最基础的用法 —— 一个人做、所有人看。
如何做出来它？
第一步，描述你要什么。
在豆包工作里打开一个新的工作任务说：
帮我做一份「北京 5 日秋季红叶」旅行手册网页：
- 封面用北京秋季主题。
- 按天做时间轴，每天列景点、交通方式、预计停留时间。
- 每个行程节点配一段 100 字左右的介绍和亮点。
- 附一张整体路线示意。
- 最后加一个预算表和 5 条实用贴士。
风格清爽，适合手机看。
几分钟后，一份移动端手册就出来了：慕田峪长城秋色封面、五天时间轴、路线示意图、预算表、五条贴士。它是一个 HTML 文件，待在你的项目目录里。
第二步，说一句“部署”。
这时你不用管它怎么发布、发布到哪、域名是什么。只要说：
帮我部署上线。
第一次部署时，Pages 会引导你完成登录认证（在浏览器里授权一次即可，后续会自动保持登录；授权失效时重新登录即可）。这一步只做一次。
完成认证后，Pages 自动接管：打包项目文件、上传到火山引擎服务器、完成部署，几秒后返回一个公网预览链接。你把它发给同行的朋友，她在手机上点开就是完整的手册 —— 不需要下载、不需要解压、不需要任何设置。
这就是第一件事的价值：一个人做出来的东西，一句话变成所有人都能看到的页面。它适合旅行手册、活动通知、产品介绍页、个人作品集 —— 任何“做好了就发给大家看”的场景。
从“我的行程”到“我们的行程”
旅行手册真到了组队出行的时候，问题才刚开始。
一个人做的手册是给别人看。可真到了行前，群里就开始刷屏：香山和慕田峪先去哪个？酒店定城区还是住景区旁？故宫门票谁来约？这顿烤鸭谁先垫了？钱怎么分？
这些事，一份定稿的手册回答不了 —— 因为它已经“定稿”了，但组队的行程是所有人一起攒出来的。你需要一个大家都能打开、都能往里写、写了别人立刻能看到的地方 —— 一面“大家一起写的墙”。
共创行程墙 Demo
接着上面那个项目，不用推翻重来。你说：
在这份旅行手册的基础上，升级成一个多人共创行程墙：
① 景点投票，大家能点赞、票数实时更新
② 想去清单，任何人都能新增条目
③ 可认领的任务卡（订票/订酒店/租车），显示认领人
④ AA 预算表，自动汇总人均
这些数据要能被多人写入并长期保存下来。帮我部署上线。
关键就在最后那句“多人写入、长期保存”——Pages 识别到这需要数据库，自动接上了火山引擎 Supabase。它做了几件你不需要操心的事：
- 在云端数据库里建好四张表：投票记录、想去清单、任务卡、预算明细；
- 打开行级安全，让任何人都能读、能写，数据长期留在云端；
- 开启实时同步 —— 一个人投了票，其他人的页面几秒内就更新；
- 把页面和数据库一起部署到同一个链接下。
整个过程你不需要写一行代码、不需要建一张表。 Pages 按你的描述把数据库结构设计好，再把它和页面一起发出去，返回一个可分享的链接。
同行的朋友打开页面，先在顶部输入自己的昵称，就能开始协作：给想去的景点投一票、把“五道营胡同午餐”加进清单、认领“订故宫门票”那张任务卡、记下一笔酒店的垫付。
这就是第二件事的价值：从“给别人看”升级到“我们一起写”。它适合组队出行、活动筹备、班级作业、部门小项目 —— 任何“一群人需要在同一个地方对齐信息”的场景。
IGA Pages：补上“用起来”这一步
两个 Demo 背后，是 IGA Pages 在发挥作用。
豆包工作近日正式发布。它能围绕一句话的目标，自动写文档、做表格、生成图片视频，甚至直接搭出一个网页或小应用。你描述想要什么，它就把成品交到你手上。可东西做出来，不等于用起来。
IGA Pages 是豆包工作里的一个内置技能插件。你只需在「插件 - 豆包推荐」中搜索“iga pages”并安装，就可以使用。安装插件以后，当豆包帮你做完一个页面，你只要顺口说一句“帮我部署”、“发出去给别人看”，它就自动接管，不需要你单独找入口、装工具、配环境。
Pages 做两件事：
- 第一件，把静态页面变成可分享的链接。你做的网页在“做好那一刻就定稿了”—— 谁打开都是同一份内容。Pages 把它发布到火山引擎遍布全球的服务器上，几秒内生成一个预览链接。你把链接转发到微信群，对方在手机浏览器里直接打开，不需要任何额外操作。
- 第二件，也是它真正不一样的地方。当你说“这个要多人一起写、数据要存下来”，Pages 会自动接上火山引擎 Supabase —— 一个云端数据库，把“前端页面 + 数据库”打包成一个完整项目一起部署。你不需要懂什么是表、什么是接口，Pages 帮你搭好。正是这一层，让“大家一起用”成为可能。
AI 负责造，Pages 负责流通
两个 Demo 看似不同，其实是同一条路径上的两步。
- Demo 一的静态部署，解决的是“被看到”—— 你做的东西不再困在自己的文件夹里，一个链接就能送到任何人手机上。
- Demo 二的动态部署，解决的是“被一起用”—— 页面不再是一张定稿的纸，而是一面可以共同编辑、共同记录、共同决策的墙。
Pages 不是把东西“做完”的工具，而是把做完的东西“发出去”的那一步。AI 负责造，Pages 负责让它真正流通起来。
立即试用
打开豆包工作，把你最近做的那份东西 —— 一份手册、一个清单、一个活动页 —— 顺口说一句“帮我部署”。你会立刻看到它从文件夹里走出来，变成一个可以转发、可以打开、可以和朋友一起填的链接。
开始前提醒
- 需要火山引擎账号。 第一次使用 Pages 时按提示完成登录授权即可，全程在浏览器里完成。
- 预览链接有效期 3 小时，必须包含有效的 token。 需要长期分享的话，建议在控制台更换使用自己的域名，参考自定义域名配置教程：docs.volcengine.com/docs/Statio… 。链接打不开？先检查是不是复制完整了（链接末尾带一串访问参数）；再看是不是超过 3 小时过期了 —— 过期就重新说一句“部署”。
合法的预览链接必须包含 iga_token 和 iga_time。出于安全考虑，豆包展示的预览链接可能没有这两个参数。这时，你可以直接要求豆包提供保留 iga_token 和 iga_time 的预览链接。
- 火山引擎 Supabase 按实际用量计费。 搭建动态 Demo 前需确保火山引擎账号余额充足，否则可能搭建失败。了解更多计费信息：docs.volcengine.com/docs/aidap/…
- AI 生成具有随机性。 同一句提示词每次生成的版式、配图、文案细节可能不同；上文 Demo 中的页面结构是本次生成的结果，不代表每次都完全一致。你可以多生成几次挑最满意的，再让 Pages 部署它。
本文由 AI图鉴自动抓取并翻译，版权归原作者所有；如需查看原文请点下方链接。
Turning on the Doubao job and saying, "Do me a Beijing red leaf travel manual," a few minutes later, a page with a clear layout, a timeline and a budget sheet was in your folder. But friends want to see it? You have to send HTML along with the photo folders, and friends download, depress, double click on -- the phone may be wrong. It's impossible to get a group of people to fill in, vote, count AA?
The problem is not bad work, but the last step after it is done: how can it be seen and used together?
IGA Pages is the plug-in to this step -- it turns the Doubao job into a shared, co-founded online link. Here's a real trip to Beijing to see how the two Demos landed.
Personal travel manual, Demo
It's the most basic use -- one person does it, everyone sees it.
How do you make it?
Step one, describe what you want.
In the Doubao job, a new task was opened:
Help me make a travel brochure page for Beijing 5 fall leaves:
- Cover with Beijing fall theme.
- Time axis by day, daily location, mode of transport, projected stay.
- A 100-word introduction and a bright spot for each node.
- with an overall routing.
- A final budget table and 5 practical stickers.
Nice style, perfect for a cell phone.
A few minutes later, a mobile manual came out: Autumn cover of the Great Wall, a five-day axis, a map of routes, a budget table, five stickers. It's an HTML file, stay in your project directory.
Step two, say “deployment”.
And then you don't care how it goes to publish, publish, what the domain name is. Just say:
Help me deploy online.
In the first deployment, Pages will guide you to the completion of the login certification (just once authorized in the browser, then automatically maintain the login; re-entry is sufficient when the authorization lapses). This step is only done once.
Upon certification, Pages automatically takes over: pack project files, upload to Volcengine server, complete deployment and return to a public web preview link in a few seconds. You send it to your friends, and she clicks on her phone and she's a complete manual -- it doesn't need to download, it doesn't need to depress, it doesn't need any settings.
And that's the value of the first thing: something that a person makes, a word becomes a page that everyone can see. It's suitable for travel manuals, campaign announcements, product introduction pages, personal collections -- anything that's done and sent to you.
From my trip to our trip.
The travel manual was only beginning when the team was on its way.
A man makes a manual for others. It's true that before the trip, the crowd began to draw screens: which one to go first? The hotel's downtown or next to the view? So who's the ticket to the palace? Who's got the roast duck?
These things, a finalized manual doesn't answer -- because it's "finalized," but the team's itinerary is all developed together. You need a place where everyone can open, write inside, write what others can see right away -- a wall that everyone can write together.
The Wall of the Process, Demo.
Then the top project, you don't have to overturn it. You said:
Based on this travel manual, it was upgraded into a multi-person journey wall:
One spot vote, you can hear it.
You want to go to the list, anyone can add an entry.
3 Available task cards (booking/booking hotel/rent), indicating identification
4 AA budget table, automatically aggregated per capita
These data need to be written and kept permanently. Help me deploy online.
The key is in the last sentence, “Manual writing, long-term preservation”, where Pages identifies this as requiring a database and automatically connects to Volcengine Supabase. It did a few things you didn't have to worry about:
- Construction of four tables in the cloud database: voting records, list of wishes, mission cards, budget details;
- Open line security so that anyone can read and write and data remain in the clouds for a long time;
- Turning on real-time syncs -- one person voted, others' pages were updated in seconds;
- Deployment of pages and databases under the same link.
You don't have to write a line of code, you don't need a table. Pages designs the database structure as you describe it, sends it with the page and returns a shared link.
Friends of their peers open their pages and enter their nicknames at the top, so they can start working together: vote for the site they want, add the "Five Campesian Lunches" to the list, claim the "Royal House Ticket" card, write down a advance from the hotel.
And that's the second thing that's worth: from "seeing" to "we write together." It's suitable for team trips, campaign preparation, class work, small sector projects - any scenario where a group of people needs to match information in the same place.
IGA Pages: Add the step of "Use Up"
Two Demo behind, is IGA Pages working.
Doubao has recently been officially publish. It can automatically write documents, make tables, generate photographic videos, or even direct a web page or a small application around the object of a sentence. If you describe what you want, it delivers the finished product to you. But something made doesn't mean it's working.
IGA Pages is a built-in skill plugin for Doubao jobs. All you have to do is search for and install "iga pages" in "plugin - Doubao recommended" and use it. Once the plugin has been installed, when Doubao finishes a page for you, you simply say, "Set me up" and "send it to someone else" and it automatically takes over, without you having to find a single entrance, install tools, prepare the environment.
Pages does two things:
- First, to turn static pages into shared links. And the web page that you're doing is, "Done at the moment," -- it's the same thing who opens it. Pages puts publish to Volcengine on servers all over the world, generating a preview link in a few seconds. You forward the links to the WeChat group, and the other side opens them directly in the mobile browser, without any additional operation.
- Second, it's really different. When you say, "This one needs to be written together and the data saved," Pages automatically connects to Volcengine Supabase -- a cloud database, wrapping the front page + database into a complete project. You don't need to know what's a watch, what's an interface, Pages. It is this floor that makes it possible to use it together.
AI, building, Pages, circulation.
Two Demos look different, actually two steps along the same path.
- The static deployment of Demo, the solution is to be seen -- what you do is not stuck in your own folder, and a link can be sent to anyone's cell phone.
- The dynamic deployment of Demo II, which addresses the problem of being “shared together” - the page is no longer a finalized piece of paper, but a wall that allows for co-editing, common records and common decision-making.
Pages is not a tool to "do" things, but a step to "send" things. AI is responsible for building, Pages is responsible for making it really flow.
It's a trial.
Open the Doubao job and put the last piece of your work -- a manual, a list, an activity page -- and say, "Help me deploy." You'll see it coming out of the folder immediately, turning into a link that can be forwarded, opened, filled with friends.
Synchronising folder
- Need Volcengine account number. Use the Pages for the first time to do the login authorization by hint and complete the entire process in the browser.
- The preview link is valid for 3 hours and must contain a valid token. If long-term sharing is needed, it is proposed to replace the use of its own domain name on the console with a reference to the custom domain configuration tutorial: docs.volcengine.com/docs/ Statio... Can't get the link open? Check if the copy is complete (with a sequence of access parameters at the end of the link); see if the time has expired for more than three hours -- if the time expires, rephrase "deployment."
The valid preview link must contain iga token and ga time. For security reasons, the preview link presented by Doubao may not have these two parameters. At this point, you can directly request Doubao to provide a preview link to keep iga token and iga time.
- Volcengine Supabase at actual usage. The build-up dynamic Demo needed to ensure that the balance of Volcengine accounts was sufficient, otherwise the build-up might fail. More information on the billing: docs.volcengine.com/docs/aidap/...
- AI generation is random. The layout, layout and file details of each generation of the same sentence prompt may differ; the page structure in Demo above is the result of this generation and does not mean that there is complete consistency in each case. You can generate more than a few times to choose the most satisfying and then have Pages deploy it.
Auto-fetched and translated by AI Atlas. All rights belong to the original author.