This came up during the discussion of arguments for the content definition/view CLI commands.

So I considered making view name unique per definition (like repo -> product) but for simplicity, I think it would be better to not let users name two views with the same name. Especially since there are pages and CLI output where it's not evident what the view's definition is.

That said, if there's a good reason to make view name unique per def, I can do that.