Suggest improving route documentation and optimizing admin path structure
木有符号
Hi team,
When using Strapi 5 with a shared domain for frontend/backend, we noticed that in addition to
/api
and /admin
, the system uses several undocumented routes like /content-manager
, /upload
, etc. This requires us to manually add each path rule in reverse proxy configurations (see attached Caddy config), where any oversight can lead to route conflicts.Suggestions:
- Clearly list all system-used routes in prominent documentation sections
- Nest admin-related paths under /admin(e.g./admin/content-manager)
- Add prominent notices about route configuration in quick-start guides
These improvements would help developers configure production environments more efficiently and avoid route conflicts. Thank you for your great work!