Pretty simple question: what are best practices for making a handful of feature classes which participate in relationship classes with one another available for editing offline in Collector.
Up to this point I have been accustomed to publishing one feature service per feature class that I wish to edit. Many of those feature classes have had related tables for storing additional records or photo attachments, but I have never had to deal with this situation where the relationship classes define associations between multiple feature classes.
I've been unable to find any official esri documentation that speaks to this, nor have I found any posts on GeoNet or the broader web. I'd appreciate any recommendations or links.