Migrate your Project Handbook data
GNOME's publicly-maintained internal knowledge base, not a project management tool. Contains no exportable data model or migration API.
In its favor
Why people choose Project Handbook
The signal that keeps Project Handbook on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Publicly accessible without authentication, so contributors and onlookers can reference governance, processes, and onboarding without an account.
Backed by Git (gitlab.gnome.org) which gives the underlying content full version history, review process, and merge-request workflow available to any GNOME contributor.
Static-site hosting means zero ongoing operational cost beyond GitLab Pages — appropriate for a volunteer-maintained free-software project.
Centralizes GNOME project governance documentation that would otherwise be spread across wikis, mailing lists, and individual repositories.
Open contribution model — anyone can propose changes to handbook content via merge requests in the source repository.
Not a project management tool — anyone arriving expecting tasks, assignees, or workflow tracking will find only static documentation.
No data model means there is no migration source — confusing this site with a real PM platform leads to mis-scoped migration projects.
Read-only published content; updates require Git access to the underlying repository, which excludes non-technical contributors.
No comment or discussion system on the published site — any conversation about content happens elsewhere (mailing lists, Matrix, GitLab merge requests).
Search and discoverability are limited to in-page browser search; no full-text search index or API is exposed.
Reasons to switch
Why people leave Project Handbook
The recurring reasons buyers give for replacing Project Handbook. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Project Handbook fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Project Handbook pricing overview
Project Handbook is GNOME's free, publicly hosted handbook site. There is no commercial product, no licence fee, and no published pricing model — it is a community-maintained open-source documentation project hosted on GitLab Pages. Users access it without sign-up at no cost.
Open access (no commercial product)
Tier 1 of 1
$0
What's included
Need help selecting your Project Management?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Project Handbook's schedule — see our quote-based pricing →
What gets migrated
Project Handbook object support
Object-by-object support for Project Handbook migrations. Per-pair details surface during scoping.
Pages
Not in this platformThe handbook consists of static markdown and HTML pages published to handbook.gnome.org. There is no database, no user accounts, and no structured object schema to map. We cannot extract records for import into any destination platform.
Users
Not in this platformNo user accounts are stored by the handbook. It is publicly readable with no authentication layer. There are no contacts, assignees, or owner records to migrate.
Attachments
Not in this platformWhile the handbook may link to external assets, there is no file management system or attachment object exposed via the site. No file migration path exists.
Custom Fields
Not in this platformNo custom field schema exists on this platform. The handbook is a static documentation site, not a structured database.
Labels/Tags
Not in this platformThe handbook uses standard markdown categories and GNOME wiki-style tags for navigation, but these are not structured data objects and cannot be exported as tagged records.
Comments
Not in this platformThe handbook does not have a comment system. It is read-only published content. There are no conversation records to migrate.
Search
Not in this platformNo search index export exists. The site provides in-browser search (typically Lunr.js) scoped only to the live session. There is no API or dump mechanism to retrieve search data.
Revisions
Not in this platformWhile the underlying content is version-controlled in GitLab's own repository (gitlab.gnome.org), the published handbook at handbook.gnome.org does not expose revision history as an accessible data object.
| Object | Support | Notes |
|---|---|---|
| Pages | Not in this platform | The handbook consists of static markdown and HTML pages published to handbook.gnome.org. There is no database, no user accounts, and no structured object schema to map. We cannot extract records for import into any destination platform. |
| Users | Not in this platform | No user accounts are stored by the handbook. It is publicly readable with no authentication layer. There are no contacts, assignees, or owner records to migrate. |
| Attachments | Not in this platform | While the handbook may link to external assets, there is no file management system or attachment object exposed via the site. No file migration path exists. |
| Custom Fields | Not in this platform | No custom field schema exists on this platform. The handbook is a static documentation site, not a structured database. |
| Labels/Tags | Not in this platform | The handbook uses standard markdown categories and GNOME wiki-style tags for navigation, but these are not structured data objects and cannot be exported as tagged records. |
| Comments | Not in this platform | The handbook does not have a comment system. It is read-only published content. There are no conversation records to migrate. |
| Search | Not in this platform | No search index export exists. The site provides in-browser search (typically Lunr.js) scoped only to the live session. There is no API or dump mechanism to retrieve search data. |
| Revisions | Not in this platform | While the underlying content is version-controlled in GitLab's own repository (gitlab.gnome.org), the published handbook at handbook.gnome.org does not expose revision history as an accessible data object. |
Gotchas
What to watch for in Project Handbook migrations
Issues we've hit on past Project Handbook migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Handbook is static content, not a database
No migration target either — it is not a destination platform
GNOME's real project management lives in GitLab
| Severity | Issue |
|---|---|
| High | Handbook is static content, not a database |
| High | No migration target either — it is not a destination platform |
| Medium | GNOME's real project management lives in GitLab |
Leaving Project Handbook?
Where Project Handbook customers move next
5 destinations Project Handbook can migrate to.
How a Project Handbook migration works
Four steps, Project Handbook-specific
Connect
Not applicable — site is publicly accessible static content with no authenticated API surface into Project Handbook. Scopes limited to read-only on the data we move.
Map
We translate Project Handbook-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Project Handbook quirks before production.
Migrate
Full migration with Project Handbook rate-limit handling. Rollback available throughout.
FAQ
Project Handbook migration FAQ
Answers to the questions buyers ask most during Project Handbook migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Project Handbook migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther project management tools we support
Ready when you are
Migrate Project Handbook.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Project Handbook setup and destination — written quote back within a business day.