Angular

With Blueriq 11, we are introducing a new way of front-end development based on the Angular 5 framework. This will allow you to use today's market standards and build your front-end using a modern technology stack. Furthermore, the usage of Typescript as programming language will help in more maintainable code.

The front-end framework consists of two NPM packages, namely @blueriq/core and @blueriq/angular. The first package is a framework agnostic toolkit that contains interface definitions of the Runtime's UI Rest API and implements common logic for handling API responses. Even if you plan on using a different framework than Angular, this package should allow you to get started quickly. Secondly, the Angular specific package provides tight integration with the Angular framework, allowing you to write idiomatic Angular components for Blueriq elements.

Theming

Out of the box, a default theme is distributed with the Blueriq Runtime for showcase purposes. This theme is built-in and cannot be modified nor extended, which ensures that any custom front-end components do not depend on the specific theme version that is supplied with a Blueriq Runtime version. This approach allows for smaller migrations of the Blueriq Runtime, as any theming related changes do not directly affect your custom theme or components.

For you to get started using theme-development, we plan on publishing the default theme's source code such that you may modify/extend it to suit your needs. This theme uses the Angular CLI for development, testing and building your application.

Angular in Production

For bringing your custom Angular theme into production, please refer to the Angular CLI documentation on building an application into a small set of Javascript bundles for production usage. We recommend serving these files from a different server than the Runtime environment itself, for example a CDN environment specifically for hosting all static assets.

We recommend that all browser traffic flows through the same (proxy) server, for adhering to the same-origin security policy without needing to configure additional CORS headers to allow certain cross origin requests.