Currently, every config section is appended at the start of the pipeline run. This is used to warn the user if the config on disk is modified.
When the pipeline adds a notebook page, any associated config sections should be appended to the notebook at that stage.
This way, if a user modifies a config section for a section already saved to the notebook, a warning or error can be issued.
The associated config sections can be stored within the notebook pages rather than the notebook. This way, if a notebook page is deleted, the associated config section remembered is also forgotten with it which makes sense.