Summary

Danger

This tutorial is out of date. Please check the tutorials overview for our latest tutorials.

In this tutorial you have learned that it is possible to quickly fork a complete Quix project and get it up and running in your Quix account very quickly. This enables you to start your own project by using one of our templates. You can then modify our code, keeping your project in a public or private Git repository as required. Alternatively, you can build your own custom pipeline from a mix of our code samples, and your own custom sources, transforms, and destinations.

In addition, you have seen how in Quix you can:

• See the power of navigating your pipeline visually
• View the logs of a service as an aid to debugging
• View live data in the application view, or using the Quix Data Explorer
• Learned how you can host your project in a Git repository
• Learn how to examine the raw message data in the messages view
• Examine and edit the code of a service

Next Steps

Here are some suggested next steps to continue on your Quix learning journey:

• Build something with our code samples. You could take the camera feed, frame grabber, and object detection code samples, and add your own service to these, for example add a custom UI, or a simple service that just logs vehicles for a road that you have a specific interest in (maybe you live there).
• Try the Chat sentiment analysis tutorial.
• If you decide to build your own connectors and apps, you can contribute something to the Code Samples. Visit the GitHub Code Samples repository. Fork our Code Samples repo and submit your code, updates, and ideas.

What will you build? Let us know! We’d love to feature your application or use case in our newsletter.

Get help

If you have any further questions, we're here to help in the Quix Community.