BP_011_en.md

Prefer custom solutions to CMS

Identifiants

GreenIT	V2	V3	V4
2	12	11

Categories

Life cycle	Tiers	Responsible
2. Design	Datacenter	Architect / Developer

Indications

Priority	Implementation difficulty	Ecological impact
3	3	3

Ressources saved
Processor / RAM / Network

Description

Use a framework or a custom solution to have more liberty to optimize the digital service.

To achieve their flexibility, CMS are indeed more resource intensive than simple, custom solutions.

For instance, to manage their plugins, CMS use hook system, which is generally based on a function naming convention. Testing for the existence of new functions uses resources, whereas custom developments don't have to check for new features.

Using too many extensions can slow down the site.

Validation rule

The number of ...	is equal to or less than
extensions of a site using a CMS	3