You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, each site shares a lot of files with all the others (e.g: config/content.json, Gruntfile.js). This lack of isolation makes working on individual sites kind of painful. The control repo should be organized to allow ALL configuration, content, and assets for a given site to be completely isolated from that of a different site. This may be by putting all the data for a site into a subfolder with the site's presented domain, or maybe even by creating "child control repos" that are actually NPM dependencies.
The text was updated successfully, but these errors were encountered:
Here's the direction I'm headed. Basically, I want to make the control repo a collection of npm packages. There's a lot of "plumbing" directly inside the presenter right now, and this will let us abstract a lot of into each site and just provide a consistent interface back to the presenter.
Currently, each site shares a lot of files with all the others (e.g:
config/content.json
,Gruntfile.js
). This lack of isolation makes working on individual sites kind of painful. The control repo should be organized to allow ALL configuration, content, and assets for a given site to be completely isolated from that of a different site. This may be by putting all the data for a site into a subfolder with the site's presented domain, or maybe even by creating "child control repos" that are actually NPM dependencies.The text was updated successfully, but these errors were encountered: