Refactor models for better readability

**Feature request**
It would be great to have analytics for types.

**Use case**
Many users need this functionality for production deployments.

**Implementation idea**
Add a new config option `enable_analytics` with default `false`.

The issue names no files, tests, or entry points. Start by locating configuration handling and any existing analytics or type-processing paths; clarify what “analytics for types” should report before changing anything. Done requires a defined analytics behavior and an `enable_analytics` option whose default is `false`, with tests covering the decision.

Written by the indexing model from the issue text.