Add asset selector to core Franklin configuration

[mfrisbey]

The asset selector should be part of Franklin's core setup, meaning there shouldn't be special configuration required on the customer's end. We need to figure out what this looks like.

An initial thought is that the setup should only consist of adding the plugin (with very simple configurations) to a customer repository.

[tmathern]

An initial thought is that the setup should only consist of adding the plugin (with very simple configurations) to a customer repository. <= this will be made possible once we have a static URL hosted somewhere we'll be able to point to.

[sdmcraft]

I think for phase-1 , we can add documentation on this in the Franklin Site which list the steps to get this working. I have edit access on the Franklin site so can take a stab at it. @tmathern feel free to reassign this to me.

[tmathern]

Sounds good!

[sdmcraft]

Shared draft public doc for review https://main--helix-website--adobe.hlx.page/drafts/satyam/aem-assets-sidekick-extension

[mfrisbey]

Thinking out loud here, but what would your thoughts be on adding a new button to the sidekick:

(that's obviously just a mockup)

We could potentially control whether the button appears with a flag setting in the sidekick config (or maybe as a project setting in the UI):

{
  ...
  showAssets: true,
  ...
}

This might be more work, but IMO it has the following advantages:

• It feels more truly integrated into the sidekick.
• Customers aren't hard-coding the URL or palette definition, so we could have more control over updating those in the future from a central location.
• It's even simpler for customers to set up.

What are your thoughts @sdmcraft @tmathern @badvision?

[sdmcraft]

would your thoughts be on adding a new button to the sidekick:

My thoughts are aligned on making this natively available in sidekick. This was the original requirement in this ticket as well. This likely would require a sidekick enhancement that I logged here adobe/helix-sidekick-extension#517 .
I see the documentation approach as an interim option for phase-1 till we get the sidekick enhanced.