Project Firefly is a complete framework that enables enterprise developers to build and deploy custom web applications that extend Adobe Experience Cloud solutions and run on Adobe infrastructure. It uses modern web technologies — like the Jamstack, serverless computing, Node, and React — and supports development best practices, such as continuous integration (CI) and delivery (CD).
In this article, we’ll talk about how you can leverage and set up projects and workspaces to best supplement your development needs.
For those of you who prefer to see this in video format
The Project Firefly team shared a short presentation about projects and workspaces and how to use customizations to help your team work better together. These webinars are hosted biweekly, find out about our next event here.
Projects in the Adobe Developer Console
To quote the documentation — “All development work in the Adobe Developer Console is done as part of a project.” Projects allow you to securely manage and organize credentials and integrations within your organization. Projects always live within the context of an org — each project is only visible to the users within that organization with proper permission. You can learn more about access management for developers in managing developers documentation.
As you can see, each project can contain API integrations, Event registrations, as well as Runtime. You can add and remove these individual integrations as needed. For Project Firefly, we use templated projects to help developers get set up quickly and easily.
Projects and workspaces for Project Firefly
Image for post
These templated Firefly projects include multiple workspaces, which can be thought of as individual working environments for each developer on the project that can be configured to fit your unique needs. Instead of directly in the projects, within Firefly Projects, you will use workspaces to connect services and get the credential details needed to connect to Adobe APIs, Events, and Runtime credentials.