Client Activation Header/Footer Integration

Implementing a feed or packaged solution of a header and footer can cause numerous complications, both during implementation and in production. The list below is a set of criteria that will help both parties avoid many of the known issues related to this solution.

Any client provided feed must meet the below criteria. If it does not, Q4 will not be able to implement this solution.

Requirements:

1. Feeds or data shared by the client can only be implemented client-side (frontend solution).
2. The solution provided must not include; , , or tags.
3. A working example should be included as a link, or in the package provided with documentation.
4. CSS cannot contain any global styles or common class names that may affect the live site. If possible, all classes should be namespaced.
5. If additional fonts or font icons are being referenced but not included from a CDN, CORS must be enabled.
6. All URLs must be provided as an absolute path. This is including but not limited to; images, CSS, JavaScript and links.
7. Any required JavaScript should be provided as a standalone solution. If a framework, such as jQuery is being leveraged, this can be included as a separate file in the working example, but not bundled with the other required functionality.

Note: Changes made by the client to the original files may pass testing on other websites, but they could still break the feed Q4 is using on the website we developed. Please notify Q4 to assist with testing in all cases where an edit takes place.

Q4 can integrate your corporate header/footer feed, however the above requirements must be met in order to ensure a successful set up.