Open joliet opened 5 years ago
The team is looking at Jekyll for this - https://jekyllrb.com/. Jekyll would be used for both help docs and for the content for apps in the App Store. Jekyll is a good choice because it can be easily updated in the Kits GitHub repo using markdown. This makes it easy for academic technology staff and instructional designers to maintain Kits documentation. Jekyll is also free and open source.
DWS suggests that we move to something better than Drupal for delivering content to Kits. There's a general sense in OIT that a more lightweight content management system at Duke would be good to move to/identify for many project. This specific issue for Kits is to make sure we have this tracked to implement when a new solution is ready - either for Kits or Duke.
How might we (the Kits project team)
Questions How does this affect open-source Kits? Do we need an open source content management system?
Assumptions
Hypotheses