G-Starlink Handbook
This is the single source of truth for how G-Starlink operates. Everything β from how we handle B2B orders, to our product data model, to how the three-location team collaborates β lives here.
We follow a handbook-first approach inspired by GitLab: if something has been asked twice, it belongs in this handbook. If a decision was made, it belongs in this handbook. The chat thread, email, or meeting is the process; the handbook is the outcome.
How this site is organized
The handbook is divided into seven modules. Each has its own maintainer and rhythm.
Mission, org chart, remote collaboration norms, maintainer guide.π’ CompanySOPs for order handling, B2B reseller workflows, fulfillment.βοΈ OperationsResponse SLAs, FAQ, escalation paths, scripts.π¬ Customer ServiceProduct catalog, SKU naming, carrier codes, pricing structure.π± ProductSystem architecture, deployment, credentials (internal only).π TechGoogle Ads, SEO, email/SMS automation, content calendar.π£ MarketingOnboarding, working hours, performance, offboarding.π₯ People
Two audiences, one source
This handbook is built twice from the same source code:
- Internal build (
handbook.gstarlink.com) β everything. Protected by Cloudflare Access. - Public build (
docs.gstarlink.com) β only pages markedpublic: truein their frontmatter. No authentication, indexable by Google.
Content authors donβt choose which site a page goes to β they set public: true or public: false in the frontmatter and the build pipeline sorts it out.
Three rules for everyone
- If you were asked a question twice, write the answer here. Next time, send the link.
- Write decisions, not just chat. After any Slack thread that concludes with βOK, letβs do X,β someone writes X down here.
- Edit freely. This is a working document, not a sacred text. If something is wrong, fix it.
Canβt find what you need?
- Use the search box at the top
- Check the sidebar for the module most relevant to your question
- Still nothing? Ask in
#generalon Slack and whoever answers must also write the answer here before closing the conversation.