STACKIT Landing Zone Accelerator
STACKIT
Zuletzt aktualisiert am
Drei Stationen zu deinem ersten Beitrag: ein Profil, das sagt, wer du bist, ein Asset mit deinem Wissen und ein Trail, der deine Assets verbindet.
Assets tragen, was du weißt. Ein Profil sagt, wer du bist, und du brauchst eines, wenn eine Organisation hinter der Arbeit steht. Ein Trail ist optional und macht aus Assets eine Journey. Das Studio hilft bei allen dreien.
Dein Profil ist eine Seite mit deinem Namen, deinem Logo und einer kurzen Beschreibung. Sie kommt über einen normalen Pull Request hinein. Jedes Asset von dir verweist darauf zurück. Du trägst in eigenem Namen bei? Dann lass diese Station aus und nutze den geteilten Eintrag open-contributors.
The file name of your profile is your contributor slug. Assets, trails and logos find your profile through this slug. Your assets sit under assetcontainer/[partner-slug]/. The logo is found in the profile folder with the same name.
docs/contributors/[partner-slug].mdxdocs/contributors/[partner-slug]/Each theme carries its own file. A theme without one shows a placeholder mark instead of borrowing the other. A logo drawn for white paper disappears on our dark surfaces, so one file no longer serves both themes.
logo.png or logo.svg in the partner-specific subdirectory, 1:1 square aspect ratio. This is the file shown on the dark theme.light-logo.png or light-logo.svg, same folder and format rules. If your mark works on both grounds, supply the same artwork under both names.Ein Asset ist eine MDX-Seite mit einem kurzen Metadatenblock: ein Titel, eine Beschreibung mit 120 bis 160 Zeichen, eine Kategorie und bis zu 10 Tags. Daraus baut die Seite diese Karte.
STACKIT
Der souveräne europäische Cloud-Anbieter hinter dem Framework, mit IaaS und PaaS aus eigenen Rechenzentren in Deutschland und Österreich.
The build checks the frontmatter of every asset. The rules below say what each field needs. A file that breaks a hard rule stops the build.
Asset metadata lives under the scfAsset key (mirroring scfTrail for trails). The former name frameworkAsset is still accepted, so existing files keep working; new assets should use scfAsset. Optionally, add a maintainers list to credit who maintains the asset as a point of contact (shown above the git history).
maintainers names the people or organizations who look after this asset and act as its point of contact. It renders as a Maintainers block above the contributor list of the git history. It is a credit, not a permission: it does not restrict who may edit the file. Trails use the identical field under scfTrail.
If you have a STACKIT Git account, name yourself by username and nothing else. That is the whole entry:
scfAsset: maintainers: - user: "jane.doe"Everything else about you lives in one place: docs/settings/contributor-members.json, maintained by Framework Core. It records which contributor organization you belong to. It also records which of your mirrored profile fields may be shown: your biography as the role line, your website, your address and your contribution record. That file is the reason an asset cannot decide what is published about you: only the person a field describes can grant it. A field nobody granted is never even fetched.
Ask Framework Core to add or change your entry. It looks like this:
"jane.doe": { "org": "acme-corp", "show": { "role": true, "website": true, "activity": true }}Your organization comes from there too, which is why you do not write contributor next to a user: nobody should be able to inherit an official partner badge by typing a company name beside their own.
Two things have to exist before anything about you appears, your name included. These are your entry in the membership file and the declaration behind it. The declaration is where you state, once, what you release for publication: your brand and your content. It also says which of your profile details may be shown.
You file it yourself. Open an issue in the content repository, pick the Contributor declaration template and fill it in. A pipeline turns it into a proposed change of docs/settings/contributor-members.json, which Framework Core or your framework owner approves. Nothing you write in the issue is rendered on the site. It is the record behind what the site is allowed to do.
Until that record exists, the daily pipeline publishes nothing about you, your name included, so the credit reads “Name not public” even when the flags in the membership file are already set. The flags describe what you allow. The declaration is the proof that you allowed it. The pipeline waits for both.
The same route works later. To change what is shown, file a new declaration. To withdraw everything, pick the Withdraw your declaration template. A comment on your own declaration issue works too; Framework Core then updates your entry by hand. A role: true in an asset does nothing, so there is no way to switch a field on from a content file. That is the point: only the person a field describes can release it.
The pipeline mirrors the profiles once a day and copies only the fields that person allowed: a website, an address or a biography nobody consented to is never fetched and never stored. Your full name needs no box of its own: the declaration itself releases it, because it is the name you are credited under. Until your first mirror runs the entry shows your plain username, so a new maintainer is credited immediately rather than showing an empty row. Once mirrored, an empty Full name counts as a choice: the credit then reads “Name not public” instead of exposing your username. If you would rather keep a recognisable byline without your legal name, set the Full name to a pseudonym, a short form or your initials. The site then shows exactly that.
Every field is optional and they combine freely. An entry only has to carry at least one of user, name, contributor or email, so it is never rendered anonymously. One asset accepts up to 6 entries.
| Field | Purpose |
|---|---|
user | STACKIT Git username. The lookup key for the mirrored profile. It is also the fallback label until the profile has been mirrored. |
role | Sets the role text literally. For people without an account: with a user, the biography from their own profile appears instead, but only if they allowed it. |
website | Sets a URL literally, same rule as role. |
email | Sets an address literally, same rule as role. It renders as its own mail action, so it sits alongside a profile link instead of competing with it. |
name | Overrides the mirrored full name. It also credits people who have no Git account at all. It makes the entry a person: initials avatar, role line reading role · organization. |
contributor | Slug of a /contributors/<slug> profile, for people without an account. On its own it credits the organization, using the profile title, its logo initials and its official partner badge. Ignored next to a user, whose organization comes from the membership file. |
link | A profile or homepage URL, typically LinkedIn. It becomes the entry’s own link and takes precedence over both the mirrored website and the contributor profile. |
External partners have no account on the instance, so they are credited with the explicit fields instead:
scfAsset: maintainers: - name: "John Smith" role: "Platform Engineer" contributor: "acme-corp" email: "john.smith@example.com" link: "https://www.linkedin.com/in/john-smith/" - contributor: "acme-corp" role: "Managed service"The category field in the scfAsset block accepts one of these twelve values. Any other value fails the build:
| Category | Purpose |
|---|---|
generic | Fallback for assets that fit no specific category. |
blueprint | Reference architectures and solution designs. |
guide | High-level overviews or step-by-step installation instructions. |
code-snippet | Reusable code parts (Terraform, YAML, CLI). |
policy | Governance, security rules and compliance templates. |
video | Visual product demonstrations or webinars. |
workshop | Materials for discovery, planning, or migration workshops. |
case-study | Success stories and real-world implementation examples. |
whitepaper | Strategic concepts and deep technical research. |
service | Professional or managed offerings (consulting, support, operations). |
software | Ready-to-use applications, platform extensions, or tools. |
runbook | Step-by-step preparation, execution, validation and rollback instructions. |
Du füllst ein Formular aus. Das SCF Studio prüft jedes Feld schon beim Tippen und öffnet den Pull Request für dich. Es lädt auch eine bestehende Seite und ändert nur, was du bearbeitest.


Ein Trail ist eine Liste von Schritten. Jeder Schritt zeigt auf ein Asset, eine Seite oder einen Abschnitt daraus. Mit einem Bild oder einer zweiten Spalte wirkt er auch als Folie.
A step shows either text that you write or a card that points at another page. Each type below has an example.
Use a text step for an idea or a phase that has no page of its own yet. You write the title and the trailContext. The trailContext is the text the reader sees on the step. To write a step that works on a slide, see Write Steps That Work as Slides .
- style: "compass" title: "Assess the workloads before you build" trailContext: "Analyze the workload and its requirements before you create any resources."Use an asset step to point at an asset by its assetId. The step shows the asset card with its contributor. Add an optional #section-anchor to the assetId to show only that section of the asset instead of the whole page, exactly like the page references below (for example .../assetcontainer/stackit/howto-contributors#profile-and-logo-paths).
- style: "gondola" title: "The landing zone is the baseline" trailContext: "The accelerator sets up the baseline." assetId: "migration/assetcontainer/stackit/landing-zone-foundation-opentofu"Use a page step to point at a regular framework page that is not an asset. Name it with its pageId. The step shows the page card and the page content right in the timeline. Add an optional #section-anchor to show only that section of the page instead of the whole page.
- style: "stairs" title: "The migration modules cover the core of this phase" trailContext: "Go through the core modules of this phase." pageId: "migration/migrate/#core-modules-in-this-phase"Klicke auf Präsentieren, und der Trail läuft als Deck: am Beamer, mit einem Klicker oder am Handy. Du siehst gerade eines.


Öffne den Pull Request. Die Prüfungen laufen im Hintergrund. Mit dem Haken für die Vorschau geht eine passwortgeschützte Vorschauseite für das Review online. Mit dem Haken für den automatischen Merge folgt der Merge der Freigabe. Die öffentliche Seite zeigt die Änderung innerhalb von zwei Stunden.
Copy this example as the start of a new trail. You can add a maintainers list under scfTrail to credit who maintains the trail as a point of contact (shown above the git history). Assets use the same field.
If you have a STACKIT Git account, name yourself by username and nothing else. That is the whole entry:
scfTrail: maintainers: - user: "jane.doe"| Field | Purpose |
|---|---|
user | STACKIT Git username. The lookup key for the mirrored profile. It is also the fallback label until the profile has been mirrored. |
role | Sets the role text literally. For people without an account: with a user, the biography from their own profile appears instead, but only if they allowed it. |
website | Sets a URL literally, same rule as role. |
email | Sets an address literally, same rule as role. It renders as its own mail action, so it sits alongside a profile link instead of competing with it. |
name | Overrides the mirrored full name. It credits people who have no Git account. It makes the entry a person with an initials avatar and a role line reading role · organization. |
contributor | Slug of a /contributors/<slug> profile, for people without an account. On its own it credits the organization with the profile title, its logo initials and its official partner badge. Ignored next to a user, whose organization comes from the membership file. |
link | A profile or homepage URL, typically LinkedIn. It takes precedence over both the mirrored website and the contributor profile. |
Every field is optional and the fields combine freely. An entry only has to carry at least one of user, name, contributor or email. One trail accepts up to 6 entries. Keys the schema does not know are dropped without an error, so a typo leaves the build green and renders nothing. Maintainers are a credit, not a permission: the list does not restrict who may edit the trail. The asset integration guide carries the same fields with an example for external partners.
---title: "Standard Kubernetes Onboarding Track"description: "A comprehensive guided journey trail directing engineering workloads from legacy virtualization targets into sovereign managed STACKIT clusters."scfTrail: # Optional: credit the maintainers (shown as a point of contact above the git history). maintainers: - name: "Jane Doe" role: "Trail Owner" steps: - style: "compass" title: "Assess the workloads before you build" trailContext: "Analyze workload traits and infrastructure requirements before initializing resources."
- style: "gondola" assetId: "migration/assetcontainer/stackit/landing-zone-foundation-opentofu" trailContext: "Deploy the landing zone automated profile using standardized infrastructure code scripts."
- style: "stairs" title: "The migration modules come next" trailContext: "Work through the core migration modules; the optional #anchor renders only that page section." pageId: "migration/migrate/#core-modules-in-this-phase"
- style: "summit" title: "Validate the cluster before go-live" trailContext: "Review compliance policies and confirm that all configuration checks pass security rules."---