Imagine you start a website from scratch or from an already made template, you play around with the components (presets), you add, you test, you don’t like, you remove, then add other components, and you keep doing this until you’re happy with your design. Now you are ready to publish. What is happening is that you are also publishing all the presets that have served as tests (those which you have decided to discard) - let’s call them draft presets -, along with those you have kept. And this is the issue I wanted to point out.
It would be great to not publish the draft presets and only ship the used ones. The best way to do so, is to implement a presets cleaner, that is triggered just before publishing. Until implementing this cleaner, the workaround would be to clean them manually (but it is risky, as @Andre said in this post). In this case, it would be better to have a tutorial that helps us to do so, until the implementation of the cleaner.
In my humble opinion, having presets cleaner is a must. Using tools like SiteJet are created to ship website rapidly and not waste our time in cleaning code.
Related threads: