Using components
Components can be built independently using a JavaScript framework, allowing for quick build, test and reuse of components across multiple web pages, websites, portals, apps and channels.
Because they are built using a JavaScript framework, developers can respond quickly to customer needs or market changes by releasing new content, campaigns, or updates.
Component use by role
Developers
-
Build components using developer tools of their choice (for example, Javascript, React).
-
Collaborate across teams by working in their own IDE or code editor and keep their code in a version control system such as
git. -
Test components locally, enabling a much faster development feedback loop.
-
Use less complex back-end coding. The component rendering is kept simple and decoupled from the rest of the DXP, so developers can use APIs and focus on building the front end.
Content editors
-
Self-serve from component libraries to build pages and sites faster.
-
Manage more complex web page features such as parallax scrolling pages or accordions without needing to rely on developers.
-
Spend less time custom editing on applying different branding for sub-brand or sites across various channels (mobile app, kiosks, portal/site).
Administrators
-
Organize components into libraries and make those only available to selected sites or channels for content editors, allowing teams to execute faster and optimize content use.
-
Ensure only the correct version of a component is made available in the component library used by other users.
-
See how new components look and behave across all channels from one centralized platform (DXP), before it gets released to editors.