# Introduction ## Intended audience This book as its title suggest is for newcomers to drools. As explained in the drools tutorial, when using drools you will change the classical development paradigm you are using going from procedurale to declarative programming. The shift is not complex to accomplish but there is a need for a onboarding set of tutorials that will help you to jump into implementing algorith/business rules wiht drools with no difficulty. As a regular trainer of drools, I can only encourage you to do the exercices completely by yourself and try not to go the solutions directly. By doing so, the learning curve will be a little longer but so much easier at the end. By going directly to the solution, you will miss 50% of the training content. ## drools On-Boarding You can find here all the materials that go with this book. The book is also on Github[ here](https://github.com/nheron/droolsonboarding). Here is the [content](https://github.com/nheron/droolsonboarding/tree/25d7b86dab0670ff588b0ee9647656f19d0f45a5/SUMMARY.md) of the book ### How to edit the docs * go to [Drools Onboarding book](https://www.gitbook.com/book/nheron/droolsonboarding/details) * There you can clone and edit the document * You can do it from Github also ### How to run the tutorial and examples * the source code for the tutorials and examples can be found on [Github](https://github.com/nheron/droolscourse) * there is a virtual box appliance available with all included that you can find here (TODO) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://nicolas-heron.gitbook.io/droolsonboarding/master.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.