Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

History / FAQ

Revisions

  • docs(wiki): GEO/AEO pass across all pages — answer-first intros, FAQs, question headings Optimize every wiki page for AI answer engines (GEO/AEO) and classic SEO, additively — all facts, commands, config keys, defaults, and links preserved: - Answer-first, self-contained intros so each page stands alone if an AI surfaces it with no other context (each restates what blumi is in one clause). - TL;DR / "Key facts" blocks of atomic, extractable facts near the top. - Question-style headings ("What is X?", "How do I Y?") matching natural queries. - A FAQ (Q&A) section on each substantive page — the most AI-citable format. - Consistent entity naming + acronyms expanded on first use (RAG, SEDM, RPL, BYOK, mDNS, FCM, STT/TTS, ...). - Fixed stale version (0.3.0 -> 0.5.0) on Home. Co-Authored-By: Blumi <ankur.nairit@gmail.com>

    @ankurCES ankurCES committed Jun 8, 2026
  • docs: add FAQ (decision-maker + developer lenses), grounded in the code A new FAQ page answering the questions that actually come up — "why blumi / what does it cost / where does our data go / vendor lock-in" for decision-makers, and "which providers, offline use, sandboxing, extensibility, the grid, memory, GPU, autonomy guardrails" for developers — plus the connectivity questions (the Tailscale/MagicDNS one, FCM-from-anywhere) and security/privacy. Every answer is grounded in shipped behavior (crates, config keys, executors, auth). Linked from the sidebar, Home guide table, and Home footer. Co-Authored-By: Blumi <ankur.nairit@gmail.com>

    @ankurCES ankurCES committed Jun 7, 2026

AltStyle によって変換されたページ (->オリジナル) /