vTaiwan.tw 前端架構
編輯歷史
| 時間 | 作者 | 版本 |
|---|---|---|
| 2015-01-06 12:49 – 12:49 | r537 – r567 | |
顯示 diff（2 行未修改）
*2014/12/16 au&clkao first draft, to be reviewed by frontend team (ly/pm5/soidid)
*2014/12/30 reviewed, prototype to be verified 2015/1/6 morning by ey users
+ *2015/1/6 ey users reviewed & ok'd, http://vtaiwan.tw/mockup/ now reflects this design (in real time!).
*
*
（24 行未修改）
|
||
| 2014-12-31 07:37 – 07:51 | r309 – r536 | |
顯示 diff（1 行未修改）
上層：vTaiwan.tw 行政院法規線上諮詢系統
*2014/12/16 au&clkao first draft, to be reviewed by frontend team (ly/pm5/soidid)
+ *2014/12/30 reviewed, prototype to be verified 2015/1/6 morning by ey users
*
*
Social Object Mapping (Step 1)
- *GitBook Chapter = Discourse Category
- *GitBook Sub-Chapter = Discourse Sub-Category
- *GitBook H2 = Discourse Topic (pre-populated)
- *GitBook H1 (before the first H2) = Discourse new topics (user-initiated)
+
+ GitBook <-> Discourse
+ *SUMMARY.md H1 = Discourse Category (e.g. "群眾募資")
+ *Maybe: Turn README.md into pinned topic?
+ *Section.md H1 = Discourse Sub-Category (e.g. 發展需求)
+ *Section.md H1+p(before first H2) = Discourse Topic (pinned 置頂文)
+ *Section.md H2 = Discourse Topic
+ *(pre-populated with last paragraph?)
+
+ e.g. with http://audreyt.gitbooks.io/vtaiwan-crowdfunding/content/1.html :
+ 群眾募資 是 category，發展需求 是 sub-，股權模式或債權模式 是 topic，發言是回覆 topic
+
+ 「未分類」討論的話，目前傾向於作為置頂文的回文，例如 https://talk.vtaiwan.tw/t/topic/15 — 然後把權限設成這樣：
+ *
UX Ideas
*The left-side navigation panel collapses when user engages in the right-side comment discussions.
*User-selected annotation text becomes metadata of topical anchor for new posts within a topic.
-
+ *
Notes
*Step 2 (react-ask) needs its own social object mapping, TBD.
+ *Step 3 (billlab) also needs its own social object mapping, TBD.
|
||
| 2014-12-26 07:38 – 07:51 | r150 – r308 | |
顯示 diff vTaiwan.tw 前端架構
- *2014/12/16 au&clkao first draft
+ 上層：vTaiwan.tw 行政院法規線上諮詢系統
+ *2014/12/16 au&clkao first draft, to be reviewed by frontend team (ly/pm5/soidid)
*
*
- GitBook Chapter = Discourse Category
- GitBook Sub-Chapter = Discourse Sub-Category
- GitBook H2 = Discourse Topic (pre-populated)
- GitBook H1 (before the first H2) =
+ Social Object Mapping (Step 1)
+ *GitBook Chapter = Discourse Category
+ *GitBook Sub-Chapter = Discourse Sub-Category
+ *GitBook H2 = Discourse Topic (pre-populated)
+ *GitBook H1 (before the first H2) = Discourse new topics (user-initiated)
+
+ UX Ideas
+ *The left-side navigation panel collapses when user engages in the right-side comment discussions.
+ *User-selected annotation text becomes metadata of topical anchor for new posts within a topic.
+
+ Notes
+ *Step 2 (react-ask) needs its own social object mapping, TBD.
|
||
| 2014-12-26 07:38 | r149 | |
顯示 diff（9 行未修改）
|
||
| 2014-12-26 07:38 – 07:38 | r146 – r148 | |
顯示 diff（9 行未修改）
|
||
| 2014-12-26 07:38 | r145 | |
顯示 diff（9 行未修改）
|
||
| 2014-12-26 07:29 – 07:38 | r1 – r144 | |
顯示 diff- Untitled
+ vTaiwan.tw 前端架構
+ *2014/12/16 au&clkao first draft
+ *
+ *
- This pad text is synchronized as you type, so that everyone viewing this page sees the same text. This allows you to collaborate seamlessly on documents!
+ GitBook Chapter = Discourse Category
+ GitBook Sub-Chapter = Discourse Sub-Category
+ GitBook H2 = Discourse Topic (pre-populated)
+ GitBook H1 (before the first H2) =
|
||
| 2014-12-26 07:29 | r0 | |
顯示 diff+ Untitled
+ This pad text is synchronized as you type, so that everyone viewing this page sees the same text. This allows you to collaborate seamlessly on documents!
|
||