We are excited to have developers building on the UQ Drupal platform. As we progress, we hope to make this easier for you and invite your feedback and questions.
To get started, please read the following information:
*Please note any configuration that can be exported to a feature, should be exported to a feature.
A feature is a Drupal module that provides a collection of Drupal entities which taken together satisfy a certain use case. The list of available features components will change depending on what modules are enabled on a site and which modules have features support. This may be such components as Content Types, Roles, Taxonomies and Views.
UQ Drupal has many custom enhancements that differ from a traditional Drupal install at every layer, from the back-end infrastructure architecture to the way content is displayed. A UQ-Drupal site comes preconfigured with a UQ theme, integrations with UQ-wide Single Sign On and much more.
The platform is patched and maintained centrally, so there is no need to perform updates on sites developed using UQ-Drupal and hosted on the central ITS service.
These technologies may be replaced in a local development instance, e,g:
The UQ Web Development group have adopted Drupal development best practices and a “Code Driven Development” approach to support the long term maintainability, reusability and sustainability of features.
These principles are the basis for the short review process or based on the customised UQ experience of the development team.
UQ Drupal Dev team runs multiple physical boxes that may all run completely independently of each other if the need arises. Database and assets are replicated in a multi-master arrangement.
File storage occurs via Storage API using a custom module to provide RIAK container support. The choice of technology here (RIAK) is irrelevant, but all content storage and retrieval needs to happen through Storage API. This means selection of third party modules is made with this consideration in mind. The UQ Drupal Dev team provides a custom file browsing module (fork of KCFinder) that integrates with Storage API. They also provide a custom image/file picker that integrates with Field UI and filefield sources.
Sites that exist within UQ branding must use the provided UQ Standard theme and be based on the provided UQ Minimal install profile. Base permissions & roles are provided by the UQ core feature, and may not be altered. Custom roles may be created when necessary, however.
You may use any of the modules available from the centrally provided pool. Additional 3rd party modules will be considered on a request-by-request basis, but arbitrary modules may not be added to a UQ-Drupal site. This is to guarantee stability, security & performance of the platform.
A custom module has been developed which allows for installation and maintenance of common content types and taxonomies. These content types & taxonomies are maintained centrally, and updates to them will automatically propagate to consuming sites. They should always be used rather than creating localised structures where possible. Content created using centralised data structures may also be shared amongst other UQ-Drupal sites.
Start playing with UQ Drupal now by generating a sandbox site. Sandbox sites are available to anyone with a UQ staff login.
Join the active discussion mailing list for developers currently using or planning on using Drupal. Topics cover everything from discussing module choices, posting module code for review, to theming and templates discussion. Access can be requested via https://lists.eait.uq.edu.au/mailman/listinfo/uq-drupal-discuss.
If you run into any problems or have a feature request, please or submit a ticket to >email@example.com
If you would like to share your questions or help answer some, please post in the forum