Skip to content

There is no getting-started path for ObjectOS itself: Quickstart boots the open runtime, Deploy/Operate are not marked self-managed, and License & Pricing is buried #300

Open

Description

@objectstack-fleet

Found by the seat's site-wide audit of docs.objectos.ai on 2026-10-06, which built main @ b754364. Priority: P1.

What a new visitor finds

  • Quickstart, the only "start" page, boots ObjectStack and says "ObjectOS itself needs none of it".
  • No Cloud page: there is no "Start on ObjectOS Cloud" page.
  • Deploy and Operate apply only to self-managed installs, and nothing labels them that way.
  • Configure mixes Cloud admin tasks (users, permissions) with self-managed infrastructure (runtime, data sources, storage).
  • Sidebar order:
    • "Extend Existing Systems", which describes itself as early, sits above Quickstart.
    • License & Pricing is inside the collapsed Resources group.
  • Edition names disagree. The docs call the self-managed edition both "ObjectOS Enterprise" (positioning.ts, index, why, architecture, quickstart, faq, glossary, security) and "ObjectOS Self-Managed" with two plans under it (license.mdx:8-10, deploy/index.mdx:3-6, deploy/docker.mdx).

Blocked on two maintainer decisions

Blocked-by: #295
Blocked-by: objectstack-ai/www.objectos.ai#215

This card is pm:blocked until both are answered.

Done looks like (once unblocked)

Surface

content/docs/**/meta.json (sidebar), content/docs/quickstart.mdx, a new content/docs/start-cloud.mdx (name is the dev's call), content/docs/deploy/index.mdx, content/docs/operate/index.mdx, content/docs/configure/*.mdx (labels only), and apps/docs/lib/positioning.ts with its gate if the vocabulary changes.


Generated by Claude Code

Activity

  1. objectstack-fleet commented on Oct 12, 2026

    @objectstack-fleet
    ContributorAuthor

    Half-state repair: a Blocked-by: line for each named blocker · 2026-10-12T11:31Z

    repo:objectos PM seat (objectstack-ai/objectstack#9831), R1, session session_01H1D12NQAtnCRwY1YzR43Vd.

    This card carried pm:blocked but no line-anchored Blocked-by: line. Its two blockers appeared only in prose, which the unlock scan's reverse index rejects by design. The scan could therefore never return this card to pm:queue.

    The body now carries both lines, above the sentence that already named them:

    • Blocked-by: #295. Read just before this comment: open, needs-user-decision.
    • Blocked-by: objectstack-ai/www.objectos.ai#215. This session cannot read that repository's issues API, so its state is not verified here.

    ⛔ This is not a re-triage. Priority, scope and labels are unchanged; the only body change is the two added lines. The card returns to pm:queue only when both targets close.


    Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions