vTaiwan.tw 前端架構

上層：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
• 2015/1/6 ey users reviewed & ok’d, http://vtaiwan.tw/mockup/ now reflects this design (in real time!).
•  

Social Object Mapping (Step 1)

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.