Contently currently offers support for AEM 6.1, 6.2, 6.3, 6.4, 6.5. 

Yes. Contently currently offers support for both Classic UI and Touch UI. 

Make sure you selected an actual page and not a folder in the sample page field. If you are using Touch UI, please also make sure you followed the steps in the 'Update Your Web Console Configuration' section in the AEM Integration Guide.

First, make sure you drilled all the way down and selected a component in the component selector dialogue. Second, if you are using Touch UI, please make sure you followed the steps in the 'Update Your Web Console Configuration' section in the AEM Integration Guide.

Yes, you can edit an existing sample page. If you edit an existing sample page, please make sure to also edit the mapping for the sample page. If you edit existing fields or add new page properties or components to your sample page, you will need to make sure the mapping for this sample page is up to date to reflect these edits. These changes will only affect new AEM pages that you pull Contently content onto.

Yes. If you connect AEM to more than one Contently integration — and therefore have multiple integrations in Contently — you can use the same sample page for each integration. Each integration will have its own cloud configuration in AEM. You will have to create a separate mapping for each cloud configuration. Both mappings can use the same sample page.

If the integration name you are looking for is not in the drop down, you will need to follow these instructions to get an API key from Contently and follow the steps in the "Contently Cloud Service Configuration" section.

Each time you create a new AEM page with Contently content on it, we will create a new folder at the AEM DAM path you specified in your mapping. The name of this folder will match the name of your Contently story. Your assets from Contently will be uploaded to this new folder.

If you cannot find this new folder, make sure you are looking in the right DAM location. This new folder will be created at the DAM path you specified in your mapping. To see which DAM path you chose in your mapping, navigate to the cloud configuration with the same name as the Integration Name you chose when you created your new page. If you have more than one mapping in this cloud configuration, look for the mapping that is tied to the AEM page template you chose when you created your new page. AEM page templates are listed in your list of mappings. Edit the mapping to see which DAM path you originally specified.

If your images are not in this folder, make sure there are images attached to your Contently story. Images will only be pulled in if the image fields from your Contently story are specified in your mapping.

Some pieces of content from Contently might have fields that are empty. This is especially true for custom fields. Custom fields may be left empty on certain stories in Contently.

This might be happening for a variety of reasons. First, the ‘Push to CMS’ button will only show up on the story page for completed content in Contently. Second, not every user has permission to push stories to their CMS. You typically need admin permissions for this button to appear. And third, you might not have the AEM integration installed on your publication. Visit the Integrations page in your Publication Settings in Contently. If an AEM integration does not appear in the list, follow these instructions to add the AEM integration to your Contently account. 

If you have a question that wasn't answered here and you can't find information about it in our AEM Integration Guide or AEM Technical Manual, please reach out to your Customer Success lead who can put you in touch with product team.