Why not make the front-end configurable? So neither front-end or back-end code has to change, but the UI can re-group and place data different based on changes

Why not make the front-end configurable? So neither front-end or back-end code has to change, but the UI can re-group and place data different based on changes to config files? It adds complexity to your stack to go this way, and often results in a complex implementation/configuration process for new customers, so I truly do not recommend it as a standard practice... but when I have worked on multi-tenant products where each tenant has unique data display requirements, it definitely reduces the churn of re-deployment to meet some one-off need. Of course, you'd still need to decide where those config files live, but it now is a content change, not a code change, to alter the UX.