Below is a sample of Content Management Systems we’ve worked with and our ability to automatically get our content on them.
Import Directly – Do we have the ability to integrate directly into said CMS with proper credentials.
Main Domain – Based on the server architecture required by said CMS is it likely we can integrate on the main domain.
| CMS | Import Directly | Main Domain | Notes |
| BlogEngine | Yes | Yes | In House Software (UNSUPPORTED) |
| DotNetNuke 7+ | Yes | Yes | In House Software |
| Drupal 6 | Yes | Yes | In House Software (UNSUPPORTED) |
| Drupal 7 | Yes | Yes | In House Software |
| Drupal 8 | Yes | Yes | In House Software |
| Hubspot | Yes* | Yes | Requires API |
| Joomla 3.0 | Yes | Yes | In House Software |
| Joomla 2.5 | Yes | Yes | In House Software (article ONLY) |
| Joomla 1.5 | Yes | Yes | In House Software (UNSUPPORTED) |
| Magento | No | Yes | Can use another CMS |
| Sitefinity 8 | No | No | Proprietary |
| Sitefinity 7 | No | No | Proprietary |
| Sitefinity 6 | No | No | Proprietary |
| WordPress | Yes | Yes | In House Software |
In House Software – We have written software which will integrate our services directly with the CMS in question. We will gladly provide the software to our clients.
Use another CMS – We do not have software specific to this CMS so in order to integrate we would recommend installing a different CMS from the above list.
Proprietary – This CMS does not work with external scripts so an integration on the server is not possible. We recommend creating a subdomain which will point to a seperate server to house the integration.
Requires API – This CMS offers an API which we have successfully integrated with in the past. The API must be accessible to integrate.
In House Software (depreciated) – We have written software which will integrate our services directly with the CMS in question. The software will not receive future updates. We will still provide the software to our clients.