Structure and contribution
Organize spaces, page groups, and navigation around your products and reader tasks. Agree how writers and engineers review and publish changes.
Set up and improve GitBook documentation with clear navigation, API references, Git Sync, and a publishing workflow your team can run.
Organize spaces, page groups, and navigation around your products and reader tasks. Agree how writers and engineers review and publish changes.
Connect GitHub or GitLab where needed. Configure OpenAPI references, check imported content, and review how edits move between GitBook and your repository.
Configure supported branding, publishing settings, and your domain. Validate links and navigation, coordinate launch, and train the team within the capabilities of your GitBook plan.
Yes. We review your spaces, navigation, contribution workflow, API specifications, and publishing settings. The proposal defines the implementation, acceptance checks, responsibilities, and project price. GitBook subscriptions are separate.
Yes. Git Sync connects GitBook with GitHub or GitLab. We configure the repository and content mapping, agree the review workflow, and check synchronization in both directions with your team.
We work with GitBook’s supported branding, layout, and integration options. We check your requirements against the selected plan before committing to a design or access workflow.
Documentation migrations covers source assessment, content conversion, navigation, references, redirects, and launch. We review reusable content, components, and old URLs before agreeing the migration scope.
Docs Ops provides agreed capacity for publishing issues, reference updates, integrations, and planned improvements.