metadata.md

product	git-repo	index	solution-title	solution-hub-url	getting-started-title	getting-started-url	tutorials-title	tutorials-url
Adobe Experience Manager	https://github.com/AdobeDocs/experience-manager-core-components.en	y	Learn & Support for AEM	https://docs.adobe.com/content/help/en/experience-manager-cloud-service/sites/home.html	Getting Started Developing for AEM	https://docs.adobe.com/content/help/en/experience-manager-cloud-service/core-concepts/home.html	AEM Tutorials	https://docs.adobe.com/content/help/en/experience-manager-learn/cloud-service/overview.html

Metadata for internal use

Metadata in the GitHub authoring system is hierarchal and is defined the the following increasing levels of precedent.

1. metadata.md
2. ToC
3. Article

Metadata defined in the metadata.md file apply to the entire repo, but can be overridden at the ToC and article levels. Any overriding of the metadata should be done at the lowest level possible.

The metadata in the experience-manager-core-components.en repo is the minimum required.

metadata.md

• product
• git-repo
• index: y
• solution-title
• solution-hub-url
• getting-started-title
• getting-started-url
• tutorials-title
• tutorials-url

ToCs

• sub-product
• user-guide-title

Article

• title
• description
• index: n (only for previous versions of components)

Additional information about the metadata can be found in the internal authoring guide.