Exporters

Just like we currently have [importers](https://semapps.org/docs/middleware/importer/) to import non-semantic data to SemApps instances, we could provide exporters which export semantic resources to non-semantic tools like Wordpress or YesWiki.

It would be much easier to handle since we would only need to listen to `ldp.resource.created`, `ldp.resource.updated` and `ldp.resource.deleted` Moleculer events.

Then we will call the APIs, after having transformed these data.

It could work with all the tools we use for importers:

- [Discourse](https://semapps.org/docs/middleware/importer/discourse)
- [Drupal](https://semapps.org/docs/middleware/importer/drupal)
- [GoGoCarto](https://semapps.org/docs/middleware/importer/gogocarto)
- [HumHub](https://semapps.org/docs/middleware/importer/humhub)
- [JotForm](https://semapps.org/docs/middleware/importer/jotform)
- [PrestaShop](https://semapps.org/docs/middleware/importer/prestashop)
- [Mobilizon](https://semapps.org/docs/middleware/importer/mobilizon)
- [YesWiki](https://semapps.org/docs/middleware/importer/yeswiki)

Start by reading the existing importer documentation for Discourse, Drupal, GoGoCarto, HumHub, JotForm, PrestaShop, Mobilizon and YesWiki. Then investigate the ldp.resource.created, ldp.resource.updated and ldp.resource.deleted Moleculer events and the corresponding external APIs. Done would require a defined exporter scope, transformation behavior and supported tool integrations.

Written by the indexing model from the issue text.