Skip to content
This repository has been archived by the owner on Apr 16, 2024. It is now read-only.

Best practices

Michael edited this page Dec 14, 2017 · 8 revisions

Development

This block collects the best practices for the development of geli.

Frontend

General

As we use angular/material2 as our design components, which is still in development, we noticed during our development efforts that sometimes features are incomplete or not working as we need. So we used plain CSS as a workaround, e.g. the lecture component with its list.

Backend

We use HTTP error codes to return errors to the clients. Throwing an HTTP error is done by using exceptions, e.g. throw new BadRequestError('No lecture ID was submitted.');

Other

Tinyfy Images

To save space and traffic we should tinyfy all static images with eg. https://tinyjpg.com before the first commit of the file.
We may consider to use a npm-package to scale and deliver different sizes of images.

Usage

This block collects the best practices for the usage of the geli platfom.