> ## Documentation Index
> Fetch the complete documentation index at: https://belajarkoding.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# BelajarKoding Docs

> Documentation portal for BelajarKoding products. Start with KilatKoding to set up, launch, and rebrand a SaaS boilerplate faster.

<Info>
  This portal is organized by product. KilatKoding is the first fully documented product, and the structure is ready for more products later.
</Info>

## Build faster without starting from scratch

If you want to build a SaaS app, member portal, or AI product without starting from a blank screen, begin with KilatKoding. The boilerplate already includes the foundation that usually takes the longest to build: landing pages, auth, dashboard, billing, admin, email, blog, AI, and testing.

This portal supports two audiences at the same time: non-technical readers who want to understand what is already ready to use, and developers who need to set up, customize, and launch the product in a structured way.

<Columns cols={2}>
  <Card title="Open the KilatKoding docs" href="/en/kilatkoding" horizontal>
    Go to the main entry page for reading paths, cross-platform setup, use cases, technical reference, and operational guidance.
  </Card>

  <Card title="See the best-fit use cases" href="/en/kilatkoding/use-cases" horizontal>
    Match KilatKoding to pre-launch waitlists, subscription SaaS, client portals, AI products, or client rebranding projects.
  </Card>
</Columns>

## Why start with KilatKoding

<Columns cols={2}>
  <Card title="You do not start from zero">
    You begin with an application foundation that already includes auth, payments, email, admin, dashboards, and marketing pages.
  </Card>

  <Card title="Closer to Indonesian market needs">
    KilatKoding already includes integrations such as Midtrans and Doku, plus flows that fit local products more naturally.
  </Card>

  <Card title="Useful for non-technical teams and developers">
    The docs cover planning, ownership, launch checklists, technical setup, and operational runbooks.
  </Card>

  <Card title="Flexible for customization and rebranding">
    You can change branding, pricing, pages, feature toggles, product flows, and integrations with less guesswork.
  </Card>
</Columns>

## Start with the path that fits your goal

<Columns cols={3}>
  <Card title="Understand first" href="/en/kilatkoding/product-overview">
    Start with the product overview, use cases, and no-code vs developer page to make faster decisions.
  </Card>

  <Card title="Run and set up" href="/en/kilatkoding/getting-started">
    Continue to getting started, local setup, services setup, and environment variables when you are ready to run the project.
  </Card>

  <Card title="Launch and operate" href="/en/kilatkoding/launch-checklists">
    Open the launch checklists, testing recipes, Vercel deployment, and operational runbook before going live.
  </Card>
</Columns>

## Available products

<Columns cols={2}>
  <Card title="KilatKoding" href="/en/kilatkoding">
    KilatKoding is a Next.js SaaS boilerplate designed to help you build faster, then adapt the product around your own business model.
  </Card>

  <Card title="Future products will appear here">
    The portal structure, language setup, and navigation are already separated by product, so new docs can be added without disrupting KilatKoding.
  </Card>
</Columns>

## If you only have 10 minutes

1. Open [KilatKoding](/en/kilatkoding) to see the main overview and reading paths.
2. Read [KilatKoding use cases](/en/kilatkoding/use-cases) to decide whether the boilerplate fits your product.
3. Check [What you can do without code vs what needs a developer](/en/kilatkoding/no-code-vs-developer) to set team expectations early.
4. Continue to [Getting started](/en/kilatkoding/getting-started) when you are ready to begin setup.

## About the documentation scope

This public documentation reflects the `kilatkoding-src` repository as of March 19, 2026. If the source code changes later, you can update the KilatKoding pages without changing the multi-product portal structure.

<Tip>
  If you add more products later, keep the same pattern: one product, one dedicated top-level menu, and one clear journey from overview to operations.
</Tip>