Abstract Names

Always prefer abstract, semantic, technology-neutral names for every platform-owned identifier, including directories, files, variables, functions, properties, and generated names. Name concepts by their purpose so names remain meaningful when an implementation changes. Prefer names a layperson can understand. For example, use container rather than docker, iam rather than keycloak, webServer rather than nginx, site rather than nextJs, and iamTheme rather than keycloakTheme. Follow camelCase naming conventions. Keep a technology name only where an external interface requires its exact spelling.

Correct

container
iam
webServer
site
iamTheme

Incorrect

docker
keycloak
nginxConfig
nextJsSite
keycloakTheme