No results


    An eLearning video version of these tutorials and how-to guides, with certification, is available here.


    We try real hard to make Hackolade Studio as intuitive as possible with a minimalist design, and we avoid to bloat the software with functionality that few people ever use.  In reality, the use cases for the tool are super simple:

    • start from a blank page, construct your data structures, then forward-engineer artifacts to be consumed by target technologies or data citizens;
    • or reverse-engineer an existing instance, enrich the model with descriptions and constraints, then publish the documentation


    The rich feature set appears when you realize the variety of data sources and targets for the tool, and our ability to convert to and from any of them.  This is illustrated by the capacity to translate, in any of the target technologies we support, data structures imported from JSON or YAML documents, JSON Schema of various draft levels, DDLs from all kinds of dialects, plus also XSDs or Excel.  


    The complexity occurs when diving deeper in each of the use cases.  NoSQL and JSON seem simple from the outside, but their power and flexibility offer many permutations that end up increasing complexity.  With Hackolade Studio, we try to deal with this complexity in simpler ways, and only when necessary.  For example, we allow non-technical users to generate JSON Schema files without requiring any knowledge of JSON Schema syntax.  Or for such users to create REST APIs without any knowledge of Swagger/OpenAPI specification syntax.


    As a result, you don't need extensive training to create a simple data model.  But to be a power user, you need to be aware of all the bells and whistles provided to handle real-life situations.


    People learn in different ways:


    We try to accommodate whatever method works for our users.  This series of tutorials provides a self-paced progressive learning approach to discover the features of Hackolade Studio.


    Some people like the linear flow of outlines, while others prefer non-linear mindmapping.  In addition to the tutorial pages below, we have started an experimental mindmap on this Miro page.  There are 2 views: a functional view, and a user interface view.  In the boxes of each view, you can click on the hyperlink to a page of this online documentation.


    Miro functional view



    Miro UI view


    Don't hesitate to let us know your feedback and suggestions for improvement.