Brainjocks SCORE™

Brainjocks SCORE empowers content teams to author and edit pages in an intuitive visual editor. Authors can easily create pages using pre-built components by adding them to standard values and creating tenant-specific branch templates. SCORE’s Get Lookup Source Item Rules allow you to define a set of selections that are valid for components when building specific pages on a specific tenant. 

Get Lookup Source Item Rules operate in the background as a sort of Sherpa by directing tenant-specific queries as the content author inserts or edits a component. Each component can automatically find all valid colors, style classes, rendering parameters and other options that are available for the user to select.

These and other features are designed to support component portability. A component used on one site can be reused on a different brand site yet still achieve the unique design, content storage requirements and functionality required for that tenant without affecting others.

Brainjocks SCORE sets the bar high for efficiency, consistency and continuity, and gives you the tools to reach it with every site you build. When presented with the challenge of how to support data exchange between components, SCORE extended its Atomic Construction approach by adding Component Communication Framework (CCF) to its UI layer. This JavaScript-heavy framework provides a data transport channel which components can use to send and receive data. By “communicating” through CCF’s channel, components remain completely autonomous.

With the move towards MVC, JavaScript becomes more supported and important. CCF loads only the JavaScript needed. The CCF Module Loader scans the entire page for all components and insures its scripts are not loaded multiple times. 

CCF's Event Manager allows components to communicate yet remain independent. It starts collecting event triggers as soon as the page starts loading and keeps them in a queue. Event Manager doesn’t start notifying subscribers about triggered events until all modules on the page have been loaded, ensuring components have had a chance to subscribe.

Component portability is key to reaping benefits from a component-based architecture. Coding datasource locations and queries into reusable components is limiting, yet all too common. Rather than dictating a specific content storage requirement or content tree structure, SCORE maximizes portability and reuse by allowing each tenant to decide for itself using Component Datasource Location Rules. 

These locations can be categorized as page-local content folders, site-shared content folders and multisite shared content folders. Writing the queries to find those folders is a challenge and can create complications for how you architect your site. SCORE allows you to overcome this challenge.

Each site can map its own shared content folders, giving the user the choice of where to store content when adding each component to a page. When you edit standard values and branch templates in the Experience Editor, SCORE also maps your multisite shared content folders using datasource location rules.