Documentation, connected navigation, and clearer errors

This week's updates make Openstead easier to learn and navigate, with a dedicated documentation site and clearer information when something goes wrong. This entry includes changes released on September 28.

AddedCopy Anchor Link

• A dedicated documentation site. The initial release brings together 109 pages covering services, frameworks, private databases, networking, Blueprints, developer tools, workspaces, and billing. Start with your first deployment, choose a service type, or jump into a framework guide such as Laravel, Django, or Next.js.

• An API reference for all 28 core operations. Each endpoint page includes its method, request fields, responses, and code examples. The interactive playground sends requests to the real Openstead API, with a workspace key for authenticated operations. Review the operation before sending a request that changes a resource.

• Search and Markdown access. Search across guides and reference pages, use the page outline to move through longer articles, or copy a page as Markdown. The documentation index and complete Markdown export make the same material available to developer tools, including useful endpoint details and referenced schemas.

ImprovedCopy Anchor Link

• Documentation where you need it. The marketing website and console help now link to the hosted documentation. Product pages lead to relevant guides, and existing documentation links redirect to the new site.
• Website navigation for signed-in users. After your console session is confirmed, the marketing header shows Dashboard in place of Log in and Sign up. Session checks happen in the background without delaying the page.
• Clearer service and pricing information. Website content now explains the services offered in the console, resource pricing, and monthly renewal behavior. USD checkout and illustrative NGN budget estimates are distinguished, with persistent-storage costs included in the calculator.
• Consistent platform failure pages. Missing-page and runtime failures across the website and console use a shared presentation. Hosted gateway failures show a clear status and next step; when a request reference is available, it can help support identify that failure. Your application's own responses and custom error pages remain under your control. Troubleshoot a deployment.

FixedCopy Anchor Link

• Static-site platform fallbacks. Corrected the routing used to serve platform error responses for static deployments, while retaining custom 404.html pages and SPA routing behavior.
• Usable API examples from the first render. Reference examples use the Openstead API URL and clearly marked credential placeholders. Markdown copies include endpoint parameters, request and response information, rather than an empty component placeholder.