wooldridge
A textbook data package whose whole job is to stay installable, and whose releases prove how much work that is.
Comparison · Infra & APIs
GitBook vs projoint
A side-by-side editorial comparison of GitBook and projoint — release velocity, themes, recent moves, and the top alternatives to consider.
GitBook vs projoint: at a glance
| Feature | GitBook | projoint |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 5.0 | 2.5 |
| Sparks · 30d | 0 | 0 |
| Top themes | ai-agent, documentation, reusable-content, change-requests | conjoint-analysis, survey-research, qualtrics, cran |
| Last editorial update | 1mo ago | 59m ago |
| Website | — | Visit → |
What is GitBook?
GitBook is quietly building an in-editor docs agent and hardening reusable-content workflows.
GitBook ships weekly, and two threads dominate: the GitBook Agent (its in-editor AI) and reusable/change-request tooling. Recent releases let the Agent hold multiple chats per change request, read and set variables across docs, and handle more complex multi-step edits, while change requests gained diffs for reusable blocks and integration blocks inside reusable content. An API to update change-request content rounds out a docs-as-code posture.
What is projoint?
projoint spent a year on CRAN paperwork, then shipped a correctness fix it flagged itself.
projoint is an R package for analysing conjoint survey experiments, covering Qualtrics import, reshaping, and quantity-of-interest estimation with inter-rater reliability correction. Most of its release history is CRAN admission work — citation formats, DESCRIPTION fields, \value{} tags, vignette cleanups — with four tags backfilled within ninety seconds of each other on 15 July in non-monotonic version order, so neither tag order nor timestamps in this feed track the real sequence. The substantive releases are the ones fixing data-preparation bugs that silently corrupt estimates.
GitBook vs projoint: editorial side-by-side
GitBook
5.0INFRA · APIS
GitBook is quietly building an in-editor docs agent and hardening reusable-content workflows.
◆ Current state
GitBook ships weekly, and two threads dominate: the GitBook Agent (its in-editor AI) and reusable/change-request tooling. Recent releases let the Agent hold multiple chats per change request, read and set variables across docs, and handle more complex multi-step edits, while change requests gained diffs for reusable blocks and integration blocks inside reusable content. An API to update change-request content rounds out a docs-as-code posture.
◆ Where it's heading
The direction is an authoring surface where an AI agent does structural work — updating variables everywhere, executing multi-step edits — inside a reviewable change-request flow, and where content can be automated via API from CI/CD. GitBook is positioning itself less as a docs editor and more as a governed, agent-assisted documentation pipeline.
◆ Prediction
Expect continued GitBook Agent capability expansion (broader edit actions, deeper structural understanding) and more API coverage for change requests to support automated, pipeline-driven documentation updates.
projoint
2.5INFRA · APIS
projoint spent a year on CRAN paperwork, then shipped a correctness fix it flagged itself.
◆ Current state
projoint is an R package for analysing conjoint survey experiments, covering Qualtrics import, reshaping, and quantity-of-interest estimation with inter-rater reliability correction. Most of its release history is CRAN admission work — citation formats, DESCRIPTION fields, \value{} tags, vignette cleanups — with four tags backfilled within ninety seconds of each other on 15 July in non-monotonic version order, so neither tag order nor timestamps in this feed track the real sequence. The substantive releases are the ones fixing data-preparation bugs that silently corrupt estimates.
◆ Where it's heading
The maintainer is hardening the path from raw Qualtrics export to estimate, which is where conjoint analysis quietly goes wrong. Three separate releases fix that path: dropped respondent-level weights in organize_data(), repeated-task reshaping in reshape_projoint(), and choice-to-profile mapping in 1.1.3. Each fix now arrives with regression tests and stricter validation rather than just a patch, and 1.1.3 adds an explicit .choice_map so the mapping is auditable instead of inferred.
◆ Prediction
Expect the validation-and-regression-test pattern to keep extending across the import path, with releases continuing to arrive in bursts around CRAN submission rather than on a cadence.
Alternatives to GitBook and projoint
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either GitBook or projoint.
L1centrality
A graph-centrality package that spent 2026 making its existing measures usable at scale, then went quiet.
exametrika
A test-theory package that grew into a graphical-model toolkit, now spending its releases paying down the API debt that growth created.
nuggets
nuggets keeps compounding on the 2.0 rewrite — more pattern families, lighter install.
eratosthenes
eratosthenes spends 0.1.0 hardening inputs rather than adding chronology methods.
dqcheckr
dqcheckr adds drift analysis, then removes the YAML a user had to hand-write.
See all GitBook alternatives → · See all projoint alternatives →
Recent activity from GitBook and projoint
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 17d agoprojointExplicit .choice_map guards choice-to-profile mapping
- 1mo agoprojointCRAN submission housekeeping for DESCRIPTION and examples
- 1mo agoprojointCRAN formatting pass; minor make_projoint_data() fix
- 1mo agoprojointreshape_projoint() repeated-task bug fixed; validation tightened
- 1mo agoprojointCitation metadata updated with the CRAN DOI
- 1mo agoGitBookUpdate change request content via the API
- 2mo agoGitBookMultiple AI chats per change request
- 2mo agoGitBookGitBook Agent can now work with variables
- 2mo agoGitBookReusable content diffs in change requests
- 2mo agoGitBookImproved GitBook Agent inside the editor
- 3mo agoGitBookIntegration blocks inside reusable content
- 5mo agoprojointorganize_data() no longer drops respondent-level weights
Frequently asked questions
What is the difference between GitBook and projoint?
They serve adjacent needs but don't currently overlap on shipped themes. GitBook is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is GitBook better than projoint?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. GitBook is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to GitBook?
Top GitBook alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "GitBook alternatives" section above for the current picks, or visit /alternatives/gitbook for the full list with editorial commentary on each.
What are the best alternatives to projoint?
Top projoint alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "projoint alternatives" section above for the current picks, or visit /alternatives/projoint for the full list with editorial commentary on each.