1. lots of these could be fixed with more IT / Dev resources - not intrinsically linked with Jahia. Could another platform solve this pain points? Or we are back to the same situation...
1.1. No versioning
1.2. Adding new languages (to catalogue) not really Jahia but it's architecture of the loader..
1.2.1. not straight-forward with current data architecture
1.3. Site import-export difficulties
1.3.1. Test not in sync
1.3.1.1. in progress to be solved
1.4. Translations
1.4.1. No easy workflow for language translations - need to copy and paste
1.5. Performance
1.5.1. Slow for users
1.5.2. ITES is working on solving main problems (import/export to reduce size of data - cloudflare - CDN)
1.5.3. Slow for editors
1.6. Content locks
1.6.1. less and less
1.7. Hard to deploy new features (risky)
1.7.1. ITES is working on making it more reliable.
1.8. Jahia not updated to last version
1.8.1. ITES is working on making it more reliable.
1.9. WYSIWYG could be better
1.10. Lack of native support for modern image formats (SVG, WebP, JPEG XL, AVIF)
1.10.1. could be done though.
1.11. Integration with other tools
1.11.1. Not many external tools are easy to integrate with Jahia (limited Market place)
1.12. Webstore UX not consistent - OBP, ISO.org...
1.12.1. registered users status visible only on OBP
1.13. Dev experts (difficult to find)
1.13.1. Not the most popular CMS
1.14. Data loader
1.14.1. little flexibility to modify
1.15. Search implementation
1.15.1. No resources for improving Algolia
1.15.2. No resources for improving Advanced Search
1.16. Preview standards
1.16.1. on OBP
1.17. Templating
1.17.1. not very flexible - need dev most of the times