Feature Inventory¶
This page tracks the user-facing and agent-facing features that need product documentation. It should be updated whenever a feature is added, renamed, or removed.
User-Facing Features¶
| Feature area | What users can do | Documentation page | Status |
|---|---|---|---|
| Access and organizations | Choose or create an organization, accept invitations, and request access to restricted Pages. | Access And Organizations | Code-checked |
| Home and navigation | See activity, use search, and move between Home, Pages, Turner, Agents, Settings, and Trash when allowed. | Workspace Navigation | Code-checked |
| Pages | Browse, search, filter, open, share, duplicate, upload files or folders to publish directly, and trash Pages. | Pages Library | Code-checked |
| Page capacity | Understand included Page capacity, upload continuations, multi-route Pages, and plan limits. | Page Capacity | Code-checked |
| Page activity | Review Page-level publish, access, conflict, and revision history. | Page Activity | Code-checked |
| Viewer analytics | Review Page opens and reading activity when analytics is enabled and permitted. | Viewer Analytics | Code-checked |
| Presentation controls | Turn an eligible published Page into a deck-style presentation and request a repair when needed. | Present a Page | Code-checked |
| Showcase copies | Copy a public Showcase Page into an organization. | Copy a Showcase Page | Code-checked |
| Design a Page | Chat with Turner, SecondPage's design assistant, to describe a Page, answer follow-up questions, and review generated drafts from the Turner work repository. | Design a Page | Code-checked |
| Review and revise | Leave feedback, review changes, and keep revisions attached to a Page. | Review And Revise | Code-checked |
| Sharing and visibility | Choose private, organization, or public access; use share controls. | Sharing And Visibility | Code-checked |
| Connections | Connect supported data sources so Pages can refresh from live data. | Connections | Code-checked |
| Custom domains | Add domains, follow DNS setup, verify status, and remove domains. | Custom Domains | Code-checked |
| Plans and billing | Review plan limits, availability, usage, and upgrade options. | Plans And Billing | Code-checked |
| Organization settings | Update organization profile, invite and manage members and roles, approve work-email join requests, choose auto-join domains, leave the organization, and delete the organization. | Organization And Members | Code-checked |
| Account settings | Manage profile, email, security, sessions, and sign out. | Account Settings | Code-checked |
| Comment email preferences | Choose immediate or daily email summaries for untagged comments on Pages you own. | Comment Email Preferences | Code-checked |
| Audit log | Review organization events by actor and object. | Audit Log And Trash | Code-checked |
| Trash | Restore trashed Pages when permitted. | Audit Log And Trash | Code-checked |
Agent-Facing Features¶
| Feature area | What agents/developers can do | Documentation page | Status |
|---|---|---|---|
| Agent onboarding | Decide when to use SecondPage and discover machine-readable docs. | Agent Overview | Code-checked |
| Agent management | Create agent records, review connection state, and remove or disconnect agents. | Manage Agents | Code-checked |
| MCP connection | MCP is the only customer-facing agent connection path: connect with OAuth sign-in, or an issued API key for headless runtimes that cannot complete OAuth. | Connect An Agent | Code-checked |
| Page publishing | Create, read, list, and update Pages over MCP, with inline bundles, Page upload continuations, and direct media uploads for larger image/video assets. | Publishing Flow | Code-checked |
| Design tools | Run design sessions, request hosted generation, or submit a bundle against a brief. | Design Tools For Agents | Code-checked |
| API keys | Issue, label, copy once, monitor, and revoke keys. | API Keys | Code-checked |
| Comment queue | Read assigned Page comments, filter by tagged agent, and include full thread context. | Comment Queue | Code-checked |
| Live-data connections | Help users connect data and bind Page content to supported sources. | Live Data For Agents | Code-checked |
| Page exports | Export a current Page in a supported format. | Page Exports | Code-checked |
| Agent mirrors | Consume llms.txt, skill.md, and manifest.json from the docs bundle. |
Agent Mirrors | Code-checked |
Maintainer note: legacy direct REST Page-publishing routes remain live and behaviorally unchanged behind the scenes, but keeping them undocumented and unadvertised to customers is a locked, approval-gated decision pending a live usage inventory and any needed migration notice. Do not add customer-facing instructions to call them directly.
Documentation Rules¶
- Write from the operator's point of view: what the user or agent can do next.
- Avoid implementation architecture, database names, secret names, and internal service boundaries unless they are required for product operation.
- Keep exact API shapes only in agent/developer pages.
- Re-check every page against the hidden verification notes in its frontmatter.
- Prefer short pages with clear steps over exhaustive reference prose.
Coverage Boundaries¶
This inventory covers customer-facing product workflows and agent-facing product workflows. It does not try to document internal admin consoles, cron jobs, webhook receivers, private health checks, QA harnesses, or implementation-only routes unless they become part of the normal customer or agent operating path.