[experimental] Add ‘Next steps’ tip to WYSIWYG editor documentation (#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 <[email protected]>

Author: pwizla

docusaurus/docs/cms/admin-panel-customization/wysiwyg-editor.md

@@ -15,3 +15,7 @@ Strapi's [admin panel](/cms/admin-panel-customization) comes with a built-in ric
 
 - You can install a third-party plugin, such as one for CKEditor, by visiting <ExternalLink to="https://market.strapi.io/" text="Strapi's Marketplace"/>.
 - You can create your own plugin to create and register a fully custom WYSIWYG field (see [custom fields documentation](/cms/features/custom-fields)).
+
+:::tip Next steps
+When evaluating editors, start with a plugin from the Marketplace for a quick trial, then consider a custom field if you need deeper integration (schema, validation, or custom toolbar behavior).
+:::