As for the core limitations two things are hitting me. The first I am not sure is actually a limitation but everytime I bring it up everyone basicly tells me that Umbraco is not sutied for it, the other once is doable in Umbraco but just not easily. 1. My site is a game information site so there are lots of pages for weapons, armor, items, food, quests, ect and they all interlink with eachother. A single game we are working on just over 50,000 pages for that information alone. This brings big concert for indexing and searching. While I have been told by some people who appear to work at Umbraco HQ that Umbraco can handel that many pages with no problems they do say that there might be indexing issues because of the large amount of data. Others have told me that Umbraco is not designed for these things. I really don't know, I do know I have ran into indexing problems back in v13 but those problems have been fixed in v17 bu we have not imported the information pages yet so time will tell on thise issue. 2: Dynamicly gereated and interactive pages seem to be out of scope for Umbraco. Some of the projects I want to build for my sites do not just present data but are user driven. For example, a crafting shoping list system. The user searches for the items they want to craft, the system looks a the recipies and then calculates the items needs and in what quantity. The user can then mark off what they collect as the collect them, and even save lists for feature usage. The only way I see of doing this is to create a doc type with no prooperties and wire all the code up in the back, but that means a single doc type for any and all interactive pages like this.

I had also forgoten to mention that the face password managers can cause problems with the backoffice "due to the shadow DOM" is really bad. Passwords managers are a great way to enhance account security on the net and to be like "yea, to make sure you dont have problems with umbraco uninstall your password manager"

The rich text editor issues, you mention, are tough ones. Yes, object resizing is not possible in Tiptap at the moment. Unfortunately, we cannot bring back official support for TinyMCE due to licensing. Tiny Inc. have an official package that adds support for TinyMCE, so you have the option to use it just like you did in version 13 and before. Just know that the MIT-version (version 6) is EOL (which is why we can't ship with it) and that you probably have to pay a license to upgrade to the newest version 8. Luckily, we will add more properties to edit in Tiptap, so that you can edit width and height on images. I believe that ships in version 17.4.

Lastly, password managers not being supported: I was actually under the impression that they worked now. Dashlane seemed to be the big culprit, but the latest reports I heard said that it now worked fine. Are you experiencing problems with password managers still?

Thanks for your words. I love hearing about the issues people experience with the product. Had a few more thoughts around what you said: Search & indexing - You are right, Examine will fail at some point given too much data. It's hard to tell when that happens. Ultimately, Examine is file based and so, limited by the filesystem. Did you know you can soon replace Examine? [Umbraco.Cms.Search](https://github.com/umbraco/Umbraco.Cms.Search) is currently in beta, but expect to ship soon including support for V17 and V18. It will allow you to plug in Elastic Search, which should be more than capable of carrying that amount of data. Dynamicly gereated and interactive pages - It seems to me like you are in a scenario, where you need to extend your application rather than force Umbraco CMS into a situation it's not suited for (square peg in round hole kind of scenario). You can add your own tables to the database, create repositories and controllers and handle the data like you would. You can do all of that whilst referencing Umbraco data. There are packages that add "custom data pickers" to Umbraco handling your data. [Contentment](https://marketplace.umbraco.com/package/umbraco.community.contentment) is one such example with its 'Data Picker'. a required field is on a non-active tab - Sounds like a [bug report](https://github.com/umbraco/Umbraco-CMS/issues) waiting to happen?

I do understand why TinyMCE was removed and I had heard about the unmatainablity of the old backoffice. To me, and many others though I have seen a lot less talk about it since 17 relesed, the new backoffice was a big downgrade compaired to 13. Personaly when I was dealing with in 14-16 I understood these where STS and considered them more beta versions vs an acutal, production ready, release like 17. I don't know the structure of the teams at HQ and how issues are prioritized so I am not going to speculate on resorce allocation and priortization for getting the new backoffice feature equavalant to the old but the current issues my team and I are having are a big annoyanceI and have actually cost me money in downtime. The employee I have that had a PW manager installed on there system no longer needed it, it was a relic from an old contract they worked, and so have uninstalled it. Which looks to have resolved the issue of the the entire backoffice randomly refusing to load for him. I just started using my own password manager (proton) and so far have not noticed an issue but I don't often go into the backoffice as my resrouces are currently focused at an umbraco package I am building and then the rebuild of the site. So for now I have no data to point one way or the other. I do want to say that it was nice to see you not try to push for the subscription based plugin that Umbraco sells to manage outside data within the app (I think it is called like Data Builder or Data UI or something). I have actualy installed the TinyMCE plugin but with the performance issuse in the backoffice I am trying to keep to a minimum amount of plugins to reduce package calls and file downloads (which seems to be one of the leading theroies as to why the backend is slow).