These are options which we provide as a part of larger projects which we develop, rather than as off-the-shelf packages. These are not extensions to base TYPO3 - they are simply ways of configuring it.

Shared TYPO3 Installations 

Shared TYPO3 installations give you access to a web site which appears to the outside world to be independent, but which is in fact part of a larger TYPO3 installation which hosts a number of web sites. The web sites share a common pool of extensions, though there is no direct communication between sites.

Who is it for?

This option would mainly be useful if you

• have a managed server which normally has only a single domain available to it
• have a server or Virtual Server which does not make use of control panel software such as Plesk, and therefore has to be configured manually for each domain
• Want to resell web sites based on a limited range of customisable layouts

Availability

We do not supply this as a standard option, since we manage sites through Plesk, which offers users far more facilities than a simple web site.

Common TYPO3 installation

Common TYPO3 gives a number of organisations independent sites which are actually part of a single TYPO3 installation - much like the shared TYPO3 Installation described above.

In addition the web sites are able share a common pool of information, generally in the form of shared content elements, which can be incorporated transparently within their own sites - the look and feel of the common elements on a given site is dependent on the local css formatting, and they can format output differently by modifying extension parameters and templates locally.

The sub-sites may access only to their part of the whole site, while a central Administrator might have access to the whole structure. Alternatively, each participating organisation might have access to its own site, plus a portion of the shared part that was assigned to it, enabling a collective development effort.

Who is it for?

Any group of organisations which are independent or quasi-independent, while having a body of information in common.

For example:

• A charity with central headquarters and branches around the country.
  The HQ and the branches can each have their own website, and the material relating to the aims and objectives of the organisation, which would more commonly exist only on the HQ site would be displayed by each of the branches using the same content databases, while being displayed through the templates and sites belonging to each of the branches.
• Council Estates involved in Housing transfer.
  Each estate can have its own site, while sharing a common database which explains the process at a more general level.
• Support groups for the same medical condition can work together on a database relating to the condition, which they can expand much more rapidly than otherwise by apportioning research among themselves.
  Local matters can be managed on the individual sites, which also have a view of the common database, which appears to be part of the local website in each case.

Deployment

This sort of topology usually makes most sense if deployed on a server or virtual server which is dedicated to the task

Availability

Please contact us if you might be interested in this kind of solution.

TYPO3 and Glyphgate

Glyphgate requires extensive customisation of the server environment, and in practice requires a dedicated server. This can be provided either by renting web space from the Glyphgate developers, or other ISPs who provide Glyphgate licenses.

Availability

We would be happy to customise a dedicated server for you, and to provide a Glyphgate server ourselves, if their appears to be sufficient demand.

Please contact us if you are interested.