DivrajSingh
Offline
Joined the community
11/2/20
Employee
Employee
Sr. Manager Product Experts, AEM Guides
Delhi, India
Badges
Accepted Solutions
Likes Received
Posts
Discussions
Questions
Ideas
Blog Posts
-
Also do make sure the HTML heading does not include any namespaces, a sample HTML header would be: <?xml version="1.0" encoding="UTF-8"?> <html xmlns=http://www.w3.org/1999/xhtml> With all the rules catered, the sample index.html will look like: <?xml version="1.0" encoding="UTF-8"?> <html xmlns="...Discussions
Type
3.1KViews
1Like
4Replies
-
The steps you defined seems correct and we validated the functionality on XML Documentation v3.8 - and it works as expected. Will it possible for you to share the sample content zip? Or you can raise a support ticket with the sample package.Discussions
Type
3.1KViews
0Likes
5Replies
-
It seems you did already publish to the same target "/content/output/sites" once using the default config "/libs/fmdita/config/templates/default" before using the weretail-techdocs config - because of which the settings are from default template. To explain - the template settings are set only on th...Discussions
Type
6.5KViews
1Like
2Replies
-
Hi @Apmag , If you are asking about the configuration "topicPageTemplate" - this is added on the new config that you can create, refer Step1 of the original post on this page. The generated page uses this config to create page that uses this value as cq:template.Discussions
Type
6.5KViews
1Like
4Replies
-
For understanding how editable templates are setup, you can refer to the samples site (weretail) page "/content/we-retail/us/en" which uses the component "/apps/weretail/components/structure/page" - from where you can follow how header and footer are aded to their pages. We used the content page tem...Discussions
Type
6.5KViews
1Like
0Replies
-
These paths are the nodes under the generated page where the content of topic and topic head gets generated. Following description is the snippet from Installation and configuration guide: These two properties are mandatory - or else the DITA content will not be added to the generated page.Discussions
Type
6.7KViews
1Like
9Replies
-
REQUIREMENT You are managing DITA content in AEM, and you want to publish that content to (say) PDF output. But you have metadata for your publication(ditamap) managed as AEM metadata - and you want to pass this metadata to the publishing engine to use it in the output. Let us understand this with...Discussions
Type
15.0KViews
3Likes
9Replies
-
Problem Statement You are using XML Documentation to author XML/DITA content and one of the publish output is AEM Sites.You want to use an existing AEM Sites template in order to use the pre-designed header/footer (branding, styles etc.) used on your marketing or end user portal (instead of out-of-t...Discussions
Type
6.9KViews
3Likes
20Replies
-
AEM creates additional version of a media assets when you revert between different versions of the asset. This is functionality as design, as the system: expects that the image version that is currently active may have some work in progress changes and may require saving those before moving to anoth...Discussions
Type
1.2KViews
3Likes
0Replies
-
@Kiran_Mohan : I think what you are asking is documented here. Let me know if you were looking for somethin else.Discussions
Type
6.4KViews
0Likes
0Replies
7/28/21
Customize the badges you want to showcase on your profile
Events
Community
- Community home
- Guidelines
- Community Advisors
- Experience League Showcase
- Advertising
- Analytics
- Audience Manager
- Campaign Classic v7 & Campaign v8
- Campaign Standard
- Developer
- Experience Manager Sites & More
- Experience Platform
- Journey Optimizer
- Target
- Community Announcements
- Real-Time Customer Data Platform
- Workfront
- Marketo Engage
- Commerce
- Creative Cloud
- Document Cloud
Resources
Adobe account
Change language
Copyright © 2025 Adobe. All rights reserved.
