How to submit

Welcome

Welcome to the Cloud Native Reference Architecture contributing guide, and thank you for your interest.

The goal of this site is to show real-life examples of successful cloud native architectures in order to make good choices easier to find.

The Cloud Native Reference Architecture content is stored in this GitHub repo where you’ll find a list of issues, and pull requests (PRs) for the site.

Join the Reference Architectures community!

If you want to contribute to the project or want to get in discussion with the maintainers and other contributors, you can join our #reference-architectures channel on the CNCF Slack — we’d love to meet you!

Add new architecture

Who can contribute?

Given the nature of the content we are only accepting PRs from CNCF members at this time. This will be verified during the PR approval process.

Before you start

Before beginning your Reference Architecture contributor journey, be sure to complete the following steps:

  1. Create a GitHub account, if you don’t have one already.
  2. Sign the Contributor License Agreement (CLA).
  3. Verify your commit signature
  4. Enable vigilant mode in your GitHub account to display the “Verified” status on your commits.

Submitting a new architecture

By raising a PR, you can submit a new architecture to the CNCF Reference Architecture site.

There are two template markdown files available which you can follow to see how you might build your story.

  • refarch.md is a very common architecture template.
  • refarch-platform-engineering.md is based on the common architecture template but includes an additional section to highlight the Platform Engineering team.

The architecture should go in the content/en/architectures folder. For each architecture, you should create a new folder with the name of the company. Images should be stored in the content/en/architectures/<company-name>/images folder. It’s also possible to include diagrams in the architecture. These can be included as Markdown code blocks, written in mermaid.js (also see the hugo documentation about Mermaid diagrams).

Best practices

To facilitate the reviewing process, please use semantic line breaks (e.g., one line per sentence). We recommend checking out this markdown cheat sheet to correctly format Markdown text in GitHub (e.g., hyperlink, bold, italic). And when naming .md files, please use lowercase letters and hyphens instead of spaces to separate words and avoid parenthesis.

Update an existing architecture

To update an existing architecture, you can request changes by creating an issue or, if you are from the organization that submitted the architecture, work on the changes yourself and submit a PR.

Request a change via an issue

If you want to flag a problem with an architecture, you can use the “Report issue” option of the CNCF Reference Architecture webpage. Locate yourself in the CNCF page of the architecture you’d like to flag and click on “Report issue”. This will automatically open an issue for you.

We updated this guide based on templates from The Good Docs Project.

Last modified November 18, 2024: Update how-to page with correct links (565cf0f)