Adobe Developer Console project creation

When creating an AEM Content Fragment Console extension, first we need to start off at the Adobe Developer Console and create a new project to associate our extension with. So for this we head over to developer.adobe.com.

So we’ll click the console button to open the console. And if you’re part of multiple Adobe Orgs, make sure that you have selected the Adobe Org that your AEM environment that the extension will be added to exists in. Next we’ll head over to projects. And we’ll create a new project. And from here we’ll create it from a project template and select app builder. First we need to give our project a title and make sure you make the semantics since this is going to be how you identify the project later on in Adobe Developer Console that’s associated with your specific content fragment extension. The app name is simply a unique name for the app. You can change this or you can leave it as the auto-generated name itself. Workspaces are where the extension is deployed. So the production workspace should be self-explanatory. This is where the final build of the extension is deployed that will automatically be injected into AEM as a cloud service content fragment consoles. The stage workspace is typically used for development and testing. So development builds or release candidate builds can be deployed into the stage workspace for testing. And if you have larger more complex development workflows, you can always add new workspaces for each of your use cases. Lastly, keep the Adobe IO runtime checkbox checked if you are going to need an Adobe IO runtime action for this extension. Typically to do any meaningful work or interact with AEM itself from the extension, you’ll need an Adobe IO runtime action. So we’ll want to keep this checked most of the time. We can save our project. And now our project is created.