Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Segregate individual sites #271

Open
ktbartholomew opened this issue Jan 7, 2016 · 1 comment
Open

Segregate individual sites #271

ktbartholomew opened this issue Jan 7, 2016 · 1 comment

Comments

@ktbartholomew
Copy link
Contributor

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.

@ktbartholomew
Copy link
Contributor Author

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.

https://github.com/deconst/deconst-control

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant