Draft:Frontend management platform
Submission declined on 4 June 2026 by ChrysGalley (talk). This draft is not adequately supported by reliable sources. Wikipedia's verifiability policy requires that all content be supported by reliable sources.
Where to get help
How to improve a draft
You can also browse Wikipedia:Featured articles and Wikipedia:Good articles to find examples of Wikipedia's best writing on topics similar to your proposed article. Improving your odds of a speedy review To improve your odds of a faster review, tag your draft with relevant WikiProject tags using the button below. This will let reviewers know a new draft has been submitted in their area of interest. For instance, if you wrote about a female astronomer, you would want to add the Biography, Astronomy, and Women scientists tags. Editor resources
|
Comment: AI submissions can't be accepted. ChrysGalley (talk) 11:33, 4 June 2026 (UTC)
A frontend management platform (FMP) is a category of cloud-based software used to build, manage, and deliver the frontend (user interface) layer of websites and applications that are built on API-first or headless architectures. Frontend management platforms connect multiple backend systems, such as e-commerce platforms, content management systems (CMS), enterprise resource planning (ERP), and customer relationship management (CRM) systems through APIs and provide a unified layer for composing, governing, and deploying user interfaces across channels and devices.[1]
Background
[edit]In traditional, monolithic web architectures, the presentation layer is part of the same system that manages content and business logic, as in a classic CMS or e-commerce suite.[citation needed] From the 2010s onward, vendors increasingly decoupled the presentation layer from backend systems ("decoupled" or "headless" architectures), exposing content and commerce functions through APIs instead of rendering pages themselves.[citation needed] This approach later became associated with composable commerce, in which commerce capabilities such as product catalog, checkout, search, and payments are selected as independent, API-connected components and assembled into a custom stack.[2]
Because headless backends do not provide a user interface, organizations adopting these architectures must either build and operate a custom frontend in-house or use specialized tooling. Frontend management platforms emerged as one such tooling category, alongside related offerings marketed as "frontend as a service" (FaaS) and "frontend cloud".[1][3]
Characteristics
[edit]Frontend management platforms typically combine several functions:[1]
- Backend orchestration - connecting and aggregating multiple data sources (commerce, CMS, ERP, CRM, search, or machine-learning APIs) behind a single frontend layer.
- Component and design governance - managing reusable UI components, layouts, and design tokens so that interfaces remain consistent across channels.
- Editorial tooling - visual editors and preview functions that allow non-developers, such as marketing or product teams, to compose and modify pages without code changes.
- Multi-channel delivery - rendering interfaces for web browsers, mobile devices, point-of-sale displays, and other digital touchpoints, often with automated deployment and edge delivery.
See also
[edit]References
[edit]- 1 2 3 "Compare Frontend Management Platforms". OMR Reviews. Retrieved 4 June 2026.
- ↑ "Composable Commerce in 2026 (Redefine Your Tech Stack)". BigCommerce. Retrieved 4 June 2026.
- ↑ "Composable Frontend: Composable Commerce Explained". Netguru. Retrieved 4 June 2026.

Please delete the portions which were LLM-generated, and summarize in your own words a range of independent, reliable, published sources that discuss the subject. If you have used an LLM but you believe that your use is covered by one of the two exceptions (basic copyediting and translation between two languages in which you are fully fluent), please provide a transcript of the prompt(s) you used while writing your draft (see the how-to guide). Reviewers can make mistakes. If you have not received any LLM assistance, you may seek a second opinion at the AfC Help Desk.
See the advice page on large language models for more information.