I'm currently exploring Adobe Target and considering setting up a sophisticated and customizable approval workflow within the platform. The envisioned workflow would involve multiple levels of approval, perhaps 2-3, before any activity is ready to be published.

Something you do on organization you are supporting? @Jagadeesh_Prakash 

Is this forking wcm-core a practice you think Adobe is evangelizing and telling organizations to do? Is there anybody from Adobe Tech team supports such?

Please see here @Mohit_KBansal 

Hello @Mohit_KBansal please see my reply to @Jagadeesh_Prakash 

But what if I would like to create my organization core components based on how wcm-core was built? Is it possible? Or should I better say, is it a good practice to fork wcm-core, rename it as organization-core-components and build new components from there.

Hello Adobe friends,   Is it a practice to fork aem-wcm-core-components from github to be the organization’s core component? Therefore, it will be at the same level as wcm-core under /apps/core?

But then again, is referencing from maven dependency a best practice, or should we extend the org-core components to another AEM project as a supertype/resourcetype?

Hello Adobe friends,   I am working on a new project of mine. I am contemplating creating an organization's core components based on WCM Core Components and adding an organization branding and style system. Now several questions in mind I'd like to raise:   Where should the core components be locate...

Can we have two launch scripts running in one web application? Will it not have issues on JS/backend calls?How about the performance and best practices?