Does google groups have a maximum post limit
Ok, i’m going to rattle some of this off real quick. I hope it makes sense… getting the terminology right has been tough enough… and i’m still not sold on it.
We have 3 iterations in our own multi-tenant cms, and it works really well, we like it a lot, but obviously, you have to grow and change over time.
The last version we have has been modified from its base, and supports multi deployments (websites) per site (organization)… allowing a website, a mobile site, etc for a given Master Site / Organization. More below.
Right now, we have a serious set of upgrades we wanted to work into the system, but with all of the theming etc, it seems like a perfect time to re-evaluate how we do everything.
We decided to re-eval platforms, and Adrian Moreno and a few others have guided us to ColdBox.
The structure and conventions should make it easier for us to add more developers (we’re pretty busy but before we add more devs we want to define our workflow etc etc), and this should help us be more efficient, so ColdBox with its documentation and community is a good match.
We looked at contentbox, watched some of the videos etc, installed it, but without multi-tenant it would be tough to work around given our use of our own multi-tenant for several years now.
Some of the key points we enjoy with our current system.
A centralized location to maintain all the sites
Super Admin can manage sites / core config while logged into any of the sites
When you add a website it creates a datastore for that site (think of it as a company/organization datastore)
All sites share the same db, for ease to roll out updates etc.
If you want to add additional websites (deployments) for a datastore you can.
For example… we have one organization, a photographer, 1 datastore, 1 folder structure for assets, but we are adding a wedding website, a portraits website, a sports website, a mobile site, and an app, and they all pull from one data store, 1 folder structure. the only difference in the sites it the navigational structure + layout etc. When you add a blog widget, it pulls from one location, if they want to have a customer login, its shared across sites, and all their albums are shared across etc, so they dont need to update each sites’ albums etc, its all built into one “Organization” Datastore.
Modules are basically the model and admin features to maintain the modules, and then you can use widgets to use the models in your views.
Modules and widgets are configurable and you can select which organizations have access to what.
Widgets are created for platforms… so you have a blog recent posts widget… it might be desktop only, it might be desktop / email / fb / mobile
A lot of widgets are designed especially for mobile, like photo gallery widgets for mobile imitate native apps, like photoswipe.js
Because the platform has limitations, widgets are developed to focus the model to best fit that platform.
Facebook platform has limitations on how those widget works, and Email widgets are limited even more (limited css and js etc)… so you can throw content from your models into all sorts of platforms, just by using a widget specific to that platform.
The beauty of the way our system is setup, is its a centralized system, we can upgrade site functionality by checking or unchecking boxes.
Users can be shared across multiple sites,
Database updates are instant for all sites in the multi-tenant.
We are adding iis integration so when you add a site, it shells it out, configures all the mappings it needs, adds bindings… so a lower level staff member can install a site and have it ready to add content with only a few clicks in our admin, no need to remote into a box and know how to use iis or apache etc etc.
We’re adding dns automation to setup live dns binding (with supported api’s of course) so when a new site is added, we can setup a new subdomain without going to a separate system or remoting into a box.
We’re adding redirection for non canonicalized domains, so it can force your sub domains to your preferred subdomain… this can be done by just adding a list of domains (and subs) to a website, and selecting one as the main/default and the others get re-written for you.
We’re even considering a subscription based upsell system for those premium modules, so instead of us checking a box to give a site/org access to a module or a premium widget, they the end user or site manager can add it themselves, and pay a setup fee / and or monthly fee where appropriate.
Its our own system, so we have the power to do what we want, we have basically built a business management tool, so our accounting people can login and disable a site if they are not in good standing (although i’m in favor of automating it all of course), if they need to reset a password, they dont need to know the url of the site, and the username and password of that admin, to get in and reset it etc, there is a centralized management tool.
Of course we could built tools to talk to several databases, and manage items,
With one centralized management tool, we can build phone tablet and even desktop apps (thinking about html 5 with air etc) so we can manage everything on the go.
We’ve looked at some of the domain reseller api’s too, so users can renew or signup their domains in their admin, or our staff can… there are lots of things that we can do to make our business better, more efficient, and at the same time give our customer lots of powerful tools at their fingertips.
Of course, this model would allow us to have customers manage whatever tool or service we offer, not just websites. We could have people sign up at a centralized site like mymadeupdomainnametools.com and sign up a crm service, email marketing tool, facebook helper tool, or other non website related services we could offer too… and of course, by having a centralized model, you can upsell and cross sell your existing clients. We have a decent number of clients, but it would be nice to let them know what we’re doing without being in their face, making relevant suggestions as they go.
Sorry for the long post, but these are some of the ideas we’re working with… obviously its a big broad view of what we do and where we’re headed… but I wanted to give a list of functions and why, because you can do single sites, but for lots of reasons we have gone to this multi-tenant and we like the way it allows us to function.
The funny thing, the reason i came back to look at content box was because i was going to setup a wiki to track my ideas and document as we develop our new version.
I there are several people looking for the same type of thing… we could pool ideas, maybe resources, since we’re new to Coldbox too, it would be great to get some senior ColdBox guidance too.
Anyways, feel free to hit me up here, twitter, or send me a personal email.
Would be happy to compare notes and chit chat.
I’m trying to get more community involved.
Have a great day.