-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
create update page init #2321
Draft
Boegie19
wants to merge
153
commits into
strapi:main
Choose a base branch
from
Boegie19:create-update-page
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
create update page init #2321
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This double dot seems to be wrong. Tested it locally
Change sequence of lines
Before the change we have one ul per line
* Fixing the table of links in the rest api documentation * String to specify the default behavior when creating a document * Updating the links in the sidebar, too * copy fix
I'm proposing this rather than asking a question about the license. I wasn't able to find an ee directory in the repo (maybe I missed it!) so I thought this might help you.
* Fixing the table of links in the rest api documentation * String to specify the default behavior when creating a document * Updating the links in the sidebar, too * publishedAt breaking change * Update docusaurus/docs/dev-docs/api/rest.md * Update docusaurus/docs/dev-docs/api/rest.md * Rename file and add it to BC list --------- Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com> Co-authored-by: Pierre Wizla <pwizla+github@gmail.com>
Fix v4CompatibilityMode flag name in step-by-step.md
The space separator between the key and the value has been deprecated; instead, use the format "ENV key=value"
Correct flag name
strapi#2224) * Update configuring-view-of-content-type.md Because higher in that note it is said that “Only one field can be displayed per relational field.” * Address feedback from pwizla
* chore: deleted old cloud assets * fix: updated screenshots for design system v2 and new header
* Initiate pages in User Guide and Dev Docs * Add the Dev Docs part * Fix callout cross-linking dev docs and user guide * Add user guide draft * Improve Dev Docs intro. * Improve Dev Docs * Slightly improve User Guide * Add beta badge to Dev Docs * Add beta badge to User Guide * Fix: Use arraw for allowed origins Co-authored-by: Marc Roig <marc12info@gmail.com> * Update Open preview disabled/save changes behavior * Fix Dev Docs code (status) * Add front-end fetching to implementation guide * Improve URL handler * Update docusaurus/docs/dev-docs/preview.md * Update docusaurus/docs/dev-docs/preview.md * Add CSP directive in front end * Fix typo --------- Co-authored-by: Marc Roig <marc12info@gmail.com>
* Discard comment * Update prerequisites * Update feature flag doc
* Update the first message to remove v4 docs and to let users know that these docs are only for JS strapi projects * Remove the testEnvironment key because it's already set to the Jest default * Update setupStrapi function for Strapi 5 * Remove the unneeded fs module import at the top of this example * It's important to add this so that the correct database config file is used. * Change callout at the top of the page
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Thanks, @Boegie19, that's a good idea. You can go ahead. However please note that I'm in vacation very soon and the |
pwizla
added
source: Dev Docs
PRs/issues targeting the Developer Docs
pr: updated content
PRs updating existing documentation content
temp: port to doc6
(Temporary label) The content of this PR should be ported to Strapi Docs v6
labels
Dec 16, 2024
Okay NP thanks for the info and Happy holidays 🎅 |
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: Dev Docs
PRs/issues targeting the Developer Docs
temp: port to doc6
(Temporary label) The content of this PR should be ported to Strapi Docs v6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
node for pwizla tell me if you want this or if you want it in an other way or not at all.
What does it do?
Add a create and update page to both api and document service
Why is it needed?
The docs never make clear how to create or update dynamic zones for example.
Related issue(s)/PR(s)
#2327