-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
π Production hotfix: Upload providers links β Marketplace #1314
Merged
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
* Updated Heroku deployment documentation Added a line to recommend WSL for windows users on step 5 of the postgres setup, as that was something that would have saved me some time while following the guide. Also fixed a numbering error * Update docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/heroku.md Co-authored-by: Pierre Wizla <[email protected]> * Added multiple options for windows users on step 5 * Remove WSL suggestion and format as a tip Co-authored-by: Pierre Wizla <[email protected]>
* Update admin-customization.md for plugin translation Add instructions to admin-customization.md for extending a plugin's translations, which requires prefixing the key/value pair (declared in the plugin's translation file) with the plugin's name, for example `"content-type-builder.plugin.name": "Constructeur de Type-Contenu"` in order to translate the `plugin.name` key declared in `content-type-builder` plugin. This wasn't made clear by the documentation previously, since even for default plugins (such as content-type-builder) some fields are not translatable with the default method because they are declared independently in the plugin's files. I couldn't find any reference in the docs to the fact the plugin's name needed to be added as a prefix in order to extend a plugin's key. * Update docs/developer-docs/latest/development/admin-customization.md Co-authored-by: Pierre Wizla <[email protected]> Co-authored-by: Pierre Wizla <[email protected]>
* Support HTML in SidebarGroup title * Add hotjar * Delete SidebarGroup.vue
Latest Windows OS version is Windows 11
β¦ion.md Co-authored-by: Shaun Brown <[email protected]>
β¦ion.md Co-authored-by: Shaun Brown <[email protected]>
β¦ion.md Co-authored-by: Shaun Brown <[email protected]>
fix: typos fixed
Windows Desktop Recommended Version Correction
Modify api token v2 RBAC
Add callout for read-only API tokens
Bump dependencies version
update v4.2.x -> v4.3.x migration guide
fix: the youtube link for video demo is outdated
Add GraphQL Plugin config to TypeScript example similar to JavaScript
I follow the AWS guidelines for a fresh start. When I came to the pm2 step, I noticed some missing environment variables in ecosystem.config.js.
GCP deployment guide: add callout
This reverts commit 34f68ff.
* Update LTS version for node to include v18 * Update docs/developer-docs/latest/developer-resources/cli/snippets/installation-prerequisites.md Co-authored-by: Pierre Wizla <[email protected]> Co-authored-by: Pierre Wizla <[email protected]>
Update getting started guide to fit new strapi response format and describe new Nuxt 3 features.
* Fix missing opening tag for the code block * Fix missing file prefix
The latest updates on your projects. Learn more about Vercel for Git βοΈ
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
internal
PRs created by the Strapi core team
pr: updated content
PRs updating existing documentation content
size: small
If the PR includes only 1 file with <10 lines of text or a small code fix
source: Dev Docs
PRs/issues targeting the Developer Docs
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.
Replace AWS S3 and Cloudinary links in Upload plugin dev docs