svierk.github.io valid

Salesforce DevOps Starter Kit

CI/CD building blocks for Salesforce

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-25T13:32:30.218Z. Cached copy · Source on svierk.github.io

# Salesforce DevOps Starter Kit

> CI/CD building blocks for Salesforce

Compose flexible, GitHub-native pipelines from small, focused Actions - or drop in a ready-made reusable workflow and be productive in minutes.

## Table of Contents

### Guide

- [Getting Started](https://svierk.github.io/salesforce-devops-starter-kit/getting-started.md): Set up a first Salesforce CI/CD pipeline with the kit - from choosing a strategy and configuring JWT authentication to pull request validation and deployment.
- [Authentication](https://svierk.github.io/salesforce-devops-starter-kit/authentication.md): Authenticate CI/CD pipelines to Salesforce orgs with the JWT bearer flow or an SFDX Auth URL, and store the credentials as GitHub Actions secrets.

### Strategy & Blueprints

- [Find your blueprint](https://svierk.github.io/salesforce-devops-starter-kit/strategy.md): Five questions about orgs, teams, team setup, maturity and release style route a Salesforce team to one of five DevOps blueprints.
- [B1 - Simple Org Development](https://svierk.github.io/salesforce-devops-starter-kit/strategy/b1-simple-org-development.md): One team on one production org - GitHub Flow with short-lived feature branches, PR validation and a gated production deployment.
- [B2 - Multi-Team with Environment Branches](https://svierk.github.io/salesforce-devops-starter-kit/strategy/b2-multi-team-environment-branches.md): Several teams sharing one production org - environment branches with story promotion, release bundles or a release train, and approval gates per stage.
- [B3 - Modular Trunk](https://svierk.github.io/salesforce-devops-starter-kit/strategy/b3-modular-trunk.md): Several mature teams on one trunk - feature flags, source modules or unlocked packages, and a validation gate plus scratch org CI that genuinely block.
- [B4 - Multi-Org / Regional Rollout](https://svierk.github.io/salesforce-devops-starter-kit/strategy/b4-multi-org-regional.md): Several production orgs by region or business unit - a shared core as pinned package versions, or one environment chain per org.
- [B5 - Low-Code First](https://svierk.github.io/salesforce-devops-starter-kit/strategy/b5-low-code-admin-first.md): Admin-heavy teams where Git knowledge is the bottleneck - two org-bound branches, tool-driven promotion and a validation gate tuned to declarative work.
- [Kit Mapping](https://svierk.github.io/salesforce-devops-starter-kit/strategy/mapping.md): Which reusable workflows, input settings, branch protection rules and GitHub Environments each of the five blueprints switches on.
- [Background & Trade-Offs](https://svierk.github.io/salesforce-devops-starter-kit/strategy/background.md): The reasoning behind the blueprints - sandbox types and licences, single- vs. multi-org, org vs. package development, branching models, release styles and maturity levels.

### Reusable Workflows

- [PR Validation](https://svierk.github.io/salesforce-devops-starter-kit/workflows/pr-validation.md): Reusable workflow that
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=svierk.github.io · GET /v1/domain/svierk.github.io · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for svierk.github.io:
1. POST https://agentwebmap.com/v1/sites/svierk.github.io/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://svierk.github.io/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/svierk.github.io/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/svierk.github.io).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.