---
title: STARTER KIT — ROADMAP
slug: starter-kit-roadmap
layer: STARTER KIT
layer_order: 11
order: 111
description: Release path for the kit — private template zip first, then a workshop resource, then a possible open-source core.
---

> **FLUX DOCUMENTATION SYSTEM**
> Layer 11 — STARTER KIT | starter-kit-roadmap
> flux.dantesisofo.com/wiki/starter-kit-roadmap/

# STARTER KIT — ROADMAP

How the blueprint becomes a thing students can use, in increasing order of
openness and risk.

---

## 1. STAGE 1 — PRIVATE TEMPLATE (START HERE)

A private template repo or downloadable zip, access-controlled.

- **Why first:** you keep control while iterating; identifiers are still being
  externalized; lowest exposure risk.
- **Contents:** the reusable code ([TEMPLATE KIT PLAN](../starter-kit-template-plan/)),
  the six docs, `.env.example`, sample walk, empty catalog seed.
- **Gate:** passes the [sanitization checklist](../starter-kit-security/).
- **Validation:** a fresh machine + a throwaway bucket completes name → upload →
  generate → publish using only the docs.

---

## 2. STAGE 2 — WORKSHOP RESOURCE (BEST VALUE FIT)

The strongest fit for the *teaching* value. The code is reusable, but the real
lesson is **AWS setup + the workflow + the information-architecture concepts**
(routes-on-hub vs photos-on-pages, canonical naming, static-first hosting).

- Bundle the private template + the docs + a guided walkthrough (recorded or live).
- Students leave with their **own** city-in-flux archive deployed on their **own**
  bucket.
- Natural place to charge: the outcome (a live, owned archive) is concrete.

---

## 3. STAGE 3 — POSSIBLE OPEN-SOURCE CORE (LATER)

A stripped public "geotag static publisher" core, *after*:

- a full security pass (no secrets anywhere; fresh repo so there's no history),
- a decision on how much of the canonical-naming/hub design to give away,
- a clean split: **permissive license (e.g. MIT) on the code**, with **content,
  brand, and personal data excluded**.

Open source is good for reach/marketing; it is the last step, not the first.

---

## 4. RECOMMENDATION

**Private template + paid workshop now; consider a public core later.**

This keeps the proprietary FLUX systems ([excluded list](../starter-kit-template-plan/))
private, monetizes the teaching, and leaves the open-source door open once the
sanitization is proven.

---

## 5. BUILD ORDER (WHEN GREENLIT)

1. New clean directory (not the working tree — avoids huge media + any history).
2. Copy only the reusable core.
3. Externalize all hardcoded identifiers into one config module + `.env`.
4. Add `.env.example`, `.gitignore`, empty catalog seed, `sample_walk/`.
5. Strip optional/personal features (email, the proprietary FLUX systems).
6. Write the six docs (derived from this wiki section) + a thin `flux` CLI.
7. Dry-run the full pipeline against a throwaway test bucket to prove the student
   happy path before any release.

---

See also: [OVERVIEW](../starter-kit-overview/) ·
[ARCHITECTURE](../starter-kit-architecture/) ·
[WORKFLOW](../starter-kit-workflow/) ·
[SETUP](../starter-kit-setup/) ·
[SECURITY](../starter-kit-security/) ·
[TEMPLATE PLAN](../starter-kit-template-plan/)

---

FLUX_WIKI_v2.0 — flux.dantesisofo.com/wiki/starter-kit-roadmap/