Submission Help

Use this section as the source of truth for the Community Apps submission flow. The pages here are written in Markdown so they can be published to the external docs site later without re-authoring the same guidance in multiple places.

In this section

• Repository XML format explains the minimum XML structure required for Docker templates and plugin wrappers.
• Repository information XML covers the ca_profile.xml file required for repository overview and support metadata.
• XML field reference is generated from the parser field catalog and lists only the public XML tags we intentionally document.
• Builder guide walks through a practical starter flow for creating a new submission-ready repository.

Recommended starting point

Start from the starter repository whenever possible. It is the maintained scaffold for Community Apps submissions, and the examples in these docs are expected to stay in sync with it.

Before you submit

1. Make sure the repository is public and active.
2. Add an OSI-approved LICENSE file at the repository root.
3. Add a ca_profile.xml file with a non-empty <Profile> section.
4. Include valid Docker template XML and/or plugin wrapper XML files.
5. Check the generated XML field reference if you need parser-backed tag guidance beyond the starter files.
6. Run Validate and Scan in the submission flow after each meaningful XML change.

External references

• Starter repository
• Community Apps support thread