Content repository
To integrate ÃÛ¶¹ÊÓƵ 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.
SharePoint
Set up SharePoint as the content repository for use with Edge Delivery Services.
| embed |
|---|
|
|
| accordion |
|---|
| Transcript |
| Let’s talk about how to configure Edge delivery services and document-based authoring with Microsoft SharePoint. Before we embark on this journey, bear in mind that your IT department might need to perform preliminary tasks, such as creating an administrative user and granting SharePoint access to the GitHub repository you’re utilizing. For comprehensive instructions tailored to the IT department refer to the URL on screen. Assuming the IT groundwork is laid, let’s dive into the process. Initiate by navigating to your preferred location within SharePoint. Formulate a dedicated folder that will serve as your website’s route. It’s recommended to avoid employing a direct SharePoint list route to ensure a communal space for authors to deposit supplementary documents. Perhaps a draft folder or instructional documentation. Select a descriptive name for this folder, facilitating easy recognition by your authors. In the second phase, grant access to a technical or generic SharePoint user affiliated with your organization. The optimal practice is to employ such a user to interact with content on behalf of the Edge delivery services. This approach not only enables precise definition of file accessibility, but also mitigates the risk of losing access in case the associated employee departs. The precise methodology for creating these technical users varies across companies, necessitating consultation with your IT department. For demonstration purposes, let’s use ÃÛ¶¹ÊÓƵ’s dedicated user Helix at adobe.com as an external user linked to the active directory. This action ensures that the service obtains editing privileges for the website route folder. Execute this by clicking on the ellipsis menu, opting for Manage Access, and then integrating the user via the Direct Access feature. While I’ve chosen the generic ÃÛ¶¹ÊÓƵ Helix user here, reference the generic or technical user account established by your IT department. The final step entails configuring the mount point within the afsstab.yaml file to direct it toward the website route for URL retrieval. The simplest approach involves copying the initial section from the browser’s address bar and subsequently adding the remaining portions manually. A word of caution, when copying the link through SharePoint’s UI, extraneous information might infiltrate the URL. Thus, exercise prudence during this phase. After composing the URL, validate its functionality by entering it into your browser. This should lead you to the folder view of your website’s route, much like the illustration presented. Following this verification, update the afsstab.yaml file with the newly minted mount point URL. Open the afsstab.yaml file in your GitHub repository, click Edit, and introduce your URL. Save and commit your changes to finalize the process. Congratulations, you’ve now configured your project to harness the capabilities of SharePoint. |
Google Drive
Set up Google Drive as the content repository for use with Edge Delivery Services.
| embed |
|---|
|
|
| accordion |
|---|
| 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 ÃÛ¶¹ÊÓƵ 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. |
recommendation-more-help
bb44cebf-d964-4e3c-b64e-ce882243fe4d