Strapi documentation doesn't talk about good practices of running Strapi in cluster mode, that is one of the cases to optimize and take advantage of your server, where you can use the pm2, like the docs already mention. Could one of you create a section to talk about cluster mode best practices in the documentation please? I don't know if it's relevant, but in my tests, I already have some errors like "sorry, too many clients already" when running more than 9 instances in cluster mode. from: https://github.com/strapi/strapi/issues/13237#issuecomment-1228958677

To add and use the lifecycles in a plugin created content type, you need to add lifecycles to the content type folder as written in the docs. But you also need to import the "lifecycles" file in the index file. I could not found this information in the docs.

A lot of tutorials online mention imports of functions from @strapi/utils, but there is no official documentation for the module. Also, the API documentation does not fully describe properties of the strapi object. Can we please add docs for these and any other modules that might be used by developers creating custom Strapi logic?

at the moment there is no documentation on how you can add new queries/mutations, how you can implements resolvers and return values

I think strapi should allow to create custom pages like in our case, guidelines page on how to add content

Can you explain this: https://docs.strapi.io/dev-docs/custom-fields#registering-a-custom-field-in-the-admin-panel:~:text=Though%20the%20recommended%20way%20to%20add%20a%20custom%20field%20is%20through%20creating%20a%20plugin%2C%20app%2Dspecific%20custom%20fields%20can%20also%20be%20registered%20within%20the%20global%20register%20function%20found%20in%20src/index.js%20and%20src/admin/app/js%20files . I'm struggling to find anything that could describe how can we implement a custom field with the src/index.js file without having to create a plugin, but I don't find anything on the web.

There's no documentation on how does one add custom policy for a User collection route like update or delete. I am building an app and I need to make sure that an authenticated user can only update/delete their own data. And for that, I need to add a policy to the update/delete route for the users-permissions plugin. But there's no documentation for it.

How to make single-type dynamic zones

Configuration docs explain how to configure plugins.js using env vars, however they say to hardcode values in middlewares.js. I suggest to update docs to something similar to the following, to have values in a single place (not hardcoded). I have it already working properly. module.exports = ({ env }) => ([ // ... { name: 'strapi::security', config: { contentSecurityPolicy: { useDefaults: true, directives: { 'connect-src': ["'self'", 'https:'], 'img-src': [ "'self'", 'data:', 'blob:', env('AWS_BUCKET') + '.s3.' + env('AWS_REGION') + '. amazonaws.com ', ], 'media-src': [ "'self'", 'data:', 'blob:', env('AWS_BUCKET') + '.s3.' + env('AWS_REGION') + '. amazonaws.com ', ], upgradeInsecureRequests: null, }, }, }, }, // ... ]);

I am trying to disable introspection on graphql queries through strapi. I added the configuration in config/plugin.js graphql: { endpoint: "/graphql", tracing: false, shadowCRUD: true, playgroundAlways: false, depthLimit: 7, amountLimit: 100, apolloServer: { introspection: false, }, }, But this has no effect at all