It’s too much trouble to recreate from scratch different templates, content etc and doing so doesn’t address the problem of keeping both sites up to date.
Here is what I do.
1. In CMSMS create a page with content type "Section" and marked it to not display in the menu, inactive and name it eg "External Includes". Not only does it prevent it showing in your CMSM front end, sitemaps, etc, it makes it easy to identify in your admin page list.
2. Create a page template with only '{process_pagedata}{content}' and call it "Content Only"
3. Create a sub-page of "External Includes" called "Header" (or whatever is relevant to the bit you want to include in the other site) and set the template as "Content Only" as per above.
4. Copy the relevant sections of the CMSMS template (or Global Content Block, page content, menu tag, etc) in to the content of the External Include sub-page.
In the template of the relevant 3rd party application, I call/include the CMSMS page, eg
Code: Select all
<?php include 'http://www.mysite.com/external-includes/stuff-to-go-on-the-other-site.html’ >
Also means that you only need to update CMSMS for the changes to be reflected in the other app.
When you're duplicating content, be careful to ensure that the pages are different so you wont get penalized by search engines. To get around this, when I'm using a module I create different module templates. Same data, one data-entry, different output.
Have fun with it.
Psy