-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Add ‘Next steps’ tip to WYSIWYG editor documentation #2851
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
Conversation
This file contains hidden or 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
…, services, middlewares, routes)
…, secrets manager)
…tizeOutput when overriding actions
…me.dark overrides
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
|
pwizla
added a commit
that referenced
this pull request
Nov 20, 2025
…2851) * docs(backend): correct TypeScript code fences in TS tabs (controllers, services, middlewares, routes) * docs(bundlers): clarify webpack config example rename and JS/TS filenames * docs(routes): add guidance to prefer fully-qualified handler names in custom routers * docs(api-tokens): add concise security tip (least privilege, rotation, secrets manager) * docs(controllers): add caution about validateQuery/sanitizeQuery/sanitizeOutput when overriding actions * docs(policies): clarify scoped policy folders and fix example path * docs(webhooks): add signature verification tip and fix TS config path * docs(theme-extension): add minimal TS example for theme.light and theme.dark overrides * docs(wysiwyg): add next steps tip (plugin first, custom field for deeper integration) * Limit PR scope based on title; keep only intended doc(s); revert unrelated files --------- Co-authored-by: GitHub Actions <noreply@github.com>
pwizla
added a commit
that referenced
this pull request
Nov 20, 2025
…2851) (#2859) * docs(backend): correct TypeScript code fences in TS tabs (controllers, services, middlewares, routes) * docs(bundlers): clarify webpack config example rename and JS/TS filenames * docs(routes): add guidance to prefer fully-qualified handler names in custom routers * docs(api-tokens): add concise security tip (least privilege, rotation, secrets manager) * docs(controllers): add caution about validateQuery/sanitizeQuery/sanitizeOutput when overriding actions * docs(policies): clarify scoped policy folders and fix example path * docs(webhooks): add signature verification tip and fix TS config path * docs(theme-extension): add minimal TS example for theme.light and theme.dark overrides * docs(wysiwyg): add next steps tip (plugin first, custom field for deeper integration) * Limit PR scope based on title; keep only intended doc(s); revert unrelated files --------- Co-authored-by: GitHub Actions <noreply@github.com>
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: chore
source: repo
PRs/issues not targeting a specific documentation but rather affecting the whole repo
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.
This PR adds a “Next steps” tip to the WYSIWYG editor documentation about choosing a plugin vs a custom field.