11👍
Signals are simply hooks that allow you to fire pieces of code after a particular action occurs, i.e. ‘when an instance/row of a model Foo is saved, run the function baz()‘. Signals have two components : the actual signal (the action that has been carried out – a save/delete etc.) and the receiving function (what to do when that action occurs).
Django has many signals built in (for example, that is fired after or before a save operation, a signal that is fired after or before a delete operation) but you can also create your own signals. If you had a signup process in your website, you could write a signal that fires when a user creates an account and then link that signal to a function that sends the user an email
I don’t think your situation is related to using signals. It sounds to me like you want to create a single form (composed of 3 smaller forms) where the latter 2 forms (Education & Experience) rely on the previous form (CV) being saved first?
In this case the issue is that you can’t fill out the 2nd and 3rd form without having filled out the 1st form first (as no CV will exist yet) so to achieve this you might be best creating a form wizard with 3 steps; first save the CV, then using the CV show the 2nd and 3rd steps (which at this stage the CV will already be saved)