Trialling Gitbook for User Guide . . YAY!

Which pages in the Producer/Hub setup guides differ dramatically? Could we remove this duplicating structure?
It would be best not to have duplicate pages, but maybe it’s worth the effort for the additional useability?

  1. Create an account - SAME (have created generic page https://ofn-user-guide.gitbooks.io/ofn-user-guide-master/content/create-an-account.html)
  2. Profile types - Have different screenshots for producer/hub packages. (have created generic page https://ofn-user-guide.gitbooks.io/ofn-user-guide-master/content/hub-profile-types.html)
  3. The Dashboard - This page is pretty redundant. It just has screenshots of the dashboard, which differ depending on producer/hub and profile/shop. (Have created generic page https://ofn-user-guide.gitbooks.io/ofn-user-guide-master/content/the-dashboard.html)
  4. Your Profile - many sections are the same for producers and hubs (Primary details, users, address, contact, social, about, business details, images), and then the there are some fields that only apply to certain types of users (properties, inventory settings, shipping/payment/enterprise fees, tag rules, shop preferences) I think a lot of these sections could/already have their own pages though. (I’ve made one generic page (not hub/producer specific).
  5. Connect with your supplying producers - HUBS ONLY
    Products- There’s producer instructions, and the hub version has additional instructions regarding whether the hub user owns the producer or not.
  6. Payment methods - SAME - we may want individual pages for each payment method? Or not. Or Collapso Expando. (I’ve made one payment method page, with expando collapso- we can always break this up).
  7. Shipping methods - SAME
  8. Enterprise fees - is pretty much the SAME, just that producers are told ‘you probably don’t need these if only selling OWN’.
  9. Order Cycles - the producer OC page is quite a lot simpler, so better to keep these separate.
  10. View Orders - SAME
  11. Reports - SAME - we could turn this into a single report page - with different cases/scenarios which then direct to individuals pages for each report. (There’s just one report page in gitbooks)
  12. Advanced Features - SAME