Extend algoliaPost with additional ghost post field

[kassiwin]

The package concerned is algolia-fragmenter specifically the transformToAlgoliaObject function.

Currently, the algoliaPost is hardcoded and the function does not offer any way to add additional fields. It will be interesting to add an optional argument to transformToAlgoliaObject which will help to extend the algoliaPost.

[coelhucas]

Up. It would be awesome to both be able to override or extend these fields (we may not want some or just add a few others).

Right now in order to do that one would have to maintain their own fork just to change a line in fragmenter code 😞

I'm willing to open a PR for this if that's ok for folks at Ghost, just let me know and also if there are any constraints regarding adding that functionality.

[aileen]

Hey hey! PRs are very welcome. Just ensure you don't introduce any breaking changes 😊

[aileen]

The planning decision is now approved in Decide the Ghost field projection and excerpt contract.

The replacement contract introduces a shared JSON-serializable Ghost content projection with an authoritative allowlisted optional-field set, safe output aliases, optional authors/tags, protected record invariants, and the same behaviour across direct callers, the CLI, and Netlify. It deliberately avoids arbitrary pass-through fields and executable mappers.

This request remains open until the new deep fragmenter interface and configuration ship. The implementation and compatible release order are still owned by Define the compatible implementation and release sequence; delivery, not the planning decision, will close this request.