fix: 完善模板可视化编辑闭环与通用验收
This commit is contained in:
1 parent
fa6b492bce
commit
22a82dbfba
39 files changed
+7773
-443
No files matched your search
@@ -15,16 +15,17 @@ This document records where template-controlled content is stored and how it rea
|
||||
|
||||
## Food Schedule Example
|
||||
|
||||
The food template declares the schedule type for the `home` and `service` pages. Its Admin fields map directly to existing database columns:
|
||||
餐饮模板的日程在 service 页展示,使用 TrustContent.config 的浅层字段:
|
||||
|
||||
- `adminFields.title` edits `TrustContent.title`.
|
||||
- `adminFields.summary` edits the primary weekday schedule in `TrustContent.summary`.
|
||||
- `adminFields.content` edits the weekend and supplementary schedule in `TrustContent.content`.
|
||||
- The public workspace returns those values as a `RuntimeTrustItem`; the home and service page renderers read `item.summary` and `item.content`.
|
||||
- title 编辑日程区块标题。
|
||||
- weekdayLabel、weekdayTag、weekdayDetail、weekdayHours 编辑工作日卡片。
|
||||
- weekendLabel、weekendTag、weekendDetail、weekendHours 编辑周末卡片。
|
||||
- status 编辑日程状态。summary 和 content 已在该类型声明中隐藏,不参与日程渲染。
|
||||
- 配送范围与流程分别使用 coverage 和 process 类型的配置字段,不能把摘要或正文作为第二套结构化数据入口。
|
||||
|
||||
No schedule-specific Prisma migration is needed. Different templates can choose different field labels while retaining the shared trust-content storage contract.
|
||||
编辑器区域列表和 renderer 的 slot 均优先使用带结构化配置的记录。页面点选传递真实 recordId;没有记录时提供内容管理入口。保存只影响品牌草稿,发布后公开 Runtime 才更新。模板样例仍属于包,不作为数据库注册目录。
|
||||
|
||||
The Admin editor lists the selected template's declared trust types and uses their `adminFields` labels, help, and placeholders. In the food workspace, the service page links directly to the trust-content editor, so the schedule is configured under **内容管理 → 信任内容 → 出摊安排**. Saving changes the brand's draft content; the Mini Program sees the new values after the next publication.
|
||||
详情页中的业务记录只提供选择预览;公共标题和按钮文案通过品牌配置区域编辑,影响全部详情页,不复制到每条业务记录。
|
||||
|
||||
## Inquiry Field Runtime Mapping
|
||||
|
||||
|
||||
Reference in new issue
Block a user