sitewide api_key

[missinglink]

In the case where the component is rolled out widely across a medium/large website, the HTML code may exist in multiple views across the codebase.

Changing the API key in this scenario becomes a bit of a chore.

Would it be possible to define the api_key parameter once per installation and then omit the api_key attribute when embedding the component?

[mxlje]

I think we should keep this in mind for a future release but not have it at launch.

[missinglink]

As discussed today, the immediate solution for this is to use the includes/templates/dynamic code generation tooling available from the web framework to have a single place in the codebase which can implement defaults and be a single place to make global changes.