Sorry, I thought I responded to this the other day, but my comments are nowhere that I can see now.  

Anyway, this is a good question. As the Shepherd workflow will continue to be supported, I felt it should be documented and connected to this centralized set of docs.  The Shepherd workflow can still remain on the CSSWG wiki only and not linked from here, but it will keep our testing documentation fractured. At least with this acknowledgement here (and with the Shepherd doc linking to all the new doc here), they're somewhat connected. 

If you think it should be removed from here, I'll go ahead. Fractured documentation is just one side effect of the bigger issue of fractured infrastructure and workflows across WGs.