Recommendations to others considering DubBot:
Start with just one site that uses your template and work out all the issues DubBot flags first (assuming your site has issues--your site doesn't have any issues, does it?) . Get this done before letting your users in so they're not seeing template-wide issues that aren't their responsibility to fix. Also, under your users, you can filter which issues they'll see. We recommend setting this filter to "See issues relevant to content editors" for your users who aren't part of a core web team, that way they're just seeing things like spelling errors, content accessibility errors, broken links, and your custom governance checks, and not more technical issues that are outside the scope of their position. Review collected by and hosted on G2.com.
What problems is DubBot solving and how is that benefiting you?
Our organization uses a distributed content model in which ~400 users are responsible for content across many subdomains. Getting specific governance reporting for each for these units was a missing piece in our web content strategy. DubBot has solved this issue and gets automated feedback where it needs to go. Review collected by and hosted on G2.com.