Suggestion to improve documentations

Description

I have a thought and want to share. More like a personal opinion.
I've found it difficult to navigate through Piral documentations.

Piral Team has done an amazing job and documenting everything which makes getting started with Piral easy. Though on a day-to-day basis, I find myself needing to refer to the doc often... and struggling to

Help is wanted on this and I am available to assist anyone working on this problem. Join the freenode IRC #dashboard chatroom for support. Web IRC client

The tests for the API all emit structured data, consistently testing all the inputs and outputs whatever script might have. Because the data is structured it can be used for the documentation (a WIP) so up

Describe the bug
Running a simple, valid program in the JS.do example website may lead to a valid script terminating.

Error message is:
`Operation """": no method found, argument in overloaded package WebPerl::JSObject.
exit(255) called, but NO_EXIT_RUNTIME is set, so halting execution but not exiting the runtime or preventing further async execution (build with NO_EXIT_RUNTIME=0, if you

I'd like to convert a vTigerCRM 6.5 installation to berliCRM. How can this be done? Do you have any instructions? (maybe a script?)

This is for new developers who want to learn / get used to the code architecture of kitsune IDE. Its built on React.

For us to be open source, its important that every logic in the code base is documented. We would like to invite developers to help us get the code documented for kitsune IDE.