HammerOz, thank you for your detailed reply. It is really, really appreciated!
I’d say those limitations basically rule out the ability to use the CMS, unless I’m totally misunderstanding, for example, if there are 100 practice areas, these would be considered a ‘collection’ if we want pages for each one, then there is a limit of 40 on Business for example. So that just wouldn’t work for us, neither the limit on 100 items in a drop down. We don’t need to see all ‘100’ but certainly need to be able to choose (first 3 letters) from the 1000’s in the DB.
Displaying list of practice areas on the lawyer cards is something we’ll be doing - so again this is going to cause us some design limitations.
Syncing data to our source/app - that’s no problem, this is what we would be doing and using the CMS Api.
What a shame, it really looked like a brilliant way for our designers to speed up dev by building out the pages, but I’m surprised by some limitations here.
Do you have any visibility/experience running Webflow on a sub-directory or a hybrid model where we run our own custom search listings and then use Webflow only for more simplistic marketing pages?