Automated Checks for Architecture Center Contributions
Guidelines > Automated Checks
A contributor guide to the GitHub Actions checks that run on every SAP Architecture Center pull request, what they verify, and where results appear.
A community of practice is a group of people who share a profession or interest and come together to exchange knowledge, solve problems, and sharpen their skills. Grounded in a shared domain, it drives collaboration and continuous learning through shared experiences and resources.
View all tagsA contributor guide to the GitHub Actions checks that run on every SAP Architecture Center pull request, what they verify, and where results appear.
A tour of the background workflows that build and deploy the site to GitHub Pages and Cloudflare, scan for vulnerabilities, and check license compliance.
Links to Cloudflare, GitHub and SAP policies on cookies and privacy, including their cookie notices, privacy statements, and account privacy settings.
Learn how to organize folders, diagrams, images, and documentation for consistency and clarity in your SAP Architecture Center contribution.
Use AI coding agents to contribute to the SAP Architecture Center. Learn how AGENTS.md, CLAUDE.md, and skills give agents project context and conventions.
Contribute to the SAP Architecture Center Community of Practice: share reference architectures, follow the contribution process, and co-create with SAP experts.
How the contributor IDs check keeps SAP internal user IDs (I-, D-, and C-numbers) out of the author and contributors front matter, and why it can block a merge.
How the SAP Architecture Center uses cookies and similar technologies, the types of first- and third-party cookies set, and how to manage or delete them.
Learn about the custom Contributors and Draw.io components built for the SAP Architecture Center, and how to use them in your own reference architecture pages.
Learn how the sap, industry, partners, and people dictionaries teach cspell your terms, when to add a word, and how they differ from the typos word list.
Best practices for CSS, responsive design, and performance in the SAP Architecture Center. Ensure a fast, accessible, and maintainable site.
Welcome to the development section of the SAP Architecture Center, an open source project with guidelines, best practices, and examples to help you contribute.
Best practices for creating Draw.io diagrams for SAP solution architectures and Mermaid diagrams for process flows in the SAP Architecture Center.
How the drawio check keeps diagram files under one megabyte and blocks external image references, so every diagram stays self-contained and loads reliably.
How the external link check uses lychee to verify that outbound links in your changed pages still resolve, and why network issues are reported, not inlined.
Learn how to use front matter in SAP Architecture Center pages. This guide explains each YAML field: title, description, slug, keywords, tags, and more.
How the front matter properties check validates authorship, dates, and house-style fields on changed reference architecture pages, and why it can block a merge.
How the non-blocking LanguageTool grammar check reviews prose in your changed docs and news pages, where its suggestions appear, and why it never fails a PR.
Why Architecture Center pages must take their title from the front matter instead of a level-1 Markdown heading, and how the H1 title check enforces it.
Learn how to contribute to the SAP Architecture Center. Follow step-by-step guidelines for submitting code, documentation, or AI-generated content.
How the internal link check finds SAP-internal-only URLs that break for public visitors, which host patterns it flags, and which customer-facing hosts are safe.
How the orphan files check verifies that every image or diagram you add is actually referenced by a Markdown page, and when it warns instead of failing.
How SAP processes your personal data on the SAP Architecture Center, the legal bases, your data protection rights, and country-specific privacy provisions.
How the Quick Start tool uses GitHub OAuth and what personal data it processes to fork repositories, commit changes, and create pull requests on your behalf.
Publish reference architectures with Quick Start, the no-code editor: log in with GitHub, add text and Draw.io diagrams, and submit a pull request.
How the ID check validates that every reference architecture has a unique six-character id and a matching slug, and what happens when two pages collide.
How the SAP Architecture Center publishes RSS and Atom feeds for the news and the reference architectures, and how to control which content appears in them.
The SAP Open Source Code of Conduct, based on Contributor Covenant 2.1, with community standards, enforcement guidelines, and how to report misconduct.
How the SEO front matter check measures the length of each page title and description, which lengths only warn, and which lengths fail your pull request build.
How the cspell spelling check scans changed Markdown on your pull request, what it flags as unknown words, and how custom dictionaries keep it quiet.
Meet the Office of the CTO and the network of core and extended contributors who build, publish, and govern the SAP Architecture Center.
How the typos check catches real misspellings in changed docs and news pages without flagging valid SAP product names, and how to allow a word it corrects.
A worked walkthrough of a pull request: which checks run, where errors and warnings appear, what blocks a merge, and how to read and fix each message.