Those things are helpful, sure, but the problem is you take a silo approach, with different feature sets explained in different places, which is overwhelming. Fine for super users, who know what’s useful to them, so they know where to head for info, but newbies don’t know enough to decide what they need to know, so they go to a jillion places to try to gather it all, which adds to the overwhelmedness.
The problem of flexibility - serving myriad use cases - is obviously not unique to Drafts. My suggestion (I’m pretty good at this having founded a popular web community at the dawn of time that served many different purposes to many different people) is that you’re over-estimating how much you need to cater to personal adaptation. Humans are hard-wired to watch demonstrations of irrelevant use cases and apply/adapt it to their unique needs. They’ll do that work for you.
As is, you are forking and fragmenting (thinking like devs!) to explain and cater to diverse use cases, and this increases complexity on our end as well as yours. Maybe you need to formalize the different use cases for marketing, but I’d avoid that morass for support purposes.
Show us someone using Drafts in real-case scenarios, at nearly normal speed, with only light narration. We’ll pick up the gist faster than you think. Don’t sweat that most of us won’t be creating invoices for a wholesale pipe fitting business. Just let us GET THE FEEL. Don’t under-pace…don’t teach, show. If you approach like this with, say, three very distinct use cases, you can trust users to adapt and personalize on THEIR end. A pull, not a push.
If you could produce such a demo and re-do it for major releases, that would be optimal. If not, re-do it every X releases but do produce a visual run-down of new features for each release, again, showing a few real-world use cases (again - bears repeating! - we can self-adapt and personalize better than you realize). Don’t make them slow and pedantic (we can read support materials for fine details). Just give the flavor of the new tricks. Like looking over the shoulder of a real-world Drafts user.
Sorry I went on a bit, but this sort of thing is an interest of mine, so I’m actually forcing myself to be terse!