Hi, I am customising store locator page in SCA 2019.2. I wanted to confirm the feasibility of using extensibility api for this customisation. Because there is no component for store locator. I'll have to use the layout component. Should I proceed with extensibility api or use the conventional extension method used in pre aconcagua versions.

Generally speaking, you should use the extensibility API as much as possible

So I should customise store locator using layout component? Also what if I want to change a function in SCA source?

So I should customise store locator using layout component?

Yes, why not?

Also what if I want to change a function in SCA source?

Then just change it using non-API methods.

If we want to create a plugin for store locator, then the non api methods can cause a problem in exporting the extension to another project, right?

Well yes, this is the nature of the extensibility API versus 'traditional' customisation methods. The API ensures a high level of interoperability; traditional methods do not

We want this extension to be distributable, so we definitely cannot use the traditional method. I was thinking of removing the source store locator from distro and then using the same code and our customisations to create an extension using extensibility api. What do you suggest?

Er, well that could be a violation of our copyright as you would be copying and distributing our source code, so I would probably get a lawyer to check whether that's OK first. Second of all, I don't see how you could apply that to, say, a SuiteCommerce site, which does not allow for the modification of distro.json.

Okay I'll think of some other workaround that does not violate copyrights