Hello

Please can you clarify the following questions for me.

Scenario: Rapid deployment of small sites to independent clients who have no connection to each other.

Can you confirm that it is possible to configure individual sites so client A has no access to client B's website?

When creating a new site from backend, can each new site:
1) have preconfigured pages containing default content and associated menus (eg Menu1->Page1, Menu2->Page2, Menu3->Page3 etc)
1a) Can this content be dependant on site type (eg site type A has associated content version A, type B has Content B etc)?
2) Select a style from a list of say 20 style templates?
3) Select which components are to be used on the new site. eg if a new side needs to have online forms.

For each site created, can the client
1) Log on and edit from the front end? (My preference is not to provide backend access)
2) Pick a different style himself
3) Upload images and pdfs to a directory unique to their website (using something like JCE File Manager or whatever)

Misc
Can each site have it's own Google analytics code?

Look forward to hearing from you
Iain

The concept of JMS is based on the sharing.
- Sharing of the same Joomla application code (PHP code)
- Sharing of the content of a limited number of extensions that you can retrieve at
www.jms2win.com/en/list-of-extensions?vi...id=269&Itemid=53

0) As the content of each website is mainly stored in the DB then yes, the content of each website can be independent between Client A and Client B

1) Yes you can create a "template website" that will be used to create the client website.
When you replicate a website, this is like a backup/restore with the difference that the files and folders on the disk are shared.
It is also possible to configure JMS to have a specific /images directory and specific /templates directory.
See tutorial video CP-05
www.jms2win.com/en/tutorial#jms12x-CP-05

2) If you create a template website that contain the 20 joomla templates then the client will be able to change and select the template that he want.

3) As you replicate the website, all the component are pre-installed.
If you want later add an extension, it must be previously installed in the master.
You also have the JMS tools that can help you doing the installation of an extension on a slave site or use the standard Joomla extension manager to re-install the extension or discover the existing one on the disk.

For the front-end,
1) Up to you to setup the ACL as you would do with a standalone joomla.
This is not JMS related.

2) If this feature is present in standard Joomla without back-end access then yes.
JMS does not change anything in the Joomla processing.

3) Yes you can configure Joomla media manger option to have specific path for the images.
See also the Tutorial Video CP-05
For PDF, this may depends on 3rd parties extensions. Some hardcode the path where the files is uploaded and could be shared on the disks. Other extension didn't do that.
So this is extension dependent and not JMS dependent.

4) Yes each site can have their own Google Analytic code.
We also have developed a free "Multisites Google Analytics" that may help when you share the whole website content between differnt domains and that you also want to have different statistics depending on the domain.
www.jms2win.com/en/component/docman/doc_...tes-google-analytics

Thanks for the info.

Can I ask about Style templates (not JMS Site templates). When you create a new website are the templates copied across to the new site or are they "read" from the original installation? ie do I end up with a separate template for each site? If I changed the master style - would that change be reflected right across all websites using that style or would I have to update all of instances?

This depends on the JMS Template rule and if you have asked to share (special copy) or use a copy of the /templates directory.

When you share them then any change in one place is automatically reflected in the other sites.
When you did a copy then you don't have any other site affected.

To cross-check, verify if you have a link or a physical directory on the /templates or in their subdirectories.