Split the wcc-contentful GEM into two parts: data access and the "Webpage CMS" features.
Data Access:
credentialing into Contentful.
making data requests.
caching data locally.
Webpage CMS:
Any idea related to a Page, Section, or web page UI elements (i.e. menus, buttons)
Any of the HTML DOM that represents these concepts.
Controllers that implements the server side of a sections behavior (e.g. sending an email from a Contact Us section)
Page URL resolution, redirection, and handling preview (controller) should be in a gem
In developing these two gems, it would make since for an interface to live between them. This potentially would allow a different data source to replace Contentful and not have to change the entire gem.
We agreed that these two gems would be versioned together, likely living together in the same git repository.
The scope of this card does NOT include making something work that doesn't currently. The items listed here are only useful in that they describe the functional allocation (which functions go where) in splitting up the functionality.
Split the wcc-contentful GEM into two parts: data access and the "Webpage CMS" features.
Data Access:
Webpage CMS:
In developing these two gems, it would make since for an interface to live between them. This potentially would allow a different data source to replace Contentful and not have to change the entire gem.
We agreed that these two gems would be versioned together, likely living together in the same git repository.
The scope of this card does NOT include making something work that doesn't currently. The items listed here are only useful in that they describe the functional allocation (which functions go where) in splitting up the functionality.