StepsSection

<StepsSection
  title="What happens on push"
  description="The same four steps for every site produced by the technology — nothing bespoke per project."
>
  <StepItem
    ind="1"
    title="Content lands in git"
    description="You edit markdown or typed content tags — in your IDE, in the GitLab web editor, or with an AI agent working on the repository"
  />
  <StepItem
    ind="2"
    title="CI pulls the builder"
    description="A standard pipeline pulls the builder image; the engine and its locked dependencies come ready-made, so builds stay reproducible for years"
  />
  <StepItem
    ind="3"
    title="Static output is built"
    description="Markdown is rendered, images are converted into responsive webp, files are pre-compressed and SEO files are generated"
  />
  <StepItem
    ind="4"
    title="An image ships"
    description="The result is an ordinary ~50 MB nginx image — deploy it to our Kubernetes clusters or to any Docker hosting you control"
  />
</StepsSection>

<StepsSection
  title="From a git repository to a live site"
  description="A new website is just a new content repository. Time to first site — hours, not weeks."
>
  <StepItem
    ind="1"
    title="Write content"
    description="Put your content in a git repository: markdown files for articles and knowledge bases, semantically typed content tags for landing pages"
  />
  <StepItem
    ind="2"
    title="Add a tiny Dockerfile"
    description="A few lines on top of our standard builder image — no build configs, no toolchain to maintain in your repo"
  />
  <StepItem
    ind="3"
    title="Push to master"
    description="CI builds your content into a ~50 MB nginx image and deploys it — to our Kubernetes clusters or any Docker hosting of yours"
  />
  <StepItem
    ind="4"
    title="Edit and preview"
    description="Change content right in the GitLab web editor; every draft gets a staging replica of the real site to review before release"
  />
</StepsSection>