Forge Community

Forge Community Introduction Image

Join the Forge Community as we collectively build an ecosystem of widgets and capabilities everyone can leverage and enhance together.

Part of the Forge omnichannel digital banking platform and its world-class product suite, the Forge Community is designed to keep you on the cutting edge of digital banking innovation long-term.
 

The Ecosystem

The Forge Community will be an integrated digital ecosystem where fintechs and Forge clients can design, build and benefit from each other’s innovations. Resources, information and tools will be shared among participants. By pooling our capabilities and resources together in this way we will:

/ Create economies of scale
/ Reduce the friction that slows down data exchange
/ Accelerate everyone’s time to market

All to ensure that our community’s common goal is realized – to revolutionize the way our customers bank online.

Ecosystem Image

Ecosystem Image

Components offered in the ecosystem are complementary to one another, providing a one-stop experience

An initial offering of core components which are highly desired or essential to the platform is provided by Central 1

Additional components will be provided by platform community (credit unions, banks, Fintechs, etc.)

Developing for the Forge Community

Getting Started – Software and Environments

Development Rights
It’s important to consider that only Backbase can provide rights to develop on the Backbase source code. However, anyone has the ability to develop Angular widgets and Java capabilities. These frameworks are free to download and learn. Today, without any investment, your organization can:
a. Develop for the Forge platform
b. Add components to the Forge Community
c. See academy.backbase.com to learn how
Access to Software
Only Backbase can provide software to run locally on your development team’s machines (CXP, DBS, and other required components can be accessed via repo.backbase.com).
Similarly, only Backbase can provide access to sample code via start.backbase.com or community.backbase.com.
Access to Environment
Backbase can provide software to run a Sandbox environment on a local workstation. For contributors who want to build an advanced internal development capability, we recommend that you go through the Backbase certification process. This will provide you with a development sandbox, the required software, access to sample code, and the support your team will need to become a full development shop.
For more information regarding the certification process and access to sample code please visit academy.backbase.com
The Contributors Journey
Want a learn more about contributing to the Forge Community?
Let us walk you through the process from start to finish.

Forge Marketplace Developer Requirements

Central 1 continues to refine the set of minimum requirements needed to contribute to the Forge Marketplace. Broadly put, as long as contributors meet the Backbase standards, Canadian regulatory requirements, and Central 1 code structure guidelines then your creation will qualify for the Forge Marketplace.
Widgets can be developed in any programming language. However, Angular 8 is the current preferred framework.

UX widgets must be developed in line with the Backbase Design System (https://designsystem.backbase.com). Furthermore, the use of specific client brands (fonts, logos, colours) which cannot be configured is not permitted.

Widgets that store or access tenant data must support multitenancy. Furthermore, they must not be used to export Personal Identifiable Information (PII) and must meet the Payment Card Industry Data Security Standard (PCI DSS). Any data access must do so via declared Capability Data Contracts.

All contributions to the Forge Community must pass through Central 1 code review, security scans, performance and functional testing. They must also meet the Central 1 structure guidelines so that they can be deployed through the Forge pipeline.

Contributions should, at a minimum, follow the Backbase development standards. Given these standards differ by use case, Central 1 recommends developers complete the relevant Backbase Trails for specific direction.

All contributions to the Forge Community must meet the Web Content Accessibility Guidelines (WCAG) 2.0 AA standards (https://www.w3.org/WAI/tutorials).

All contributions to the Forge Community must be built in such a way that is containerized within a single widget. Adverse effects on other widgets (both functional and cosmetic) will not be permitted.

Why Develop for the Forge Marketplace?

  1. Generate additional revenue or simply recover development costs for components shared through the Forge Marketplace
  2. With a shared innovation approach, the Forge platform and ecosystem can maintain pace with major fintechs as well as customer expectations for enhanced digital experiences
  3. Developers will benefit from feedback and knowledge sharing among developers across the Canadian credit union and banking system
  4. Providing components through the Forge Marketplace is consistent with the philosophy of fostering cooperation among Central 1 clients in the interests of building a more robust offering for all end users

Want to know more about Forge Community?

Talk to us
Your Relationship Manager is your primary point of contact if you’re interested in starting development or learning more about the Forge Community. If you’re new to Central 1, please email us.

Let's Chat

Read the whitepaper
Learn more about the Forge Community as a whole, the art of possible, our catalogue offering, and governance.

Want to talk to a real live person about your Forge questions? We get it!

logged in  
reset cookies