Existing Packages and Their Technologies
Universal Core includes a number of web applications, services and utility libraries. These provide functionality ranging from serving content to end users to managing surveys and authenticating users.
List of packages
- unicore.ask - service to store and manage polls and surveys
- unicore-cms - end user application to serve and interact with UC's content (to be deprecated by springboard)
- unicore.content - utility package containing UC's primary content models
- unicore.distribute - service to expose primary content via a web API for distribution purposes
- unicore.google - utility package containing tools for interfacing with Google APIs
- unicore.hub - service to authenticate users and store user profile data
- unicore-thumbor - service to store and serve images
The following technologies are being used in a number of applications and services. Services like
unicore.hub interact with other services via a RESTful API. Thus they can use any technology stack that suits their purpose. As more services are added, this list of technologies will become more diverse.
Pyramid & Cornice
We are using the Pyramid web framework with Cornice to build certain web applications and services. Cornice provides us with the building blocks for RESTful APIs. These APIs allow for interaction between different services and user-facing applications.
When we need to serve some HTML, we prefer using the Jinja2 templating language.
Babel & i18n
All Universal Core applications have to be internationalised. In order to do this, we use Babel with Pyramid and Jinja2. In our Pyramid code we use
TranslationString objects everywhere (more info here). These get translated in templates using Jinja2's
trans tag and
_ function (more info here).