Introduce slim documents

[gregberge]

We introduce slim documents, it's a lighter version of the document
computed in GitBook Open to lightweight to document stored in cache and
transferred to client. The idea is to store in this document only what
is needed to display a document in GitBook Open.

Fix RND-6822

[changeset-bot]

🦋 Changeset detected

Latest commit: 35dfe45

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
gitbook-v2	Patch
gitbook	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

Summary of the deployments:

Version 1

Version	URL	Status
Latest commit	https://1ba4e1bb.gitbook-open.pages.dev	✅
PR	https://pr3140.gitbook-open.pages.dev	✅

Version 2

Version	URL	Status
Vercel	https://gitbook-v2-a8185xh05-gitbook.vercel.app	✅
Cloudflare	https://dc76efb2-gitbook-open-v2-preview.gitbook.workers.dev	✅

Test content

Site	v1	2v	2c
GitBook	https://1ba4e1bb.gitbook-open.pages.dev/docs.gitbook.com	https://gitbook-v2-a8185xh05-gitbook.vercel.app/url/docs.gitbook.com	https://dc76efb2-gitbook-open-v2-preview.gitbook.workers.dev/url/docs.gitbook.com
E2E	https://1ba4e1bb.gitbook-open.pages.dev/gitbook.gitbook.io/test-gitbook-open	https://gitbook-v2-a8185xh05-gitbook.vercel.app/url/gitbook.gitbook.io/test-gitbook-open	https://dc76efb2-gitbook-open-v2-preview.gitbook.workers.dev/url/gitbook.gitbook.io/test-gitbook-open

[argos-ci]

The latest updates on your projects. Learn more about Argos notifications ↗︎

Build	Status	Details	Updated (UTC)
customers-v1 (Inspect)	✅ No changes detected	-	Apr 12, 2025, 6:32 PM
customers-v2 (Inspect)	✅ No changes detected	-	Apr 12, 2025, 6:33 PM
default (Inspect)	👍 Changes approved	4 changed	Apr 12, 2025, 6:34 PM
v2-vercel (Inspect)	✅ No changes detected	-	Apr 12, 2025, 6:36 PM

[emmerich]

My first thought is: why doesn't this live in the API?

[gregberge]

@emmerich it's tight to GBO and what we display in it. I think it's easier to maintain here. @SamyPesse didn't want it in the API

[linear]

RND-6822 Reduce inline props in client components to decrease page size

[SamyPesse]

@emmerich It should not be done in the API, because the choice of what data is important or not to be stored in the cache is relative to what GBO needs to do.

Our API should always respond with "all" the properties needed for different use-cases (some properties are useless on revision pages for GBO, but needed for our users using the API).

GBO can then choose to pick only some properties to select and cache; depending on what is being used.

In the API, we should just get rid of some deprecated properties on Revision.