Terminology

Format of Common Terms

The following list comprises the chosen formatting of terms commonly used in the Entando documentation:

• app

• application

• API

• AJAX

• Angular

• autogenerated or auto-generated

• backend for frontend (BFF)

• blueprint

• bundle

• CentOS

• component

• ConfigMap

• content

• content type

• content attribute

• content template

• cluster, Entando cluster

• Ctrl+C

• digital asset

• Docker

• Docker Compose

• docker-compose for commands

• elastic load balancer (ELB)

• EAP

• FreeMarker

• GitHub, git for code

• Gradle

• Helm template

• ingress, Entando ingress

• Java, JavaScript or JS

• JDBC or Javascript database connectivity

• Jest

• JHipster

• JSON

• Kubernetes, K8s, K3s

• Maven

• mobile app

• micro frontend

• microservice

• MySQL

• NGINX

• OAuth

• Oracle

• OpenShift

• operator, Entando Operator

• Opaque Secret: uppercase when talking about a K8s type of Secret

• page template

• page fragment

• plugin, Entando Plugin

• pod, Entando pod

• pop-up pop-ups

• portal

• PostgreSQL

• propTypes

• React

• ReactJS

• Red Hat

• REST APIs

• Rocky

• SaaS or Software as a service

• Secret: uppercase when talking about Kubernetes Secret

• server-side

• skeleton

• site template

• solution bundle

• Spring

• Spring Boot

• Swagger

• TBD

• TypeScript

• user-facing

• web app

• web UI

• webpack

• widget

• WildFly

• YAML

• Entando Glossary

• Do not backtick Entando terminology

As this list expands, like terms will be grouped into sections (e.g. code parameters, third party products).

Refer to the following documents for current Entando-specific terminology and a summary of language usage to be adopted for Entando technical writing:

• Term and Phrase Substitutions
• Summary of Language Guidelines and Usage