-
Notifications
You must be signed in to change notification settings - Fork 10
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
26 changed files
with
86 additions
and
65 deletions.
There are no files selected for viewing
6 changes: 0 additions & 6 deletions
6
...gments/content/Sites/CaaS/Germany/English/Options/Settings/Pagegrid/Placements/footer.xml
This file was deleted.
Oops, something went wrong.
6 changes: 0 additions & 6 deletions
6
...gments/content/Sites/CaaS/Germany/English/Options/Settings/Pagegrid/Placements/header.xml
This file was deleted.
Oops, something went wrong.
6 changes: 0 additions & 6 deletions
6
...ragments/content/Sites/CaaS/Germany/English/Options/Settings/Pagegrid/Placements/main.xml
This file was deleted.
Oops, something went wrong.
6 changes: 0 additions & 6 deletions
6
test-data/react-fragments/content/Sites/CaaS/Germany/English/_folderProperties.xml
This file was deleted.
Oops, something went wrong.
File renamed without changes
2 changes: 1 addition & 1 deletion
2
...ermany/English/Editorial/Images/Globe.xml → ...ermany/English/Editorial/Images/Globe.xml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes
2 changes: 1 addition & 1 deletion
2
...ny/English/Editorial/Images/Hackathon.xml → ...ny/English/Editorial/Images/Hackathon.xml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes
2 changes: 1 addition & 1 deletion
2
...Germany/English/Editorial/Images/Lego.xml → ...Germany/English/Editorial/Images/Lego.xml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes
2 changes: 1 addition & 1 deletion
2
...ermany/English/Editorial/Images/Scrum.xml → ...ermany/English/Editorial/Images/Scrum.xml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
21 changes: 21 additions & 0 deletions
21
...ts/content/Sites/CaaSsiopeia/Germany/English/Editorial/Products/CaaS/CoreMedia%20CaaS.xml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,21 @@ | ||
| <?xml version="1.0" encoding="UTF-8" ?> | ||
| <CMArticle folder="/Sites/CaaSsiopeia/Germany/English/Editorial/Products/CaaS" name="CoreMedia CaaS" xmlns:cmexport="http://www.coremedia.com/2012/cmexport"> | ||
| <locale>en-DE</locale> | ||
| <master/> | ||
| <viewtype/> | ||
| <linkedSettings/> | ||
| <resourceBundles2/> | ||
| <segment></segment> | ||
| <title>CoreMedia Content as a Service (CaaS)</title> | ||
| <htmlTitle></htmlTitle> | ||
| <keywords></keywords> | ||
| <htmlDescription></htmlDescription> | ||
| <subjectTaxonomy/> | ||
| <locationTaxonomy/> | ||
| <contexts/> | ||
| <teaserTitle>CoreMedia CaaS</teaserTitle> | ||
| <teaserText grammarName="coremedia-richtext-1.0"><div xmlns="http://www.coremedia.com/2003/richtext-1.0" xmlns:xlink="http://www.w3.org/1999/xlink"><p>Using the Headless API you can generate ready-to-go HTML content fragments or dynamic Javascript modules. You can then easily insert these fragments into any webpage or single-page application. Use these fragments to seamlessly integrate, reuse, syndicate or publish your content from your CoreMedia CMS anywhere.</p></div></teaserText> | ||
| <detailText grammarName="coremedia-richtext-1.0"><div xmlns="http://www.coremedia.com/2003/richtext-1.0" xmlns:xlink="http://www.w3.org/1999/xlink"><p>CoreMedia is a Content Management System (CMS) which can manage your content from creation straight through to rendering. Our Content Application Engine (CAE) provides tools and a framework with which you can easily design a beautiful, consistent and fully-functional user experience.</p><p>The components of the CoreMedia system works gracefully together as an isolated system, but it is also flexible enough to be a small but crucial component in a larger ecosystem. This larger system can include commerce systems, brick-and-mortar backend systems, marketing data, user management and many more kinds of sub-systems.</p><p>One way to achieve this flexibility is to make content from our CMS available for another system, leaving you full freedom to design and render your content using the framework of your choice. We affectionately call this service the "Headless API".</p><p>Using the Headless API you can generate ready-to-go HTML content fragments or dynamic Javascript modules. You can then easily insert these fragments into any webpage or single-page application. Use these fragments to seamlessly integrate, reuse, syndicate or publish your content from your CoreMedia CMS anywhere.</p><p><br/></p><p><img alt="" class="float--left" xlink:actuate="onLoad" xlink:show="embed" xlink:type="simple" xlink:href="coremedia:///cap/resources/../../Images/Scrum.xml#data" cmexport:path="/Sites/CaaSsiopeia/Germany/English/Editorial/Images/Scrum"/></p><p class="p--heading-2">How does it work?</p><p>The Headless API defines a simple REST API to access content from the CoreMedia repository. On the server side the content is transformed via GraphQL queries before being returned to the client as JSON reponse. On the client side, simply parse the JSON response and process it as you please.</p><p>You can customize the GraphQL queries to tailor the returned JSON to your application's needs.</p><p>The first step is to define a schema, which maps from the content properties in the repository scheme to the attributes that you would like to extract. This can be done manually or with the help of a schema generator.</p><p>Then you define a set of GraphQL queries which will be matched against the schema.</p><p>The schema and query set are either deployed alongside the headless server or installed in the CoreMedia repository. The headless server can be started either by Spring Boot or as a Tomcat webapp.</p><p>On the client side, simply request the service's URLs and process the JSON response with whatever technology you prefer.</p><p><br/></p><p class="p--heading-2">Resources</p><p>Interested in a deeper understanding of CaaS in CoreMedia? See what we’ve cooked up for you in our CoreMedia Labs:</p><p><strong>Github project</strong>: <a xlink:show="new" xlink:href="https://github.com/CoreMedia/coremedia-headless-server" xlink:type="simple">Headless Server</a> as source code, plus a <a xlink:show="new" xlink:href="https://github.com/CoreMedia/coremedia-headless-client-react" xlink:type="simple">React client</a> as an example</p><p><strong>Technical wiki</strong>: Documentation on installing and customizing the <a xlink:show="new" xlink:href="https://github.com/CoreMedia/coremedia-headless-server/wiki" xlink:type="simple">Headless Server</a>, plus documentation on the example <a xlink:show="new" xlink:href="https://github.com/CoreMedia/coremedia-headless-client-react/wiki" xlink:type="simple">React client</a></p></div></detailText> | ||
| <pictures><link href="../../Images/Lego.xml" path="/Sites/CaaSsiopeia/Germany/English/Editorial/Images/Lego"/></pictures> | ||
| <related/> | ||
| </CMArticle> |
8 changes: 4 additions & 4 deletions
8
.../English/Navigation/CaaS%20%5BSite%5D.xml → .../English/Navigation/CaaS%20%5BSite%5D.xml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,13 +1,13 @@ | ||
| <?xml version="1.0" encoding="UTF-8" ?> | ||
| <CMSite folder="/Sites/CaaS/Germany/English/Navigation" name="CaaS [Site]" xmlns:cmexport="http://www.coremedia.com/2012/cmexport"> | ||
| <CMSite folder="/Sites/CaaSsiopeia/Germany/English/Navigation" name="CaaS [Site]" xmlns:cmexport="http://www.coremedia.com/2012/cmexport"> | ||
| <locale>en-DE</locale> | ||
| <master/> | ||
| <id>caassiopeia-en-DE</id> | ||
| <name>CaaS Demo Site</name> | ||
| <root><link href="CaaS%20Start%20Page.xml" path="/Sites/CaaS/Germany/English/Navigation/CaaS%20Start%20Page"/></root> | ||
| <name>CaaS Fragment Demo Site</name> | ||
| <root><link href="CaaS%20Start%20Page.xml" path="/Sites/CaaSsiopeia/Germany/English/Navigation/CaaS%20Start%20Page"/></root> | ||
| <siteManagerGroup></siteManagerGroup> | ||
| <localSettings><Struct xmlns="http://www.coremedia.com/2008/struct" xmlns:xlink="http://www.w3.org/1999/xlink"> | ||
| <StringProperty Name="tenantId">coremedia</StringProperty> | ||
| </Struct></localSettings> | ||
| <linkedSettings><link href="../Options/Settings/CaaS%20Mappings.xml" path="/Sites/CaaS/Germany/English/Options/Settings/CaaS%20Mappings"/></linkedSettings> | ||
| <linkedSettings><link href="../Options/Settings/CaaS%20Mappings.xml" path="/Sites/CaaSsiopeia/Germany/English/Options/Settings/CaaS%20Mappings"/></linkedSettings> | ||
| </CMSite> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.