Documentation

It would be helpful to mention how many characters a "Short text" field can hold (apparently 255) and how many characters a "Long text" can hold. The docs currently only mention the following: "Choose between Short text and Long text, to allow more or less space to fill up the Text field." https://docs.strapi.io/user-docs/content-type-builder/configuring-fields-content-type#regular-fields

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

I have strapi application running on port 1337 then I have a next js project running on 3000, Is there any possible way so that I can combine my both application and fire my next js project from strapi port 1337 for eg mounting a application so that I can deploy all the things in one server

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?

Curently I can't find information on how to take part in the Strapi Admin panel localization efforts. I have found the https://localazy.com/p/strapi-frontend-admin Localazy project, suggested Ukrainian translations for a lot of strings, but I can't find a way to make sure the translations get approved and eventually included into a Strapi release. A clear documentation explaining the Admin panel translations approval and release process would be extremely helpful

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.

It would be great to know how to protect an endpoint within a custom plugin with Strapi's API tokens. Through a long process of digging through source code, I found that defining the route as an object (instead of an array) with the values type: "content-api" seems to work. However there is no documentation on this at all.

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

I'm getting all these error messages that say "unmet peer dependency." You should have documentation on how to resolve this (even if it means reminding us of package manager basics.) Basically, Strapi can't find the version of React it's looking for. It's hard for me to dissect the log, looks like @bn-digital/strapi-plugin-field-uuid > @strapi/design-system@1.14.1" has unmet peer dependency "react-dom@^17.0.0 || ^18.0.0". I should know what I'm doing and have zero problems. I might be rusty on the the technicalities of yarn, npm, forcing installs, installing globally, etc. Also, it could be an error from a plugin that I stalled a while ago. However, I have no idea what would happen to my project if I just took those plugins out. It's also not clear at all what would happen to your database and your JSON files if I just "reinstalled" Strapi.

I used Strapi a couple of years ago and I love it, so thank you. I recently wanted to spin something up, went to your website, and was like oh yea I'll copy this npx quickstart command, naturally. Problem is, I had been using nvm, I think node 16 at the time, so it installed Strapi 3. There of course were a lot of npm deprecation warnings.. etc. It took me almost an hour to realize I needed to uninstall version 3, switch my node/npm version and reinstall/run the quickstart for Strapi i 4. I'm reporting this not to complain, but to bring attention to the user experience for other developers, especially newer developers unfamiliar with managing node/npm versions, etc. I was completely unaware of the unsupported version 3 changes until I dug into it and realized the problem. Perhaps there is a way to communicate this on the homepage, or somewhere in an FAQ. Just a heads up, thank you.