100% agree - furthermore, I think the idea of the ‘blog’ should really be repackaged as ‘collections’. As it can be used for so many things beyond a blog.
For example, the site I’m creating wanted a listing page of the 5 core services and then a separate page for each service. Each service has language and an image that should be consistent wherever listed in the entire site. If I were to just make separate pages I would have to manually add that language and image, whereas if I use the ‘blog’ and make each service a ‘post’, I can create the listing page, create a ‘post’ page, and then if I ever list them anywhere else in the site, I can use a loop to cycle through the posts and grab the language and image.
The same is true for work ‘case studies’. The only problem I’m running into there is that unlike the ‘services’ example above where I could get away with a static template for each service, case study ‘posts’ can be wildly different from one another, some might use 2 column image rows, others might use videos, etc. Not having the ability to drag and drop really complicates things. I’m now having to code a really complex module (MOAM, mother of all modules) that can handle all types of content. Feels extremely dirty.