This is second post of series on Adobe Project Firefly, You can read about the introduction and why you should consider using Adobe Project Firefly.
Project firefly involves lot of moving parts, as a primer to get started it makes sense to spend some time and understand the core fundamentals & stack of products and services available.
In this post we’ll go over
- Getting Access to Adobe Project Firefly
- Core components of the Project firefly framework
- Architecture Overview
- Security Overview
- Integration with Adobe Experience Cloud
Getting Access to Adobe Project Firefly
Adobe Project firefly is still in developer preview and you can get access by filling in the form, you can read more about it HERE
Core components of Adobe Project Firefly
Here’s a look at the core components of project firefly
- Adobe I/O CLI
- Adobe Experience Cloud Product Libraries
- CI/CD Pipeline
Adobe Project Firefly Architecture
This video from Adobe project firefly teams sums up the architecture of firefly applications. .
Project Firefly Security Overview
This video talks in brief about Access control for apps and out of box features to build secure application with firefly
Integration with Adobe Experience Cloud
Adobe Experience Cloud is a single gateway to all your existing apps today, With Project firefly you can leverage this to provide unified experience to users and manage all your apps within the experience cloud shell.
Any products/apps built will have access to and interact with experience cloud features such as topbar, menu, alerts and notification.
For detailed guide refer to this page
Next Post in this series
The next post will cover set up and getting started with Adobe Project Firefly. Stay tuned! .
1 comment