Terminology

Documentation

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

Format of Common Terms

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

• app
• application
• API
• AJAX
• Angular
• backend for frontend (BFF)
• blueprint
• bundle
• CentOS
• component
• ConfigMap
• content
• content type
• content attribute
• content template
• Ctrl+C
• digital asset
• Docker
• elastic load balancer (ELB)
• FreeMarker
• GitHub, git for code
• Helm template
• JavaScript or JS
• JDBC or Javascript database connectivity
• Jest
• JSON
• Kubernetes, K8s, K3s
• Maven
• mobile app
• micro frontend
• microservice
• MySQL
• NGINX
• Oracle
• OpenShift
• page template
• page fragment
• plugin
• portal
• PostgreSQL
• propTypes
• React
• Reactjs
• Red Hat
• REST APIs
• Rocky
• SaaS or Software as a service
• skeleton
• site template
• solution bundle
• Swagger
• TBD
• TypeScript
• web app
• web UI
• webpack
• widget
• YAML

https://docs.google.com/spreadsheets/d/1PMzv7qhmNgZF6raVq40l-j4Mqn09lxnqGclahEmizsQ/edit#gid=963508268 Entando Terms: do not backtick Entando terms

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