Content repository
To integrate Adobe Experience Manager (AEM) with Edge Delivery Services, start by setting up SharePoint or Google Drive as your content repository. Both platforms work well with AEM, allowing for smooth content management and delivery. Choose the one that aligns with your preferences and follow the steps to get it up and running with AEM and Edge Delivery Services.
Document authoring options
There are two supported content repositories for document authoring, SharePoint and Google Drive.
Set up SharePoint as the content repository for use with Edge Delivery Services.
| embed |
|---|
|
|
Set up Google Drive as the content repository for use with Edge Delivery Services.
| embed |
|---|
|
|
Transcript
In your fork of the Boilerplate GitHub repository, the site points to an existing content source in Google Drive. See this folder for some example content. This content is read-only, but it can be copied into your Google Drive folder to serve as a starting point. To author your own content, create a folder in your own Google Drive and share the folder with the Adobe Experience Manager user, helix at adobe.com. A good way to start authoring your own content is to copy index, nav and footer from the sample content and familiarize yourself with the content structure. Nav and footer are not changed frequently in a project and have a special structure. Most of the files in a project look more similar to index. Download the files and copy slash paste the entire content into corresponding files in your own Google Drive. You can also download the files via download all or download individual files. However, remember to convert the downloaded .docs files back into native Google Docs when you upload them to your folder in your Google Drive. Now that you have your content, you need to connect that content to your GitHub repo. You do this by changing the reference in fstab.yaml in your GitHub repo to the folder you just shared. Copy slash paste the folder URL from your Google Drive to fstab.yaml. Be aware that after you make that change, you will see 404 not found errors as your content has not been previewed yet. Please refer to the next section to see how to start authoring and previewing your content. If you copied over index, nav and footer all three of those are separate documents with their own preview and publish cycles, so make sure you preview and publish all of them if needed. Commit your changes and you have hooked up your own content source to your website.