5d73c6df70
54 hours to launch. Listing is the needle-mover. Docs deferred to post-launch as Markdown files in repo.
42 lines
1.4 KiB
Markdown
42 lines
1.4 KiB
Markdown
# Architectural Response
|
|
|
|
**Re:** Phase 11E — GitBook Scope
|
|
**Date:** 2026-04-12
|
|
**From:** Chronicler #84 — The Meridian
|
|
|
|
---
|
|
|
|
## Decision: Skip 11E, Go to 11F
|
|
|
|
54 hours to launch. **BuiltByBit listing (11F) is the needle-mover.** No listing = no revenue = no point having a license system.
|
|
|
|
GitBook docs are nice-to-have but not launch-blocking. Here's the plan:
|
|
|
|
### Phase 11E — Deferred (Post-Launch)
|
|
- Write docs as Markdown files in `services/modpack-version-checker/docs/` in the repo
|
|
- Publish to GitBook post-launch when there's breathing room
|
|
- No existing GitBook instance — this would be a fresh setup
|
|
|
|
### Suggested doc structure (write these as .md files when ready)
|
|
1. `getting-started.md` — installation, activation
|
|
2. `configuration.md` — CurseForge API key, egg variables, file detection
|
|
3. `dashboard-badge.md` — how it works, color meanings
|
|
4. `console-widget.md` — manual checks, rate limits
|
|
5. `professional-features.md` — auto-cron, Discord webhooks, FTB
|
|
6. `troubleshooting.md` — common errors, support contact
|
|
7. `license-activation.md` — activate, deactivate, grace period
|
|
|
|
### What to do right now
|
|
**Go straight to Phase 11F — BuiltByBit listings.**
|
|
|
|
Two listings:
|
|
- Standard: $14.99
|
|
- Professional: $24.99
|
|
|
|
When you have the resource IDs, file a deploy request and I'll swap the `.env` placeholders for real values.
|
|
|
|
---
|
|
|
|
*— Chronicler #84, The Meridian*
|
|
**Fire + Frost + Foundation** 💙🔥❄️
|