Training Publish

Publishing the training on Trailhead

The course itself lives in ../sfdx-hardis-training and is edited with [[training-update]]. This skill covers only the two surfaces outside that repository: the Trailmixes on trailhead.salesforce.com, and the badge the course awards.

What a Trailmix can and cannot do

Re-check these once before any publishing session: the Trailhead UI changes.

Authoring a real Trailhead badge is not an option: there is no self-serve program, and myTrailhead / Enablement Sites (Trailmaker Content) is retiring. A Trailmix is the only Trailhead-native surface open to us.

Account, titles and URLs

The training site URL is temporary. The course moved from https://hardisgroupcom.github.io/sfdx-hardis-training/ to https://sfdx-hardis-training.github.io/ on 2026-10-02, and it will move again (a custom domain is planned). When it does, replace it in every source of the three repositories, in one Pull Request per repository:

# from each of sfdx-hardis, ../vscode-sfdx-hardis and ../sfdx-hardis-training
git grep -lI 'sfdx-hardis-training.github.io' -- . ':!CHANGELOG.md'

• Here the URL sits in README.md, docs/, the command descriptions under src/commands/ (and the pages yarn build:doc generates from them), CLAUDE.md and the training-* skills. Update this table and this note in the same change.
• Released CHANGELOG.md sections keep the URL they were written with.
• In the training repository the URL is written as course.site in training-universe.json and in course-site.yml (a check compares the two), and by hand in config/.sfdx-hardis.yml: the ticketing URL builders and the Training menu links. Replace all three.
• LEGACY_SITE_URL in scripts/lib/urls.mjs is the first address of the course and never changes: the forks learners made before the move still call it, and it redirects.
• test/fixtures/training-project/.sfdx-hardis.yml of the extension is a copy of the training config/.sfdx-hardis.yml: the two must stay identical.
• The path after the host does not change: only the base URL does.

Two cautions, both permanent:

• The URL embeds the account handle and the slug, and neither can be changed later without breaking every link already shared. Trailhead derives the slug from the title: do not assume the transformation, read the slug it actually generated and record it in labs/link-map.en.md of the training repository.
• These Trailmixes are personally owned. If they should outlive one person, create them from an account whose credentials the team holds, or accept the risk explicitly.

The copy

One-line descriptions, what Trailhead shows in a card. Ready to paste:

• Contributor Basics: Deliver your first Salesforce change the way a real team does: a User Story on its own branch, an org to build in, and a Pull Request that checks your work before anyone reviews it.
• Contributor Advanced: The stories that do not go through first time: deployment errors, deployment actions, overwrite protection, Apex test coverage, and a teammate who edited the same Flow as you.
• Release Manager: Own the pipeline: finish it up to production, review and merge what contributors send you, release to UAT and production, ship a hotfix, retrofit it, and monitor production.

If a single Trailmix is ever published instead of three, the title is Salesforce DevOps with sfdx-hardis and the line is: A free hands-on course that builds a complete Salesforce CI/CD pipeline on free orgs, one click at a time, from your first User Story to a monitored production release.

Longer versions of the same three, for the description field when it accepts a paragraph, are in the course README.md and the level index pages of the site. Keep them in step: the level index page is what a learner reads right after the Trailmix card.

Every description ends with the same sentence: This course awards a Cloudity badge. It is not a certification.

Level 2 is recommended to contribute and required to start Level 3. Say both, in that order, wherever the prerequisites are listed: a learner may stop after Level 1 and deliver, and a release manager cannot review a deployment error they have never solved.

Building the step list of a Trailmix

The steps are not a copy of the lab list. The shape, in order:

1. A Link to the level index page of the site, not required, titled so it reads as "why this path exists" or "what changes at this level, and how to reset if you are joining here".
2. The Trailhead warm-up modules for the level, required only where the knowledge is genuinely assumed (Git basics for Level 1, nothing for Level 2).
3. A Link to the matching sfdx-hardis guide home on sfdx-hardis.cloudity.com.
4. A Task step for anything done outside both sites: creating the Developer Edition orgs and connecting them in Orgs Manager.
5. Then, per lab and in lab order: one required Link to the lab page, followed by the optional Links to the product doc pages that lab maps to. Every lab maps to a real sfdx-hardis command and a real doc page, so there is always at least one.
6. A required Task step carrying the claim instructions.
7. A final, not required, Link to the next level's Trailmix.

Lab titles and URLs come from training-manifest.json and labs/link-map.en.md in the training repository, both generated by scripts/build/universe.mjs. Read them; never retype a lab URL by hand, and re-check the whole step list whenever a lab is renamed, renumbered or inserted, because the site URL is the file name.

Trailhead steps verified by hand and safe to link:

Do not add a step whose URL has not been opened by hand, and never link a Trailhead module published by a competing DevOps vendor, even when it is the closest match on the topic.