index.html

---
layout: default
title: Home
---

<section class="hero">
  <div class="container">
    <span class="hero__eyebrow">Spring Boot · Quarkus · .NET · Python · C++ · Go</span>
    <h1 class="hero__title">{{ site.title }}</h1>
    <p class="hero__lead">{{ site.description }}</p>
    <div class="hero__cta">
      <a class="btn btn--primary"
         href="{{ '/docs/00-setting-up/' | relative_url }}">Start the book →</a>
      <a class="btn btn--secondary"
         href="{{ '/examples/' | relative_url }}">Run the examples →</a>
      <a class="btn btn--secondary"
         href="https://github.com/{{ site.github_username }}/{{ site.github_repo }}"
         rel="noopener">View on GitHub ↗</a>
    </div>
  </div>
</section>

<section class="section-tight">
  <div class="container">
    <div class="stats">
      <div class="stat"><span class="stat__value">6</span><span class="stat__label">One book, six languages — Spring Boot, Quarkus, .NET, Python, C++, Go — behind one tab</span></div>
      <div class="stat"><span class="stat__value">13</span><span class="stat__label">Chapters from cloud-native principles through anti-patterns, plus nineteen deep-dive appendices A–S and an acronym glossary</span></div>
      <div class="stat"><span class="stat__value">📊</span><span class="stat__label">Runs on Docker Engine locally and plain Kubernetes — no managed cloud on the primary path</span></div>
      <div class="stat"><span class="stat__value">21</span><span class="stat__label">Runnable examples with automated verification — Spring Boot, Quarkus, .NET, Python, C++, and Go</span></div>
    </div>
  </div>
</section>

<section class="section">
  <div class="container">
    <h2 class="section-heading">What this tutorial is</h2>
    <p class="section-sub">
      A chapter-based companion to the <em>Designing Cloud-Native APIs</em>
      deck series. Each section of the decks becomes a chapter; the code is
      shown for Spring Boot, Quarkus, .NET, Python, C++, and Go behind a single set
      of tabs, so you read the pattern once and see it in the stack you work in.
      The running examples are the order, payment, inventory, notification, and
      shipping services, on Docker Engine locally and plain Kubernetes in production.
    </p>

    {%- comment -%}
      Two-level navigation: the homepage shows one card per Part. Each Part
      card links to its own page (the _parts collection) which lists that
      part's chapters. New chapters appear under their part automatically;
      new parts appear here just by adding a file to _parts/.
    {%- endcomment -%}
    <div class="cards">
      {% assign parts_sorted = site.parts | sort: "order" %}
      {% for part in parts_sorted %}
      {% assign part_docs = site.docs | where: "part", part.part_name %}
      <a class="card" href="{{ part.url | relative_url }}">
        <div class="card__eyebrow">Part {{ part.order }}</div>
        <h3 class="card__title">{{ part.title }}</h3>
        {% if part.blurb %}
        <p class="card__desc">{{ part.blurb }}</p>
        {% endif %}
        <div class="card__meta">
          {% if part_docs.size > 0 %}
            <span>{{ part_docs.size }} chapter{% if part_docs.size != 1 %}s{% endif %}</span>
          {% else %}
            <span>Coming soon</span>
          {% endif %}
          <span>Explore →</span>
        </div>
      </a>
      {% endfor %}
    </div>
  </div>
</section>