Two Snaps - One Athos

[korgon]

As we have discussed this fork is to become the foundation for Athos front end integrations. To that end we will need to remove all references to Searchspring in this repository.

Some key things that need to be changed, but maybe not directly replaced with Athos, would be things that we might want to change to use the word "snap". For example, the searchspring-preview used in branch overrides, this could be changed to athos-preview (needs to be decided). A similar change would be for searchspring-context attribute used in getContext() calls - I think we would likely want to preserve this (to make migrations easier), we would add a new supported context identifier athos-context perhaps.

Another example of a change needed would be for when we are looking at the script src attribute we have some regex that likely includes 'snapui.searchspring.io' - this needs to be modified to support 'snapui.athoscommerce.io'.

Class name prefix (and all associated styles) will stay as ss_.

Cookies and storage (local and session) will need to be renamed, likely from ss -> athos (eg. ssSessionId -> athosSessionId). For tracking cookies controlled by beacon.js - these will need to have support for backwards compatibility and the renaming and functionality for that is a separate task in that repository.

Documentation will need to be adjusted removing all references of Searchspring.

[adriamurphy]

@korgon I was looking at getConext today and will the change to use athos-context only be available in 1.0? I assume so because that's where this issue is. But just curious for our internal docs and scaffolds.

[korgon]

@adriamurphy - yea only in 1.0.

Any site on Athos should use or be moved to 1.0 (to be known as Athos Snap vs. Searchspring Snap).