Builder Guide

Use this flow to create a new Community Apps repository quickly without missing the metadata required by the submission pipeline.

Start here

Use the starter repository as the default starting point. It already includes the required root files, example Docker and plugin XML, and a placeholder icon that the submission flow will reject if you forget to replace it.

Quick start checklist

1. Create a new repository from the starter repository, or copy its structure into your own repo.
2. Make sure the repository is public and not archived or disabled.
3. Replace the starter README.md, LICENSE copyright line, icon.svg, and XML placeholder values.
4. Remove any example Docker or plugin files you do not need.
5. Add template XML files for each Docker app and/or plugin you publish.
6. Run Validate and Scan in /submit.
7. Submit for review once all scan checks pass.

Suggested repository layout

my-ca-repo/
  README.md
  LICENSE
  .gitignore
  icon.svg
  ca_profile.xml
  templates/example-app.xml
  plugins/example-plugin.xml

Builder paths

Pick the path that best matches how you want to build and maintain the repository:

• Template-first: create XML files directly, then iterate with submission scan feedback.
• App-first: start from one working container template, then copy and refine it for additional apps.
• Plugin-first: publish the plugin manifest first, then add the matching plugin XML wrapper with enough review context.

Recommended next step

After the initial scaffold is in place, review the Repository XML format page, confirm your repository info in Repository Information XML, use the parser-backed XML field reference when you need more tag detail, and run the submission flow at /submit.