tag:help-archives.hannonhill.com,2010-02-09:/discussions/how-do-i/21321-include-page-from-another-siteCascade CMS: Discussion 2018-10-18T20:37:49Ztag:help-archives.hannonhill.com,2010-02-09:Comment/391228712016-02-09T13:28:35Z2016-02-09T13:28:35ZInclude page from another site<div><p>Hi,</p>
<p>To clarify, you would like to add a checkbox to your news
articles that would dictate if the article should be included
within other Sites, or only the Site containing the
<strong>news</strong> folder? If so, you can accomplish this
by:</p>
<ul>
<li>Using either a Content Type Index Block, or the <a href="http://www.hannonhill.com/kb/Script-Formats/#locator-tool">Query
API</a>, to pull in the data for all of the news</li>
<li>Create a Format that loops over the articles looking for the
ones that have the checkbox checked, and if so display it</li>
</ul>
<p>If you choose to go the Index Block route, you would attach both
the block and format to the pages within your other Sites. If you
go the Query API route, you would attach just the Format to the
pages within your other Sites; you will also need to make sure you
use <code>searchAcrossAllSites()</code> when building the query to
ensure your news are picked up from the other Sites.</p>
<p>Please let me know if you have any questions.</p>
<p>Thanks!</p></div>Ryan Griffithtag:help-archives.hannonhill.com,2010-02-09:Comment/391228712016-02-09T13:37:26Z2016-02-09T13:37:26ZInclude page from another site<div><p>Your clarification is exactly correct.</p>
<p>Just to make sure I'm understanding this correctly, by using
either method above we could then create our news on site1.com. Our
users could go to site1.com/news-article-example.html and if we
used the above methods we could also go to
site2.com/news-article-example.html as well? Would our content
folks only need to publish the news article on site1 & do
nothing else?</p></div>webteamtag:help-archives.hannonhill.com,2010-02-09:Comment/391228712016-02-09T13:53:19Z2016-02-09T13:53:19ZInclude page from another site<div><p>Hi,</p>
<p>My apologies for the confusion. With the setup I described, you
would have one central location for news (**site1.com**) and your
other sites (**site2.com**) would aggregate and link those articles
located in <strong>site1.com</strong>.</p>
<p>Please let me know if you have any questions.</p>
<p>Thanks!</p></div>Ryan Griffithtag:help-archives.hannonhill.com,2010-02-09:Comment/391228712016-02-09T14:01:34Z2016-02-09T14:01:34ZInclude page from another site<div><p>I should have specified my question more clear. So if I
understand correctly, using just Cascade's features we can't have
the same page live on site1.com & site2.com? The link on
site2.com would just redirect them to the page on site1.com?</p>
<p>I have other ways of accomplishing this using XML feeds &
either JS or server side code. I was just curious if Cascade had a
better method.</p></div>webteamtag:help-archives.hannonhill.com,2010-02-09:Comment/391228712016-02-09T14:17:05Z2016-02-09T14:17:05ZInclude page from another site<div><p>Hi,</p>
<p>Correct, there would be no out-of-the-box way to create a clone
of a page within <strong>site1.com</strong> with the page's data,
but in the design/layout of <strong>site2.com</strong>.</p>
<p>The only ways I can think of accomplishing this would be to:</p>
<ul>
<li>Create a corresponding page within <strong>site2.com</strong>,
but that page's data definition has a chooser in which the original
article is selected. You would have a Format that uses the chosen
page and outputs its data</li>
<li>Use Web Services to read the articles from
<strong>site1.com</strong> and create a corresponding page within
<strong>site2.com</strong>.</li>
</ul>
<p>Either method could possibly result in incorrect content in the
other sites unless you regularly "re-sync" the pages to ensure the
clones have any updated content.</p>
<p>If you don't mind me asking, could you explain your use case a
bit more for having the same page in two different sites?
Generally, clients opt for a central news location for consistency
in message and branding.</p>
<p>Thanks!</p></div>Ryan Griffithtag:help-archives.hannonhill.com,2010-02-09:Comment/391228712016-02-09T14:38:04Z2016-02-09T14:38:04ZInclude page from another site<div><p>We have two main companies, each with their own website,
branding & identity. We also have additional websites for our
retirees, for members of our cooperative, an intranet for our
internal employees. As well as digital signage across our locations
& other sources I'm probably forgetting where we want our news
to display. We are trying to slowly move to the idea of COPE
(Create Once, Publish Everywhere). The main idea here is to allow
our content writers to create the content, specify what type of
content it is & who might be interested in it. Then any other
source, be it a website, an app, digital signage or anything else,
can pull relevant content & display it in its own format.</p>
<p>The original posted question is a baby step towards this
philosophy.</p></div>webteamtag:help-archives.hannonhill.com,2010-02-09:Comment/391228712016-02-09T14:45:54Z2016-02-09T14:45:54ZInclude page from another site<div><p>Ah, that makes sense then.</p>
<p>In that case, publishing to a single data source like an
XML/JSON file or database might be the most flexible. Or, perhaps a
combination of solutions depending on the use case.</p>
<p>For example, depending on how your signage works, you could end
up having a "signage" output that has a specific look and publishes
to a specific location. Or if you signage can pull in an XML file,
you could go with what you mentioned previously.</p>
<p>Please let me know if you have any questions.</p>
<p>Thanks!</p></div>Ryan Griffithtag:help-archives.hannonhill.com,2010-02-09:Comment/391228712016-02-09T14:49:27Z2016-02-09T14:49:27ZInclude page from another site<div><p>Will do. Thank you as always for your awesome support!</p></div>webteam