lbighetti
Create ex_doc for context modules
Sorry I should have written a better description, I meant more ex_doc on relevant functions/modules.
I am not sure if this issue is meant to be a specific task for the entire project, but this documentation should be must-have on all implementations already, don't you think? I mean, as we must have tests for all new functions and modules, they should have their own documentation without the need to have a specific task for it. WDYT?
@rafaels88 I think some modules make more sense than others to have in-code documentation such as ex_docs. I believe mostly where the module is being shared within several parts of the application. For me this is the case for the context modules - in our case Mentorships and Accounts. Those definitely would be great to have ex_docs as they are reused several times and will potentially be reused more for future features.
Does that make sense ? Let me know your thoughts.
@pacheco7 for general documentation we can start with REAME i think. Perhaps we can move to wiki when we reach a point where the content is too extensive or too complex for the README. What do you think?