Skip to content

Better explain the move to documentId #2604

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Jul 28, 2025

Conversation

pwizla
Copy link
Collaborator

@pwizla pwizla commented Jul 23, 2025

This PR aims at explaining why Strapi 5 moved from id to documentId.
It also mentions the max. character length of documentId.

The PR leverages the new ExpandableContent component that was recently created to give more context about this strategic
change from Strapi, the reasons behind it, and how best to handle the transition from previous versions.

Direct preview link 👉 here (click the "View more…" button to reveal all the added content 👀 )

@pwizla pwizla self-assigned this Jul 23, 2025
@pwizla pwizla requested a review from meganelacheny as a code owner July 23, 2025 12:51
@pwizla pwizla added pr: updated content PRs updating existing documentation content source: CMS labels Jul 23, 2025
Copy link

vercel bot commented Jul 23, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
documentation ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 23, 2025 0:51am

@pwizla pwizla added this to the 6.6.5 milestone Jul 23, 2025
@pwizla pwizla changed the title Cms/fix problem expand document service docs Better explain the move to documentId Jul 23, 2025
@pwizla pwizla merged commit d9bc1bd into main Jul 28, 2025
14 checks passed
@pwizla pwizla deleted the cms/fix-problem-expand-document-service-docs branch July 28, 2025 09:41
pwizla added a commit that referenced this pull request Jul 28, 2025
* Expand Document Service API introduction

* Improve formatting for additional resources in breaking change page

* Fine-tune introduction wording

* Mention why using documentId is recommended
pwizla added a commit that referenced this pull request Jul 28, 2025
* Expand Document Service API introduction

* Improve formatting for additional resources in breaking change page

* Fine-tune introduction wording

* Mention why using documentId is recommended
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr: updated content PRs updating existing documentation content source: CMS
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant