Engineering guidelines

← Development concepts

The articles are currently available in English and Russian. The English version is shown below.

From principle to everyday work

Ownership, explicit contracts and locality guide implementation. Keep domain behavior with its owner. Extend an established mechanism before adding a new layer. Runtime code consumes configuration through the framework's settings contract.

CMS plugins, API serializers and media lifecycle follow the same rule. A domain plugin remains in its domain; reusable integration belongs to infrastructure. Media processing preserves relative paths, actual image geometry and explicit processing state.

Verification includes service checks, model/migration consistency, behavioral tests and public error semantics. Generated code is regenerated, dependencies are deliberate, and a public API change migrates all its consumers.

Source references

These principles are adapted from the working core-service architecture and engineering guidelines of Fun Tours. The source documents also record project-specific deployment and media mechanisms; those mechanisms remain with their respective owners.