Hey, I’m trying to figure out how to best generate a documentation for a large Meteor project. The project has both npm and atmosphere packages / libraries that need to be documented and i’m using jsdoc to generate them. So far so good. I’ve got my documentation up and running, but there are some things that I wasn’t able to figure out yet. Its unlikely to be meteor specific, but I do see that docs.meteor.com has already solved the issue:
Differentiating server and clientside code. I see that the jsdocs of meteor are using a tag called @locus. However its not documented anywhere and it seems to be specifically made for meteor and meteor-jsdoc.
Its also good to mention that I find meteor-jsdoc a bit too much and too custom made for meteor in regards to the project that i’m working on.
So how do I differentiate serverside, clientside and ‘Anywhere’ in my jsdocs without having to use meteor-jsdoc? Are there other meteor specific gotchas that I will have to watch out for when writing documentation?