Wiki

[killua-eu]

General concept:

• simple Markdown powerded wiki (stackedit.io)
• flat structure (hierarchies won't reflect in url/path)
• attachments bound to each doc
• rbac auth on wiki docs
• revisions
• main backend: sql. tables:
  • wikies (each wiki is meant as a collection of entries on a specific topic with specific access rights)
  • wiki entries in current revision + wiki metadata (access rights can be managed away from the default defined by the wiki containing the entry by specific users)
  • all wiki entry revisions (1 line = json with data and metadata about 1 revision of 1 entry)
  • (stor tables for file storage)
  • consider taking out the per-rollam into a separate table?
• alt. backend: git (can be implemented later)
• metadata on each wiki entry:
  • views stats
  • edit stats
  • 'per rollam'-style read & understood & agreed stats (digital signing by logged in users that they read/understood/agreed to the content of the wiki) - per rollam signatures will apply only to a specific revision. if an update is performed, a new sign-request will be asked for.
  • require per-rollam to apply to an attached file(s) too
  • per rollam signatures may have a time-framed validity even if document doesnt change (i.e. 1 year). after this time, a new read-request response is required.
• api endpoints:
  • check if user x read article y in revision z (by default z=current)
  • print (format f = json / html) list of users that read article y on day z
  • print article as pdf

[killua-eu]

Updates:

• see if we shouldn't do per rollam as a separate module. we might actually use this elswhere too (i.e. legito service clone)
• per rollam requires external validation. ideal would be a 2FA via password+sms/email codes so that we have an independent 3rd party as someone who can validate signatures. mechanisms should be easy to extend (i.e. send photo with date, face and signature)