Scenario
An agency would like to provide a “module” of content in a separate subsite that has nothing to do with Drupal. This could be an eLearning module or perhaps a campaign site. Publishing content in this way is an extension of the typical CMS pattern of managing individual content items. In this case, the module of content is treated as a whole where there is less need to manage revisions and authorship.
Challenge
The challenge is that Drupal is a CMS, not a file system. The publishing of subsites is perhaps best left to services designed specifically for this task - static file hosting. In these environments, the management of files and the assignment of domains is much easier. However, agencies may face procurement issues where a service such as GovCMS is easier to procure than hosting on a different host. In these cases, there is a desire to host on the GovCMS site.
Solution
The Mini site module was added to GovCMS to handle this situation. It allows a ZIP file to be uploaded and then unpacked in the files directory. In essence, it provides a convenient way to upload unmanaged files into Drupal. It is considered by many to be an antipattern for a CMS where there is a desire to maintain control over the files that are uploaded. However, the module does provide a convenient solution where there is a need.
Agencies should be aware that there is no out-of-the-box integration back into Drupal. ie. the minisite as uploaded will not be able to talk to Drupal as is the case with typical LMS solutions. There are ways around this with RESTful web services (Webform) where integrations are possible. Agencies should balance the wider needs and consider if a more dedicated solution with an LMS is a better alternative.
Outcome
The Mini site module provides convenience for agencies needing to publish modules of content that may have been produced outside the usual content management workflows of the CMS.
