Building Blocks¶
THe Experience Builder system facilitates the creation and management of server-side rendered web pages. Its modular building blocks provide high flexibility; clear separation of concerns across different market scenarios, and user defined control over UI features for no-code management.
System Configuration¶
system.config JSON resources create global settings and enable the configuration of website behavior. These resources act as the backbone for defining key parameters such as themes, default values, and application-wide preferences. They allow developers to control various aspects of a website’s functionality, from navigation rules to content display options. By centralizing these configurations, JSON resources ensure consistency, simplify customization, and streamline updates, making them essential for managing scalable and dynamic web applications.
Layouts¶
Layouts are Liquid files that delineate the overall structure of the pages. They act as templates that can be reused across multiple pages, ensuring consistency and reducing duplication. While the system for rendering is flexible, layouts are generally the place where top-level HTML tags, style sheets, and functionality reside. Layouts define the overall structure of a webpage, providing a framework that organizes content and ensures a consistent user experience. They serve as the backbone for design and interaction, enabling developers to manage visual elements, responsive behavior, and dynamic features efficiently.
Pages¶
Pages are the core elements of the Experience Builder system. These JSON resources enable the configuration of components and widgets to meet diverse user needs. Acting as the foundation of the user interface, pages define the structure and layout of content, seamlessly integrating dynamic and static elements. They provide a flexible framework for customizing the look and functionality of applications, ensuring adaptability to specific project requirements.
Components¶
Components are Liquid files that expose a configuration schema. These components are reusable modules that can define meaningful configuration settings, which the no-code platform can utilize. They can also be integrated into Visual Editors. Components can define their own data, determine how they are implemented, and interact seamlessly with other components, enabling developers to build modular, scalable, and user-friendly applications efficiently.
Widgets¶
Widgets are JSON resources that allow groups of components to be combined, configured, and used inside Pages. Widgets serve as modular building blocks, enabling developers to create dynamic and reusable sections of a page that can be easily customized to meet specific design and functionality requirements. By combining multiple components, widgets streamline development workflows, reduce redundancy, and provide a scalable solution for managing complex layouts.
Snippets¶
Snippets are small pieces of Liquid reusable code or content that can be included in any Liquid resources. Snippets can also call other snippets and render information passed into them. They enable developers to modularize code for better organization and reusability across applications. By leveraging snippets, teams can maintain consistent functionality, reduce redundancy, and simplify updates, improving efficiency in managing complex projects.
Assets¶
Assets include all static files such as images, CSS, and JavaScript that are used throughout the system. These files serve as essential building blocks for the user interface and functionality, ensuring the consistent delivery of styles, scripts, and visual content. Organized in a structured manner, assets facilitate quick access, efficient loading, and ease of management.
Locales¶
Locales are JSON resources that manage the localization and internationalization of content, enabling support for multiple languages and regions. They store translations, date formats, currency symbols, and other regional settings in a structured format. By integrating locales into an application, developers can provide a seamless user experience tailored to diverse audiences worldwide.
Settings¶
Settings and setting schemas are JSON resources that provide the means to create user-defined JSON structures and configurations. These schemas act as blueprints, allowing developers to define the shape and expected parameters of configurable options within an application. By leveraging setting schemas, users can tailor the functionality and behavior of applications to specific needs, ensuring flexibility and scalability.
Media¶
Media are JSON resources that provide reusability and customization to images, videos, fonts, and documents located in the DAM. These resources enable efficient organization and retrieval of digital assets, allowing developers to apply consistent settings such as scaling, formatting, and metadata across various applications. By leveraging media JSON resources, teams can streamline workflows and ensure assets are easily adaptable to diverse project requirements.
Context¶
Context allows portions of JSON resources to be modified within the scope of a specific market or region. This capability ensures that localized content aligns accurately with the target audience. By leveraging context, developers can adapt applications to reflect the language of individual markets without altering the entire resource file, streamlining updates and maintaining consistency across global deployments.