This package is the first one in the set of packages and probably the only one that needs to implement Sites model and add ''site_id'' to every table to allow MultiSite usage of this package in projects. There should be a default site with a data migration of it to the database.
I need to also think through an implementation of allowing pages & the post models to be added to multiple sites or for simplicity sake to just disallow that. I can think of quite a few instances where I would want the same page of each of the websites in the project.
We'll allow the project to handle the MultiSite routing code and can do that later and provide the necessary steps in a ReadMe file but shouldn't overcomplicate the code in this package for the many single site projects that use it.
This package is the first one in the set of packages and probably the only one that needs to implement Sites model and add ''site_id'' to every table to allow MultiSite usage of this package in projects. There should be a default site with a data migration of it to the database.
I need to also think through an implementation of allowing pages & the post models to be added to multiple sites or for simplicity sake to just disallow that. I can think of quite a few instances where I would want the same page of each of the websites in the project.
We'll allow the project to handle the MultiSite routing code and can do that later and provide the necessary steps in a ReadMe file but shouldn't overcomplicate the code in this package for the many single site projects that use it.