Add pre-save, pre-publish hooks to CMS

[cpjolicoeur]

Per discussion in the Gitter channel, just making an issue for thoughts & discussion around adding some "hooks" to the CMS for pre-save and pre-publish events. These hooks could allow the CMS user to modify file content before persisting to the backend (and/or other content changes anyone might want to do in the given hook).

[delucis]

I recently needed a widget to automatically generate a modified time for entries, but had to make do with generating it when the editor was opened. Seems like a good example of a widget that would benefit from these hooks.

Could components declare preSave() and prePublish() similar to the isValid() method that is already available?

[erquhart]

I love the idea of events in general, big thumbs up for this. I'm not sure about the component methods approach - it introduces problems that are just unnecessary.

[tech4him1]

Agreed, for the case of providing an initial value like @delucis mentioned, we can work on something like #725. Global hooks sound awesome though (I just feel like I'm back in WordPress land 😆)

[erquhart]

Ha! Any ideas for alternatives?

[cedricdelpoux]

I think this feature could be very usefull for some cases.

I have my content in a git submodules. So each netlify-cms update commit to my submodule repo. But My main repo does not change anymore so netlify does not trigger a new deploy.

[visuallization]

Oh yes this feature would be really nice! I could then create dynamically pages with a script within in my nextjs app. So let's say: As an author I create a new page and publish it over netlify cms, "on save" -> the hook kicks in, executes the script which creates tsx files in pages/ based on the .md files in content/.

Are there any news about the progress here?

[davejm]

See #2344 for a quick mockup of how this might be implemented. Unsure if this is the right direction but it's a suggestion.

[erquhart]

Commented, thanks for using a PR to promote a path forward!

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.