Raam Baranidharan

@ferrouswheel please treat this as an Epic, when implemented this will definitely result in multiple tasks in different repos. (In fact I think it might be worthwhile for us to...

> Happy to hear how others think it might work, but for me it's not clear how we can do this in a generic way for calling from the CLI...

@astroseger I think @ferrouswheel is also treating the local copy as cache from blockchain and IPFS but is suggesting that we store it at a service level instead of at...

> Down the road we might want to allow more complex documentation structures e.g. an entire directory of documentation that can be fetched by service clients and browsed locally. If...

Here is the approach we are thinking of. During service registration we accept a URL to documentation in markdown format or a document itself. We keep a copy of this...

I fail to understand your point on > Developers should build and doc their service from their project dir Depending on the language of the service an appropriate tool can...

> I think it'd suffice to just have a local dir or markdown file be defined as the docs, and ensure that's pushed when the service is updated. @ferrouswheel thanks...

@arturgontijo @astroseger @vsbogd what do you think about tools like https://github.com/marketplace/restyled-io? Was thinking of setting up such bots to enforcing linting (where applicable) and to enforce code style guidelines. As...

@anandrgitnirman lets publish the findings and close this issue

@anandrgitnirman can you confirm if this error is seen still?