wiremock-captain VS meta-system

github: https://github.com/HBOCodeLabs/wiremock-captain

Oh, There's the Documentation so you can get started on using Meta-System, and on how to develop your own Addons. And of course, there's the repo as well. :)

discord link documentation

So, given that I can see Chalk listed as the fourth dependency in your package.json...https://github.com/mapikit/meta-system/blob/master/package.json

Because it is powered by Meta-System (presentation video), you can also create new modules yourself and import them to the platform. If you're unfamiliar with Meta-System, you can check how to do it in the docs.

This is basically how I solved the modularity issue with Meta-System. Basically, the base software comes with some basic functions, but you can add your own without a change to the source code. This process consists in, during runtime, downloading the package from NPM, and then importing it and passing down the reference.

That being said, the importance of documenting your application is no breaking news. What might be surprising, however, is how difficult and time consuming the process of creating such documentation can be. While writing the documentation on my open-source software Meta-System, I came across a few difficulties that I would like to share, so that maybe you can avoid them yourself. But where do you start?

Check mapikit/Meta-system and join the discord if you like it!

This was made possible by using Meta-System, an open source software in which I had the pleasure of working on. It makes software accessible, while also providing you a way to contribute to such accessibility.