¹⁾

1. What is wiki?
   1. “A wiki is a hypertext publication collaboratively edited and managed by its own audience directly using a web browser.”
   2. We don't have to really worry about the hierarchy and structure of the content. Everyone (with privilege) can just continously add/edit information, reorganise, and relate different pages or piece of contents via hyperlinks.
2. Why use wiki?
   1. Knowledge base for incrementally build up our collective capability where every privileged members can contribute, for seamless collaboration (a hive mind).
   2. Knowing current collective knowledge/capability/expertise of the members, new projects (FYP, Master, PhD) can be designed to fill-in the identified gap or explore interesting topics/tools, building up on existing knowledge of the group.
3. Wiki greatly support the use of open-source tools.
   1. Members which directly work on a certain topics will store exact configuration to run a certain problem (the version of softwares, config files, etc), complete to reproduce results, including data analysis routines.
   2. This is important as a workflow of computational mechanics using open source tools usually use those developed by different group therefore compatibility with specific versions can arise.
   3. Computational packages are quickly evolving, therefore it is encouraged that the person working with specific tools to continously document a working or improved workflows for other members to keep updated with recent changes.
   4. Ideally, for long term usability, the set of tools including its software environment used for a certain project should be containerised, and a properly organised wiki with a group of maintainers can ensure that the setup is always reachable.
4. Privacy?
   1. Groups can be created with specified read-only/edit privileges to certain pages. For example, top level admin can read/edit all pages. A group of undergraduate students working on a very specific industrial problem will be added to a sub-group where they can only see pages relevant for their projects.
5. Wiki vs github
   1. github more on source code for a software, and documentation around it. Whereas wiki is for more general contents.
6. large media storage?
   1. can embed files from other host e.g. Youtube, Facebook, Google Drive.
   2. wiki server will only store text and formatting to save space to keep load on the server low.